Skip to main content


Since microservices are designed to be autonomous and loosely coupled, it is very important to include all the dependencies with them so that they can be easily deployed.

If the microservices need to communicate to external services, then these should communication details shoul not be hard-code and should be designed such that they are fail safe. This is because microservices can be easily evolved and deployed multiple times.

If we deploy another instance of the same microservice in another subnet, or network, we expect the settings and communication protocol to call the external services to be configurable so that we can configure our new instance of the microservice as needed.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!