Snip
|
The growth of both the types and the amount of data gene... users, and applications have resulted in a number of rec... innovations: NoSQL, rise of popularity of Hadoop, and do... higher-level map-reduce frameworks. However, the batch-p...
|
---|
Categories |
|
---|
For Snip |
loading snip actions ... |
---|---|
For Page |
loading url actions ... |
The growth of both the types and the amount of data generated by servers, users, and applications have resulted in a number of recent trends and innovations: NoSQL, rise of popularity of Hadoop, and dozens of higher-level map-reduce frameworks. However, the batch-processing model imposed by map-reduce style of processing is not always a great fit either, especially if latency is a priority.
What if we turn the problem on its head: instead of storing data and then executing batch queries over it, what if we persisted the query and ran the data through it? That is the core idea and insight behind Event Stream Processing (ESP) systems: store queries not data, process each event in real-time, and emit results when some query criteria is met.
HTML |
<p>The growth of both the types and the amount of data generated by servers, users, and applications have resulted in a number of recent trends and innovations: NoSQL, rise of popularity of Hadoop, and dozens of higher-level map-reduce frameworks. However, the batch-processing model imposed by map-reduce style of processing is not always a great fit either, especially if latency is a priority.</p> <p>What if we turn the problem on its head: instead of storing data and then executing batch queries over it, what if we persisted the query and ran the data <em>through</em> it? That is the core idea and insight behind <a href="http://en.wikipedia.org/wiki/Event_stream_processing">Event Stream Processing</a> (ESP) systems:<strong> store queries not data, process each event in real-time, and emit results when some query criteria is met</strong>. </p> |
---|