I work on a streaming system (IBM Streams). I was reading through one of your blog posts (http://www.jonathanbeard.io/blog/2015/09/19/streaming-and-dataflow.htm

I work on a streaming system (IBM Streams). I was reading through one of your blog posts (http://www.jonathanbeard.io/blog/2015/09/19/streaming-and-dataflow.html http://www.jonathanbeard.io/blog/2015/09/19/streaming-and-da...), and I saw this comment: 'Storm, Samza, and Spark are open-source streaming platforms that are focused on message-based data processing. These systems differ from other classic "streaming" modalities in that they eschew point to point communication for centralized brokers to distribute data.' That's maybe true for Spark, but it's not true for Storm and Samza (or of Streams). Yes, there is some centralization for application control, but there is no centralized data broker. That is, all messages are not routed through a centralized broker. I believe Storm does route all messages that come through the same JVM through the same logic and connection, but that's quite different from having a completely centralized broker. I can't speak for certain Samza, but I would be very surprised if it used a centralized broker. In Streams, I can say for certain that there is no centralized broker; messages are definitely sent "point to point."