[Verse 1] In Kubernetes where Kafka streams We need more than just the data flowing Schema Registry joins the scene To keep our message structure growing Apicurio or Confluent's way Both can serve your validation needs Deploy them right beside Strimzi And watch your data quality succeed [Chorus] Register, validate, evolve with care Avro, Protobuf, JSON everywhere Backward, forward, full compatibility Schema Registry brings reliability Version control for every message sent Evolution without breaking what was meant [Verse 2] Avro brings us binary tight Compact serialization strong Schema first approach feels right Code generation tags along Protobuf from Google's land Language neutral, fast and clean While JSON Schema takes a stand For readable validation schemes [Chorus] Register, validate, evolve with care Avro, Protobuf, JSON everywhere Backward, forward, full compatibility Schema Registry brings reliability Version control for every message sent Evolution without breaking what was meant [Bridge] Backward compatibility reads the old Forward compatibility writes the new Full means both directions hold None means breaking changes through Transitive checks the chain complete From version one to latest state Your schemas never skip a beat When evolution rules you create [Verse 3] Deploy Registry in the same namespace Network policies keep it secure Service discovery finds its place Through Kubernetes DNS for sure Schema subjects organize your types Version numbers track each change Consumer groups avoid the gripes When schemas shift within their range [Chorus] Register, validate, evolve with care Avro, Protobuf, JSON everywhere Backward, forward, full compatibility Schema Registry brings reliability Version control for every message sent Evolution without breaking what was meant [Outro] From producer to consumer flow Registry stands between Ensuring that the data show Stays valid, typed, and clean
← 2 Kafka Bridge (HTTP API) | 4 Kafka Streams & ksqlDB on Kubernetes →