Btw if you are looking for a different comparison point there are other
frameworks such as akka (http://akka.io), apache spark (
https://spark.apache.org), or ibm streams that might be more interesting.
On Nov 17, 2014 2:19 AM, "Patrick Wiener" wrote:
> @Nathan: :) thanks for the quality comparis
@Nathan: :) thanks for the quality comparison. Nice bottom line for a
presentaton/conclusion.
@all: thank you for your help. Awesome support in this community.
> Am 17.11.2014 um 07:58 schrieb Vladi Feigin :
>
> Nathan,
>
> Liked ! <>
>
>
>> On Sun, Nov 16, 2014 at 9:06 PM, Nathan Leun
Nathan,
Liked ! <>
On Sun, Nov 16, 2014 at 9:06 PM, Nathan Leung wrote:
> Also it supports cycles in the graph. It's like comparing a bicycle to an
> airplane.
> On Nov 16, 2014 2:03 PM, "Vladi Feigin" wrote:
>
>> Storm is much more sophisticated then just filter-pipe pattern.
>> It provide
Also it supports cycles in the graph. It's like comparing a bicycle to an
airplane.
On Nov 16, 2014 2:03 PM, "Vladi Feigin" wrote:
> Storm is much more sophisticated then just filter-pipe pattern.
> It provides
> 1. Reliability: guarantees that every spout tuple will be fully
> processed. Actuall
Storm is much more sophisticated then just filter-pipe pattern.
It provides
1. Reliability: guarantees that every spout tuple will be fully processed.
Actually it provides : at-most-once delivery(no ackers) , at-least-once
delivery(ackers) and exactly-once (Trident) semantic for the message
deliv
So basically Storm’s core concept can be compared to pipes-and-filters-pattern
BUT provides a more „user-friendly“ framework than e.g. a unix based
pipes-and-filters processing.
btw: I haven’t come across with TRIDENT yet. Just starting to dive deeper into
Storm as a potential technology for a
