It is tempting to skip using a Schema Registry when you are moving fast. "Just send JSON," you tell yourself. "Formal schemas can come later."
That decision usually comes back to bite you - not all at once, but incrementally, over weeks and months.
The Costs
Every change becomes a potential incident. Without a contract between producers and consumers, ordinary development work - renaming a field for clarity, correcting a type, adding a required field - becomes a potential production failure. The change seems safe from the producer side. The breakage appears hours later in a consumer error log, after real data has already been processed incorrectly.
Consumer code becomes defensively paranoid. Teams adapt to unpredictable message formats by adding defensive checks everywhere: does this field exist? Is it the type I expect? What is the fallback if the field is missing? This defensive code is fragile, difficult to test exhaustively, and grows with every format variation. It never gets cleaned up because cleaning it up requires trust in the message format that does not exist.
Onboarding new developers is harder. Without a registry, the authoritative description of what your events look like is scattered across producer code, consumer code, old documentation, and the memories of people who have been on the project long enough to remember the decisions. New developers learn the hard way, through failures.
Silent corruptions are the worst. The failures that produce noisy errors are frustrating but diagnosable. The failures that produce silently wrong results - events that parse without error but carry subtly incorrect data because a field changed meaning - are much worse. These can persist for days before anyone notices the downstream effect in memory quality or answer accuracy.
The Real Calculation
A Schema Registry adds modest setup overhead once. The absence of one adds ongoing maintenance overhead indefinitely. The break-even point comes much sooner than most people expect.
If you are serious about building a reliable event-driven system at any meaningful scale, a Schema Registry is not optional infrastructure - it is the baseline.