Microservices are only useful if they are used. So, it’s worthwhile identifying the consumers of our microservices and how they’ll interact with our system teams. In some architectures, that could include mobile application development teams, web development teams, or even third-party organizations. In our model, the main consumer of our microservices system is the API team. The API team is responsible for exposing our microservices to other development teams as an application programming interface (API). For example, a mobile application development team would interact with the API released by this team and never
call our microservices directly.
To learn more please download this whitepaper.