Kafka – Managing Breaking Changes in a Multi-Team Environment

In my article Kafka Versioning I have briefly covered different ways of handling versions and using schemas to manage changes to the data structures. However, merely understanding these concepts falls short when operating within an environment characterized by numerous teams and bounded contexts. It is necessary to identify patterns and principles for navigating model changes successfully.

Navigating Kafka: Strategies for Managing Schema Changes

I have worked with DDD for many years, and learned to not share databases and to use anti-corruption layers between systems and services. Therefore, I was at first very reluctant to connect Kafka directly to the databases. Wouldn't that recreate the monolith that we have been working so hard to get rid of?