Hi Murthy, It looks like that you can use Ignite Streaming feature [1] with pre-configured sliding window [2] basing on what you mean under "temporarily". One of the advantages of Ignite's sliding windows is that you can query particular events using advanced SQL, text or other queries.
[1] https://apacheignite.readme.io/docs/streaming--cep [2] https://apacheignite.readme.io/docs/sliding-windows -- Denis On Mon, Jan 18, 2016 at 8:50 PM, Murthy Kakarlamudi <ksa...@gmail.com> wrote: > Thanks all for your responses. Will look into these alternatives. > > On Mon, Jan 18, 2016 at 11:24 AM, Jörn Franke <jornfra...@gmail.com> > wrote: > >> You seem to look for streaming solutions , such as Spark Streaming or >> Flink Streaming or Storm >> >> > On 18 Jan 2016, at 17:19, Dood@ODDO <oddodao...@gmail.com> wrote: >> > >> > Kafka may suit your needs as a "queue" with producer/consumer and >> persistence capabilities also. >> > >> >> On 1/18/2016 9:52 AM, Murthy Kakarlamudi wrote: >> >> Hi, >> >> We have a scenario where in we have a c++ application that pumps out >> data ticks multiple times in a second. These data ticks needs to be >> displayed in the web front end. We need some middleware platform to hold >> those events temporarily before being consumed by web-front end. Can Ignite >> work as a viable middleware option in this scenario? In future we are >> expecting that there will be multiple consumers for these data ticks. Can >> Ignite Messaging be used in this scenario? >> >> >> >> Thanks, >> >> Satya. >> > >> > >
