diff --git a/aggregator-microservices/README.md b/aggregator-microservices/README.md
index 2d1e63529..732129e17 100644
--- a/aggregator-microservices/README.md
+++ b/aggregator-microservices/README.md
@@ -3,6 +3,7 @@ title: Aggregator Microservices
 category: Architectural
 language: en
 tag:
+- API design
 - Cloud distributed
 - Decoupling
 - Microservices
@@ -10,15 +11,13 @@ tag:
 
 ## Intent
 
-The user makes a single call to the aggregator service, and the aggregator then calls each relevant microservice.
+Streamline client's interactions with system's microservices by providing a single aggregation point that consolidates data and responses from multiple services. This simplifies the client's communication with the system, improving efficiency and reducing complexity.
 
 ## Explanation
 
 Real world example
 
-> Our web marketplace needs information about products and their current inventory. It makes a call to an aggregator
-> service which in turn calls the product information microservice and product inventory microservice returning the
-> combined information. 
+> Our web marketplace needs information about products and their current inventory. It makes a call to an aggregator service, which, in turn, calls the product information and product inventory microservices, returning the combined information.
 
 In plain words
 
@@ -36,7 +35,7 @@ Let's start from the data model. Here's our `Product`.
 public class Product {
   private String title;
   private int productInventories;
-  // getters and setters ->
+  // Getters and setters omitted for brevity ->
   ...
 }
 ```
@@ -94,14 +93,39 @@ curl http://localhost:50004/product
 
 ## Class diagram
 
-![alt text](./aggregator-service/etc/aggregator-service.png "Aggregator Microservice")
+![Class diagram of the Aggregator Microservices Pattern](./aggregator-service/etc/aggregator-service.png "Aggregator Microservice")
 
 ## Applicability
 
-Use the Aggregator Microservices pattern when you need a unified API for various microservices, regardless the client device.
+The Aggregator Microservices Design Pattern is particularly useful in scenarios where a client requires a composite response that is assembled from data provided by multiple microservices. Common use cases include e-commerce applications where product details, inventory, and reviews might be provided by separate services, or in dashboard applications where aggregated data from various services is displayed in a unified view.
+
+## Consequences
+
+Benefits:
+
+* Simplified Client: Clients interact with just one service rather than managing calls to multiple microservices, which simplifies client-side logic.
+* Reduced Latency: By aggregating responses, the number of network calls is reduced, which can improve the application's overall latency.
+* Decoupling: Clients are decoupled from the individual microservices, allowing for more flexibility in changing the microservices landscape without impacting clients.
+* Centralized Logic: Aggregation allows for centralized transformation and logic application on the data collected from various services, which can be more efficient than handling it in the client or spreading it across multiple services.
+
+Trade-offs:
+
+* Single Point of Failure: The aggregator service can become a bottleneck or a single point of failure if not designed with high availability and scalability in mind.
+* Complexity: Implementing an aggregator can introduce complexity, especially in terms of data aggregation logic and error handling when dealing with multiple services.
+
+## Related Patterns
+
+* [API Gateway](https://java-design-patterns.com/patterns/api-gateway/): The Aggregator Microservices pattern is often used in conjunction with an API Gateway, which provides a single entry point for clients to access multiple microservices.
+* [Composite](https://java-design-patterns.com/patterns/composite/): The Aggregator Microservices pattern can be seen as a form of the Composite pattern, where the composite is the aggregated response from multiple microservices.
+* [Facade](https://java-design-patterns.com/patterns/facade/): The Aggregator Microservices pattern can be seen as a form of the Facade pattern, where the facade is the aggregator service that provides a simplified interface to the client.
 
 ## Credits
 
 * [Microservice Design Patterns](http://web.archive.org/web/20190705163602/http://blog.arungupta.me/microservice-design-patterns/)
 * [Microservices Patterns: With examples in Java](https://www.amazon.com/gp/product/1617294543/ref=as_li_qf_asin_il_tl?ie=UTF8&tag=javadesignpat-20&creative=9325&linkCode=as2&creativeASIN=1617294543&linkId=8b4e570267bc5fb8b8189917b461dc60)
 * [Architectural Patterns: Uncover essential patterns in the most indispensable realm of enterprise architecture](https://www.amazon.com/gp/product/B077T7V8RC/ref=as_li_qf_asin_il_tl?ie=UTF8&tag=javadesignpat-20&creative=9325&linkCode=as2&creativeASIN=B077T7V8RC&linkId=c34d204bfe1b277914b420189f09c1a4)
+* [Building Microservices: Designing Fine-Grained Systems](https://amzn.to/43aGpSR)
+* [Microservices Patterns: With examples in Java](https://amzn.to/4a5LHkP)
+* [Microservice Architecture: Aligning Principles, Practices, and Culture](https://amzn.to/3T9jZNi)
+* [Production-Ready Microservices: Building Standardized Systems Across an Engineering Organization](https://amzn.to/4a0Vk4c)
+* [Designing Distributed Systems: Patterns and Paradigms for Scalable, Reliable Services](https://amzn.to/3T9g9Uj)