Lots of problems can be understood as a immutable log of events. Kafka is a screamingly high performance, resilient, immutable log of events.
It is kind of infectious though, once you have system implemented as Kafka-and-Samza the easiest way for them to communicate e and be communicated with is more Kafka and Samza.
I am fully on board the Kafka hype train. Choo choo.
The "Turning the database inside out" article that's linked a couple of posts up about Kafka and logs in general was the one that made me sit up and take notice and really made me 'get' Kafka and the entries stream oriented processing thing.
It raises interesting questions and I've had fun producing both arguements for and against the approach.
http://kafka.apache.org/documentation/#introduction
reply