Twitter Heron: Stream Processing at Scale (opens in new tab)

> All the Stream Managers in a topology connect to each other to form an O(k^2) connection network

shouldn't that be !(k-1)? Or am I missing something about the architecture?

Is the paper online? If someone can produce a standard URL for it, we'll change the link in this post.

"In the evaluation in section 7 of the paper, Heron beats Storm in every single metric."

In every metric except perhaps the most important one for actual users:

Storm is open source, Heron isn't.

Also, the @TwitterOSS account indicated that there are "no plans to open source in the short-term":

https://twitter.com/TwitterOSS/status/605460461761396736

Now I get it. It's not just "I didn't write this, therefore shit, so I need to rewrite it from scratch." This was a clear explanation in a bite sized chunk which illustrated the reasons for Heron. Thanks.