From Guesswork to Governance: Bringing API Discipline to Data Streaming
summary
Claim: move validation upstream so producers can’t write poison data and consumers can trust event formats. Uses schema registry (stored in Kafka), schema-aware serializers that check compatibility and block incompatible writes, and popular formats like Apache Avro (also supports Google Protobuf). Demo registers a schema in Confluent Cloud, produces 10 events, bumps a major schema version, registers upgrade/downgrade transforms, and consumers successfully read v1 events as v2, proving evolution and enforcement work.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:30APIs need standards
- 5:57Kafka’s byte storage
- 8:51Fire-and-forget without contracts
- 10:57Schema evolution and governance
- 13:23Schema registry as truth
- 17:54Schema-aware serializers
- 19:59Live demo: schema evolution
- 25:02Q&A
related talks
38mStreaming with Structure
23mEver Changing Data Model Schema Management For The Future
31mOne Data Pipeline to Rule Them All
01h 00mEvolving Your Kafka Architecture With Schema Registry
43mFrom Tower of Babel to Babel Fish: Evolving Kafka Architecture With Schema Registry
39mMoving Beyond Moving Bytes
29mHigh-Quality Performant and Cost Efficient Schema-Aware Data Streams on Flink at Netflix Scale
23mThe Enterprise Guide To Building A Data Mesh
