What are the design approaches of Microservices?

Few Microservices design patters are –
1) Aggregator Microservice design pattern- Aggregator would be a simple web page that invokes multiple services to achieve the functionality required by the application
2) Proxy design pattern – Different Microservices may be invoked based upon the business need. You may like to do this where each individual service need not be exposed to the consumer and should instead go through an interface.
3) Chained microservice design pattern produce a single consolidated response to the request. In this case, the request from the client is received by Service A, which is then communicating with Service B, which in turn may be communicating with Service C. All the services are likely using a synchronous HTTP request/response messaging.
4) Asynchronous Messaging Microservice Design Pattern- Some microservice architectures may elect to use message queues instead of REST request/response because of that. A combination of REST request/response and pub/sub messaging may be used to accomplish the business need.
5) Shared Data Microservice design pattern- Even if only a SQL database is used in the monolithic application, denormalizing the database would lead to duplication of data, and possibly inconsistency. In a transition phase, some applications may benefit from a shared data microservice design pattern.
In this design pattern, some microservices, likely in a chain, may share caching and database stores. This would only make sense if there is a strong coupling between the two services.