In this video, learn how to use asynchronous messaging to solve for data migration when moving to microservices architectures.
- [Instructor] One of my first uses … I was building a new and improved version … of a single domain model … as I was helping my company move … from Monolith and SOAP. … Part of my task was to isolate and migrate the data … without system impact. … The design that I created and used … was based on asynchronous messaging. … from an all encompassing database … This is often a core part of a microservices migration … which, again, is where I first encountered it. … The migration, however, isn't just about moving data. … The key for me, was that I had to cut over … to the new system without a noticeable downtime. … I had a very small window of scheduled downtime … to deploy new code but not nearly enough to move the data … so I had to build a migration plan … that started months before the actual code deployed. … Orchestration is often used for its reliability … and the ease of use in an event driven system … like a database write. … Now, before we jump in the model, … we have a few things that we need to consider first. …
- Gains and tradeoffs of asynchronous communications
- Use cases for interservice communication patterns
- Event-driven microservices
- Use cases for choreographed and orchestrated events
- Streaming data platforms
- Data flows, migration, and synchronization