The implementation mechanism of microservices emphasizes the emphasis of microservices that you keep the deployment separation and the none-to-minimal dependencies on other external resources outside this microservice boundary. A microservice is cohesive within itself, and because it's autonomous, it's best to deploy each microservice in its own separate container. This makes it easy to deploy and easy for the tools to manage deployment.

Each container creates its own boundary around the microservice, and this enables a number of microservices to coexist, and to serve the business without affecting each other beyond their boundaries.

For simplicity, a container can be considered as a tiny VM running a stripped-down version of OS.

Deploying a microservice in the container also enables a simpler and flexible way to enable the scaling for your microservice. (Note that we will cover more on containerization in the last chapter.)