Muthu, >>2. With Ignite/Web Console, if a DB table insert/update/delete operation were to happen to the database directly is there a way to have that automatically picked up into the cache (so its always in sync with the DB tables)? >> I know this is too much to ask. I ask because we currently have code which uses MyBatis as ORM to read/write to PostgreSQL DB & i need to build a cache without trying to integrate with MyBatis which is problematic. >> I have some tools in mind & things like messaging based loads, etc to try but if Ignite does this with some integration that would be great.
First of all, I would like to state that it is not correct mix Ignite and Web Console in this context. Web Console - is just an *EXTERNAL tool*. It could generate some code for you and also allows to execute some Ad-hock SQL queries and monitor your cluster. That's all. Second, there only one way to have caches and DB in sync - do ALL data modifications via Ignite caches only. And configure caches to write-through to your DB. So, you should directly use Ignite as DB -> configure your ORM to work with Ignite as with DB via Ignite JDBC driver. And configure caches to write-through to your DB. -- Alexey Kuznetsov
