Austin, There are 2 ways I see being implemented in prod for CDC from an RDBMS to Ignite:
- Set triggers on the RDBMS end and push changes to a streaming pipeline such as JMS. Have JMS (or other technology) to stream changes straight to Ignite. - Use Oracle Golden Gate integration of GridGain which supports SQL Server [1]: https://docs.gridgain.com/docs/goldengate-replication The first option is free, the second is paid. You won't have any troubles with CDC to Ignite if the latter is used for reads only or there will be no conflicts in updates on Ignite and RDBMS ends. If the conflicts are possible then you need to come up with a conflict resolution strategy. - Denis On Thu, Mar 28, 2019 at 7:29 AM Ilya Kasnacheev <[email protected]> wrote: > Hello! > > This is impossible in general, since databases do not have uniform push > API. Moreover it is tricky WRT transactional changes. > > It may be possible for specific database (triggers, etc), but you will > have to implement the bulk of logic, or maybe use a 3rd party solution. > > Regards, > -- > Ilya Kasnacheev > > > чт, 28 мар. 2019 г. в 13:55, austin solomon <[email protected]>: > >> As per my knowledge by enabling writeThrough any updates to the cache >> will be >> reflected to its underlying RDBMS tables. >> >> Whereas we want the other way, updates in RDBMS table should be reflected >> in >> cache. >> >> Thanks, >> Austin >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> >
