Skip to content
About
Main content

The schema registry as metadata

Why can schema lookups be cached forever, and what general principle does that show?

A stores the schema (field names and types) of messages, giving each version an ID. Unlike most , it is load-bearing at read time: a consumer cannot decode a message without the schema, so the registry sits in the data path, and its availability is a schema-evolution concern. What belongs here is why the usual fix is safe. Consumers schemas aggressively, and the cache is correct for free, because schema IDs are : an ID never maps to a different schema. So the cache never needs , and its time-to-live () can be infinite.

This is a general and underused principle:

That is the whole reason schema IDs are not schema names. A name can be re-pointed to a new schema; an ID cannot.