Sharing the wealth, socialising Kafka event sources in an organisation
summary
Implemented an AsyncAPI catalog and portal that publishers use to document Kafka topics, generate client stubs and sample code, and let teams discover existing event sources instead of rebuilding them. Documents map schema format + content type to infer serializers but surface ambiguity, prompting proposals for bootstrap servers grouping and a dedicated Kafka binding to declare serializer encodings. Also documents vendor differences in schema registries (Confluent style magic byte vs headers) and points to issue 65 for spec changes.
AI-written summary · about
chapters (7)
- 0:00Start
- 12:13Payload Encoding
- 17:22Schema Registries
- 19:06Approaches To Embed the Schema Id Information in a Kafka Message
- 19:35Embedding the Schema Id in the Record
- 20:37Record Headers
- 22:01Summary
related talks
45mManage, secure, and socialize Kafka topics
01h 00mKafka as a Platform: the Ecosystem from the Ground Up
41mKafka as a Platform: The Ecosystem from the Ground Up
39mKafka as a Platform: The Ecosystem from the Ground Up
01h 00mKafka as a Platform: the Ecosystem from the Ground Up
26mKafka in the Wild
39mIntroduction to AsyncAPI for Apache Kafka
38mStreaming with Structure