Have a service that acts as the sole entry point into a microservices-based application
Consider a mobile shopping application. The product information that it needs to show to the user includes the description, price, reviews, recommendations and shipping information. The ownership of that data is spread among a number of microservices. In theory, the application could access each microservice separately. But in practice, it makes more sense for the mobile application to retrieve the needed information by making a single request to a service known as an API Gateway, which aggregates data from multiple services.
For a full description of this pattern see the API Gateway Pattern.