Very nice post :) Storm is very good in terms of the capabilities it has. The only thing is they could have provided API in Scala as well as Python. Also, when debugging, understanding clojure code is bit hard. They should have written code using functional programming language like Scala.
On Wed, Oct 21, 2015 at 1:18 AM, Ankur Garg <[email protected]> wrote: > Very Nice post Satish . Thanks for sharing :) . > > On Wed, Oct 21, 2015 at 12:33 AM, P. Taylor Goetz <[email protected]> > wrote: > >> Hi Satish, >> >> Great series of blog posts. Thanks for sharing! >> >> -Taylor >> >> On Oct 19, 2015, at 4:24 AM, Satish Mittal <[email protected]> >> wrote: >> >> Hi All, >> >> The data platform team at Inmobi recently performed an extensive >> evaluation exercise in the process of finalizing the real-time Stream >> processing stack as the choice of our platform. >> >> We have captured all the details of our evaluation as the following >> series of 4 blogs which have been published at Inmobi technology site: >> >> 1) Introduction; Identifying stream processing use-cases at Inmobi; >> Identifying potential Technology Candidates. In the interest of time, we >> limited the >> >> http://technology.inmobi.com/blog/real-time-stream-processing-at-inmobi-part-1 >> >> 2) Detailed overview of Storm and Spark Streaming platforms >> >> http://technology.inmobi.com/blog/real-time-stream-processing-at-inmobi-part-2 >> >> 3) Identify and define various important evaluation criteria >> >> http://technology.inmobi.com/blog/real-time-stream-processing-at-inmobi-part-3 >> >> 4) Detailed findings on various evaluation criteria, evaluation summary >> along with the final recommendation. >> >> http://technology.inmobi.com/blog/real-time-stream-processing-at-inmobi-part-4 >> >> We hope that this analysis would be useful in general to anyone who is >> starting to explore the world of real-time stream processing and decide >> upon a particular tech stack. >> >> Please go through the blogs and let us know your thoughts! >> >> Regards, >> Satish >> >> >> >> >> >> _____________________________________________________________ >> The information contained in this communication is intended solely for >> the use of the individual or entity to whom it is addressed and others >> authorized to receive it. It may contain confidential or legally privileged >> information. If you are not the intended recipient you are hereby notified >> that any disclosure, copying, distribution or taking any action in reliance >> on the contents of this information is strictly prohibited and may be >> unlawful. If you have received this communication in error, please notify >> us immediately by responding to this email and then delete it from your >> system. The firm is neither liable for the proper and complete transmission >> of the information contained in this communication nor for any delay in its >> receipt. >> >> >> >
