gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
java-design-patterns/aggregator-microservices
History
Christopher O'Connell e6c71b63fc 988: Replaced all of the Apache HttpClients with Java's java.net.http (#1003) 
* 988: Took out the apache http component from root pom.xml

* 988: Updated the aggregator sub projects to use java.net.http instead of apache

* 988: Updated the api-gateway-service sub projects to use java.net.http instead of apache

* Applied the code style formatter
2019-10-15 19:14:08 +03:00
..
aggregator-service
988: Replaced all of the Apache HttpClients with Java's java.net.http (#1003)
2019-10-15 19:14:08 +03:00
etc
#190 Remove urm plugin
2017-11-28 20:55:52 +02:00
information-microservice
Update license headers
2019-10-12 20:05:54 +03:00
inventory-microservice
Update license headers
2019-10-12 20:05:54 +03:00
pom.xml
Update license headers
2019-10-12 20:05:54 +03:00
README.md
#190 Remove pumlids from readmes
2017-11-28 21:28:53 +02:00

README.md

layout, title, folder, permalink, categories, tags
layout title folder permalink categories tags
pattern Aggregator Microservices aggregator-microservices /patterns/aggregator-microservices/ Architectural
Java
Spring

Intent

The user makes a single call to the Aggregator, and the aggregator then calls each relevant microservice and collects the data, apply business logic to it, and further publish is as a REST Endpoint. More variations of the aggregator are:

  • Proxy Microservice Design Pattern: A different microservice is called upon the business need.
  • Chained Microservice Design Pattern: In this case each microservice is dependent/ chained to a series of other microservices.

alt text

Applicability

Use the Aggregator Microservices pattern when you need a unified API for various microservices, regardless the client device.

Credits