storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <leon_mcl...@tutanota.com>
Subject Re: RE: Storm unique strengths
Date Thu, 02 Jun 2016 13:27:37 GMT
Hi Marc,

I had come across Heron a couple of weeks ago. It was indeed quite 
interesting. Thanks for the hint.

Regards
Leon


1. Jun 2016 11:47 by M.Roos@f1-outsourcing.eu:


>
> Maybe also take into account the new heron
>
> https://blog.twitter.com/2016/open-sourcing-twitter-heron
>
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -.
> F1 Outsourcing Development Sp. z o.o.
> Poland
>
> t:  +48 (0)124466845
> f:  +48 (0)124466843
> e:  > marc@f1-outsourcing.eu
>
>
> -----Original Message-----
> From: > leon_mclare@tutanota.com>  [> mailto:leon_mclare@tutanota.com> ]
> Sent: woensdag 1 juni 2016 11:44
> To: User
> Cc: > aaron.dossett@target.com
> Subject: Re: Storm unique strengths
>
> Hi Aaron,
>
> thank you very much for the link. I found it quite insightful. It is one
> of the few benchmarks i have encountered where Storm comes out on top in
> terms of latency, although the at-most once trade-off is quite harsh.
>
> Regards
> Leon
>
> 31. May 2016 15:37 by > Aaron.Dossett@target.com> :
>
>
>
> 	Hi Leon,
>
> 	This isn’t an advocacy piece per se, but this analysis by several
> member of the Storm community may be helpful.  For a particular use case
> you can compare performance and then assess whether the features,
> user-friendliness, or API of a particular framework is worth switching
> to.
>
> 	> https://yahooeng.tumblr.com/post/135321837876/benchmarking-streamin
> g-computation-engines-at
>
> 	
> 	From: "> leon_mclare@tutanota.com> " <> leon_mclare@tutanota.com> >
> 	Reply-To: "> user@storm.apache.org> " <> user@storm.apache.org> >
> 	Date: Monday, May 30, 2016 at 3:28 AM
> 	To: "> user@storm.apache.org> " <> user@storm.apache.org> >
> 	Subject: Storm unique strengths
> 	
>
> 	Hi Storm team,
> 	
> 	there are a lot of online comparisons between Storm and other Data
> Stream Management Systems, yet few of them originate from Storm
> committers/advocats.
> 	I am trying to identify the aspects that Storm possesses, which
> make it stand out among its direct competitors. Currently there is
> significant competition from Apache Flink, although less so from Spark
> due to its seconds latency restriction.
> 	
> 	From my experience Storm offers a unique support for DSLs, as well
> as a very flexible concept of Spouts and Bolts. Other aspects however
> seem to have been improved upon by Flink in greater part.
> 	
> 	Would you be able to direct me to resources that argue more towards
> Storm's case?
> 	
> 	Thanks in advance.
> 	
> 	Leon
> 	
Mime
View raw message