Applications start to become legacy at the point that their data model is not evolving anymore! Even though there are countless books and articles describing how to manage and refactor the code base using patterns like Strangler Fig and Branching by Abstraction, this session is about how to liberate your data model. A software without data is like a joke without a punchline, leaves you hanging.

I’ve seen firsthand how crucial it is to have a robust plan for data migration, working on projects where we faced this exact problem, the code migration was progressing smoothly, but our legacy data model held us back. It was a pivotal moment that made me realize: without effectively addressing data migration, no amount of code refactoring or system redesign would suffice. While there are numerous approaches offering data integration between systems, whether it is a shared database or having separate data stores and implementing Change Data Capture using Debezium or Kafka, the real challenge is left to the reader; listen to your environment and choose which approach fits your situation better.

Throughout this session, we will examine different patterns that can be leveraged to liberate data in your system and allow it to flow seamlessly. We will examine the advantages and disadvantages of each approach and discuss tools we could employ to achieve this goal. By the end of this session, you will be better equipped to make informed decisions about how to migrate and synchronize data in your software applications.