BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//sf26-agenda//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
BEGIN:VEVENT
UID:SESS-150@sf26-agenda
DTSTAMP:20261020T151709Z
DTSTART:20261104T210000Z
DTEND:20261104T214500Z
SUMMARY:Your Apache KafkaⓇ Topics Are APIs - Treat Them Like It
LOCATION:Room 2006
DESCRIPTION:Sandon Jacobs\n\nWould you build a REST API and make users gues
 s the request and response formats? What's the domain model? Name the oper
 ation… POST? GET? PUT? PATCH? What does this error code even mean? Is th
 e documentation - if it even exists - accurate and relevant? Yet that's ex
 actly what many data streaming deployments do. Apache Kafka's flexible\, u
 nopinionated serialization is a huge strength\, but it's also a potential 
 risk. Even if your event streams carry structured data\, enforcing that st
 ructure\, managing its evolution\, and validating its contents aren't hard
  requirements. This leaves consumer applications preprocessing every event
  - even ones with no business value. Designing structured events with a sc
 hema (Apache Avro and Google Protobuf) models your business domain and pro
 motes safe evolution practices. Schema-aware serializers enforce event str
 ucture before it's written to the stream\, while consumers leverage those 
 shared schemas to deserialize on the other end. Build-time validation catc
 hes schema problems before code ever reaches review - one last line of def
 ense against poison data. Through all of it\, the goal is the same: treat 
 your Kafka topics with the same rigor you'd apply to any API contract - be
 cause that's exactly what they are. Join us to learn how to move validatio
 n upstream - transforming your event streams into data consumers can actua
 lly trust\, with a practical blueprint for schema integrity and automated 
 evolution.
URL:https://sf26.rmoff.net/s/your-apache-kafkar-topics-are-apis-treat-them-
 like-it-150
END:VEVENT
END:VCALENDAR