Twitter Heron: Stream Processing at Scale

&quot;In the evaluation in section 7 of the paper, Heron beats Storm in every single metric.&quot;<p>In every metric except perhaps the most important one for actual users:<p>Storm is open source, Heron isn&#x27;t.<p>Also, the @TwitterOSS account indicated that there are &quot;no plans to open source in the short-term&quot;:<p><a href="https:&#x2F;&#x2F;twitter.com&#x2F;TwitterOSS&#x2F;status&#x2F;605460461761396736" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;TwitterOSS&#x2F;status&#x2F;605460461761396736</a>

&gt; All the Stream Managers in a topology connect to each other to form an O(k^2) connection network<p>shouldn&#x27;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&#x27;ll change the link in this post.

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