Cord is a data streaming platform for composing, aggregating and distributing arbitrary streams. It uses a publish-subscribe model that allows multiple publishers to share their streams via a broker. Subscribers can then compose custom sinks using a regex-like pattern to access realtime data based on their individual requirements.
Cord has a programmable interface in the form of the cord-client library, so it can be adapted to various use cases. As the library matures, this library will form the basis of a suite of adaptors for common technologies.
The easiest way to get up and running is by using the Client CLI. In most production scenarios, you would implement the Client library independently.
By default, the --bind-address is 127.0.0.1, and the --port is 7101.
$ ./cord-broker &
In this example, we will subscribe to the /names namespace.
$ ./cord sub /names
Whenever a new event is published under this namespace, it will be printed to stdout.
First, declare that you will provide the /names namespace.
$ ./cord pub /names
Next, enter key-value pairs into the console, using the format NAMESPACE=VALUE. For
example:
/names=pete
/names/fictional=Homer Simpson
Cord comprises a number of modules:
- cord-broker - the server binary that aggregates and distributes arbitrary streams
- cord-client - provides a library and CLI for interacting with Cord brokers
- cord-message - provides the core
Messageenumerator and codec for sendingMessages between brokers and clients - cord-pattern - provides the algorithm for comparing namespace patterns
- cord-pubsub - provides a
PublisherandSubscriberto represent the stream and sink components of a client connection within a broker
Cord derives its name from the spinal cord. The long term goal of this project is to aggregate data from every part of your environment, so that the decisions you make within that environment are better informed. This is akin to the central nervous system, which uses the spinal cord to aggregate electrical feedback from nerve endings.