Eurybates is a library for producing to and consuming from queues. There is one queue per consumer (named eurybates.<service-name>), and producers write to each consumer's queue*, after getting the list of consumer queues from Zookeeper. Each consumer receives all messages, but the consumer library discards all events which don't have the tag which you specify when you initialize the consumer (a simple string). This was judged to be more efficient than consumers somehow registering their tags with the queue server.
When a new service which consumes from Eurybates is deployed, its name must be added to Zookeeper under the path /eurybates/services. Producers then pick up the new service and start sending to its queue. (See section "Adding a queue to ActiveMQ" below)
Eurybates supports Kafka and ActiveMQ, but as of writing we use it with ActiveMQ at Socrata. It's configured via a properties object and a client-application-defined Source ID.
To include Eurybates in your SBT Project
Ensure you have the Socrata CloudBees Resolver added the list of resolvers
resolvers ++= Seq(
"socrata maven" at "https://repository-socrata-oss.forge.cloudbees.com/release"
)
Then add Eurybates to your list of library dependencies
libraryDependencies ++= Seq(
"com.socrata" %% "eurybates" % EURYBATES_VERSION
)
Traditional SBT Tasks
sbt compile test package
Eurybates can be used to produce or consume messages. To do either requires the following properties configuration. All configuration is rooted with the prefix of eurybates.
eurybates.*
Configuration differs based off different components.
- Producer
- Consumer (Planned)
- Picking a Producer type(s). The available options are activemq, kafka, local_service, and noop.
eurybates.producers = activemq | kafka | local_service | noop
or
For Multi-Plexing Producers
eurybates.producers = activemq,kafka
Configuring Kafka Requires a broker list Properties. The broker list is a comma separated of Kafka broker host:port. Each broker must be apart of the same Cluster.
eurybates.kafka.broker_list = kafka-1:9092,kafka-2:9092
eurybates.activemq.connection_string = tcp://activemq-1:PORT
-
Find and ssh into a zookeeper node (for example,
knife search node 'role:*zookeeper* AND environment:*staging*')
sudo su
/opt/zookeeper/zookeeper-3.4.6/bin/zkCli.sh
create /eurybates/services/new-queue-name "new-queue-name"You could use any consumer library capable of consuming messages from JMS (for activemq) or Kafka. We are looking to modernize Eurybates to use a better streaming models. Possible options for consuming Kafka Messages.
- Kafka Clients: Maven Library
- Scala Kafka: https://github.com/stealthly/scala-kafka
- Reactive Kafka: https://github.com/softwaremill/reactive-kafka
- Eurybates itself
Eurybates enforces some interesting requirements and design decisions that can make it initially confusing. Eurybates also makes some assumptions about how you want to commit offsets as well. Currently, Eurybates automatically commits offsets every 10 seconds. This means you have no direct control over when you tell Kafka you have recieved a message. If this does not fit your use case do NOT use Eurybates at this time. Please use one of the above options.
If you decide to use Eurybates, in order to consume messages you must define a class that extends com.socrata.eurybates.Service.
class FooBarService extends Service {
override def messageReceived(message: Message): Unit = {
// Process the message however you like
System.out.println(s"Yay I Received a message: $message")
}
}
The service serves as a callback and a consumer must defined in your container class, object, or trait like so.
object FooBarWrapper {
def consumer() = new KafkaServiceConsumer("kafka-broker-1:9062",
"some-source-id",
Executors.newFixedThreadPool(1),
(sn: ServiceName, s: String, t: Throwable) => {},
Map((Name, new FooBarService())))
}
TODO Document how to incorporate Eurybates into your test.
None at this time... Yikes.
Socrata Engineering Members
- Robert Macomber
- Andrew Gall
- Michael Hotan
Apache Version 2.0 License