From Monolith to (µ)Services. What happens with my Data?

Track: Architecture
Rewriting systems from a monolithic architecture to a services architecture is a common task nowadays to make applications easier to maintain, deploy, and release. This migration should not be a big bang rewrite where you directly switch from the old application to the new one. Instead, it is an incremental process during which functionalities are extracted one at a time into separate services. The Strangler Fig Pattern describes a method whereby a new system is slowly and incrementally growing over the top of an old system. Along the way, the whole system is continuously monitored such that old parts can be removed after the new services show correct behavior. The theory is pretty clear, and in services where no persistence is needed, it's considerably easier, but things become way more complex as soon as data is involved. Come to this session to learn how Kafka and Debezium, through Change Data Capture and the Strangler Fig pattern, can help you migrate from monoliths to a (micro)services architecture confidently even though databases are involved.
Alex Soto
Alex Soto is a Director of Developer Experience at Red Hat. He is passionate about the Java world, software automation and he believes in the open-source software model. Alex is the co-author of Testing Java Microservices and Quarkus cookbook books and contributor to several open-source projects. A Java Champion since 2017, he is also an international speaker and teacher at Salle URL University. You can follow him on Twitter (@alexsotob) to stay tuned to what’s going on in Kubernetes and Java world.