Spring for Apache Kafka and Protobuf Part 1: Event Data Modeling

What this post added

This post introduces three event modeling approaches for event-driven architectures: 'bare letter', 'deep envelope', and 'shallow envelope'. It details the advantages and disadvantages of each, focusing on aspects like schema overlap, consumer effort, data quality, maintainability, and compatibility checks. The 'bare letter' approach offers independence but risks schema overlap and increased consumer effort. 'Deep envelope' standardizes metadata for generic processing but adds complexity. 'Shallow envelope' provides flexibility with schema-on-read but defers risk to runtime and can lead to code duplication. The post also touches upon the use of Protobuf and Spring for Apache Kafka in conjunction with Confluent Schema Registry for implementing these models.