After you migrate from an existing graph database to Amazon Neptune, you might want to capture and process changed data in real time. Continuous replication of databases using the change data capture technique allows you to unlock your data and make it available to other systems for use cases such as distributed data processing, building an enterprise data lake, and modernizing your existing database. In the previous post of this series, we demonstrated with an example solution, how to perform automated migration from Neo4j to Amazon Neptune. If you are looking beyond one-time migration and want to keep both databases in sync you might want to run an ongoing replication using the change data capture technique.
