In this chapter, we learned how to deal with elements that work with several microservices at the same time.
First, we talked about strategies to follow when new features need to change multiple microservices, including how to deploy small increments in an ordered fashion and to be able to roll back if there's a catastrophic problem.
We then talked about defining a clear versioning schema, and adding a version endpoint to the RESTful interfaces that allow self-discovery of the version for microservices. This self-discovery can be used to ensure that a microservice that depends on another is not deployed if the dependency is not there, which helps in coordinating releases.
The code in GitHub for the Frontend in this chapter (https://github.com/PacktPublishing/Hands-On-Docker-for-Microservices-with-Python/tree/master/Chapter11/microservices/frontend) includes a dependency...
