tag:blogger.com,1999:blog-6952832752072188515.post8792275536348595353..comments2023-05-09T02:45:23.919-07:00Comments on Big Data and Analytics - The Currency of the 21st century: Stream Computing (Streams) versus Complex Event Processing (CEP)Tilakhttp://www.blogger.com/profile/04588995544794162628noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6952832752072188515.post-25639451485091694062012-09-05T14:52:10.615-07:002012-09-05T14:52:10.615-07:00Many differences between CEP products and InfoSphe...Many differences between CEP products and InfoSphere Streams appear to be a difference of degree. But when you set out to build a development platform for building--through programming--solutions that can apply any kind of analysis to any kind of data at any speed, you end up building a product that is fundamentally different from the business-oriented, discrete event-based, analyst-friendly CEP offerings. <br /><br />Sometimes it's hard to put your finger on it and explain it in a way that's easily grasped, but the experience of solving a challenging problem with Streams is nothing short of exhilarating. If you can think it, you can implement it. If you know of a code library that does something useful, you can apply it. During development, you don't worry about runtime issues, distributed processing, tuning, or scaling at all. The paradigm of a flow graph of individual processing steps ("operators") connected by streams is simple, powerful, and liberating in that it directs your mind to think of the problem in the most productive way. <br /><br />Sometimes problems that have a simple solution in Streams look in hindsight like they should have been simple to solve with other tools as well--but they weren't. I think this is because Streams has a well-conceived development model, with the right levels of abstraction; it's probably similar to the unleashing of application creativity that came from the introduction of the relational model in databases.Anonymoushttps://www.blogger.com/profile/03816067186578333386noreply@blogger.com