You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2017/06/28 23:12:00 UTC

[jira] [Created] (IGNITE-5610) MySQL Time Machine and Ignite Integration

Denis Magda created IGNITE-5610:
-----------------------------------

             Summary: MySQL Time Machine and Ignite Integration
                 Key: IGNITE-5610
                 URL: https://issues.apache.org/jira/browse/IGNITE-5610
             Project: Ignite
          Issue Type: Task
            Reporter: Denis Magda


There are scenarios when a relational database like MySQL is used as a persistent store by Ignite and, at the same time, the database is being updated directly by some other application.

This happens when a company migrates from a pure RDBMS based architecture to Ignite as a primary in-memory storage. During the migration, some of the applications might already work with Ignite (which will keep MySQL in sync) while the others can still interact with MySQL directly.

If this is the case, then there has to be a way to propagate all the updates happened at MySQL level and caused by direct application calls to Ignite. As one of the solution, Ignite can be integrated with MySQL Time Machine that can send all such updates to the cluster.
https://mysql-time-machine.github.io

Read more in this discussion on the dev list:
http://apache-ignite-developers.2346864.n4.nabble.com/Re-External-Re-Triggering-cache-updates-in-Ignite-td19193.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)