Let's look at three approaches to detect and prevent breaking changes in event schemas to help you maintain backward compatibility.

TheBurningMonk's blog is a platform for sharing insights and expertise in cloud computing, serverless architecture, and distributed systems design. Through articles, tutorials, and case studies, TheBurningMonk offers insights into building scalable, resilient, and cost-effective cloud-native applications using serverless technologies. Readers can learn about architectural patterns, deployment strategies, and best practices for designing serverless applications that leverage the scalability and flexibility of cloud platforms. Additionally, TheBurningMonk provides updates on the latest developments in serverless frameworks, cloud services, and event-driven architectures to help developers stay ahead of the curve and harness the full potential of serverless computing.

theburningmonk.com

There are several approaches to preventing breaking changes in event schemas, including consumer-driven contracts, using schema packages for integration tests, and utilizing a schema registry with broker-side validation. Each method offers unique benefits and potential drawbacks, and they may even be combined for optimal effectiveness. Consumer-driven contracts help enforce expectations at the development stage, sharing event schemas as code libraries simplifies setup, and a schema registry ensures centralized governance and protection against breaking changes.

How to detect and prevent breaking changes in event schemas

2. Integration tests with schema packages

3. Schema registry and broker-side validation

Try that with the Brazilian Prince-Regent name:
<blockquote>
João Maria José Francisco Xavier de Paula Luís António Domingos Rafael de Bragança
</blockquote>
It’s fucking annoying when we, Brazilians, see that first last name shit around here =P It makes no sense whatsoever.