Dealing with stateless code is easy, but it gets much harder when you have to deal with persistent state. In this case, zero-downtime migrations are paramount to guarantee integrity and consistency. Of all the microservices characteristics, the one that creates the most perplexity is the “one database per microservice.” However, very few teams have the privilege of starting something from scratch—most often they have a legacy database that will need to survive any new implementation.
In this webinar learn how these techniques (and others) relate to each other in many integration and evolution strategies for relational databases:
- Strong and eventual consistency
- Create, read, update, and delete (CRUD)
- Command and query responsibility segregation (CQRS)
- Event sourcing
- You'll leave having strategies to help you build up a microservices architecture from a legacy monolithic relational database.
- Edson Yanaga, Director, Developer Experience, Red Hat
Date: April 4, 2017
Time: 11 a.m. EST
Length: 60 min