Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ : Client / Server Version Compatibility #410

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

codesplode
Copy link

Add a question to handle client server version compatibility. I think NATS' compatibility model is awesome and this handles a lot of the major concerns.

Add a question to handle client server version compatibility. I think NATS' compatibility model is awesome and this handles a lot of the major concerns.
@codesplode
Copy link
Author

Additional Note regarding compatibility....

If possible and project maintainers agree, I do think many developers including myself would like a simple rule to help guarantee compatibility in apps in addition to this, even if it suggests a more limited compatibility overall. This would also allow NATS to keep its broad compatibility, but be able to handle unforeseen future features that might be more complex or costly to feature flag in the protocol or allow you to cleanup and deprecate / remove some of those signals over time. Here's an example / template of what I might suggest adding to the beginning or end of this content to keep the benefits of this model, while also providing a simple rule:

For those looking for a simple guarantee regarding NATS version compatibility, we recommend keeping NATS client and server versions within the same major version when possible for the greatest feature parity / stability guarantee (client 2.x.y / server 2.a.b). The NATS team can only guarantee this with NATS maintained clients of course.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant