► LEARN MORE: https://cnfl.io/microservices-101-module-1

Schema evolution is the act of modifying the structure of the data in our application, without impacting clients. This can be a challenging problem. However, it gets easier if we start with a flexible data format and take steps to avoid unnecessary data coupling. When we find ourselves having to make breaking changes, we can always fall back to creating new versions of our APIs and events to accommodate those changes.

Check out the Microservices 101 course on Confluent Developer for more details: https://cnfl.io/microservices-101-module-1

RELATED RESOURCES
► Schema Evolution and Compatibility: https://cnfl.io/49Pi4ER
► Schema Evolution: https://cnfl.io/3TiqaPh
► Schema Registry: https://cnfl.io/3TvSpv8

CHAPTERS

00:00 - Intro

00:16 - What is a schema?

00:45 - Do schemaless formats need to evolve?

01:22 - What is schema evolution?

02:06 - How does the data format impact schema evolution?

02:37 - What is a forward-compatible schema?

03:01 - What is a backward-compatible schema?

03:40 - How do we version our APIs and Events?

04:15 - Should my APIs use shared libraries?

05:23 - How can I advertise my schema changes?

05:52 - Closing

ABOUT CONFLUENT
Confluent is pioneering a fundamentally new category of data infrastructure focused on data in motion. Confluent’s cloud-native offering is the foundational platform for data in motion – designed to be the intelligent connective tissue enabling real-time data, from multiple sources, to constantly stream across the organization. With Confluent, organizations can meet the new business imperative of delivering rich, digital front-end customer experiences and transitioning to sophisticated, real-time, software-driven backend operations. To learn more, please visit www.confluent.io.

#microservices #apachekafka #kafka #confluent