Re: Two persistent data stores for a single Ignite cluster - RDBMS and Ignite native

[Ray <ra...@cisco.com>]

Hi Slava,

Thanks for the reply, I have the same doubt.

One more question here, how can a update or new inserts back-propagate to 
Ignite when another application(not ignite) writes to 3rd party persistence? 

For example, Ignite and 3rd party persistence both have one entry for now. 
When another application adds an entry to 3rd party persistence, now 3rd
party persistence has two entries. 
Can Ignite be notified and load the newly added entry automatically? 

From the document, it looks like the data can only be propagated from Ignite 
to persistence, not the other way around. 




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Two persistent data stores for a single Ignite cluster - RDBMS and Ignite native

["slava.koptilin" <sl...@gmail.com>]

Hi Naveen,

Yes, you are right. Apache Ignite does not provide that functionality out of
the box.
However, it can be implemented. Please check this article: 
https://dzone.com/articles/syncing-a-gridgain-in-memory-computing-cluster-and

Thanks!



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/