Replies: 1 comment 2 replies
-
Hey! The schema registry can have multiple versions of the schema, and that's fine as long as the versions are compatible with each other. Publishing with a different version should not be dangerous if you're following the rules (and in fact, you can set up the schema registry to error out if you even try to publish an incompatible change, which I highly recommend). I'm a bit less inclined to support the workflow you suggest here because it takes the power out of the hands of the producing service, which should know what it needs to produce. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The Schema Registry is not considered the source of truth.
Deimos currently not only reads but also writes against the schema registry, based on the files found locally.
This can be particularly dangerous in case someone with an outdated schema attempts to produce a message because it will effectively roll back the schema version in the schema registry to an older one.
We would like to limit deimos to only read from the schema registry and use that during the validation of a message (e.g. compare the auto-generated ruby class and warn when the application is producing using an outdated schema) without updating the schema registry in the process
Beta Was this translation helpful? Give feedback.
All reactions