July 2017
Intermediate to advanced
414 pages
11h 18m
English
When we allow services to evolve, one of the important aspects to consider is service versioning. Service versioning should be considered upfront, not as an afterthought. Versioning will help us to release new services without breaking existing consumers. Both the old and the new versions will be deployed side by side.
Semantic versions are widely used for service versioning. A semantic version has three components, MAJOR.MINOR.PATCH, where MAJOR is used when there is a breaking change, MINOR is used when there is a backward compatible change, and PATCH is used when there is a backward compatible bug fix.
Versioning could get complicated when there is more than one service in a microservice. It is always ...
Read now
Unlock full access