ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Pulsar's built-in schema registry enforces compatibility at the broker, turning schema evolution from a production incident into a controlled operation. Here's how the policies work and where they bite.
Schema drift corrupts streaming data silently. Pulsar's built-in schema registry enforces compatibility broker-side — here's how it works, an Avro example, and the trade-offs.
Context A team must add a required field to an Avro schema used by Kafka producers and consumers. The deployment must be zero-downtime: producers and consumers cannot be upgraded in a coordinated cutover. Confluent Schema Registry enforces compatibility at registration time, and the default TRANSITIVE validates against all prior versions. Constraint The new
apachekafka