Verifying that microservices work without Kubernetes

In this chapter and the previous one, we have seen how features in the Kubernetes platform, such as config maps, secrets, services, and ingress resources, can simplify the effort of developing a landscape of cooperating microservices. But it is important to ensure that the source code of the microservices doesn't get dependent on the platform from a functional perspective. Avoiding such a lock-in makes it possible to change to another platform in the future, if required, with minimal effort. Changing the platform should not require changes in the source code but only in the configuration of the microservices. 

Testing the microservices using Docker Compose and the test-em-all.bash test script will ensure that they work from a functional perspective, meaning that they will verify that the functionality in...