Hi Val Thank you for responding to my post. I agree with the idea of using Ignite for both read/write through cache. However in my application, writes to persistent store happens through a different application.
My application is a reporting application, where I need to stream the data, apply computation logic and generate reports for a current day data. could you advise me in this scenario. -Srini On Mon, Nov 7, 2016 at 6:25 PM, vkulichenko [via Apache Ignite Users] <ml-node+s70518n8757...@n6.nabble.com> wrote: > Hi Srini, > > I'm not sure I understood your use case. Are you updating the database > directly and want the cache to be updated automatically? Generally, this is > not how Ignite is designed. You should use Ignite API for both reads and > writes to make sure that the cache is consistent with the store. > > -Val > > ________________________________ > If you reply to this email, your message will be added to the discussion > below: > http://apache-ignite-users.70518.x6.nabble.com/Need-help-on-the-data-streaming-tp8714p8757.html > To unsubscribe from Need help on the data streaming., click here. > NAML -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Need-help-on-the-data-streaming-tp8714p8788.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
