What is the best adaptation practice for version control in a microservice architecture in terms of supporting multiple versions of deploying the same service at run time and how consumers can use different versions? 1) If we use Routing based Versioning as one of the approaches mentioned here,
then I assume that we would have the following disadvantages
- Internal services must go through a reverse proxy for consumption.
- Consumers should always be aware of the required version control.
Is it better to distribute version information to consumers?
In any case, as I believe, the following always applies:
- To change the MAJOR version, consumers must be changed.
- To change the MINOR version (backward compatibility), only the consumer (s) needing to be changed, requiring additional functionality.
- To change the PATCH version, this is optional and will probably be easy for any consumer to use.
What Microservice versioning strategy can help us resolve the above?
NOTE. Please feel free to let me know if this needs to be divided into a few questions.
source
share