diff --git a/src/data/roadmaps/graphql/content/100-graphql-introduction/101-problems-graphql-solves.md b/src/data/roadmaps/graphql/content/100-graphql-introduction/101-problems-graphql-solves.md
index d1c615a75..620bf0949 100644
--- a/src/data/roadmaps/graphql/content/100-graphql-introduction/101-problems-graphql-solves.md
+++ b/src/data/roadmaps/graphql/content/100-graphql-introduction/101-problems-graphql-solves.md
@@ -9,3 +9,5 @@ GraphQL solves several problems commonly faced when building APIs, including:
 - **Inefficient versioning:** With REST, creating a new endpoint for each version of an API can quickly become cumbersome and hard to maintain. GraphQL allows for seamless versioning by adding new fields and types, rather than creating new endpoints.
 
 - **Lack of flexibility:** REST APIs are typically fixed, meaning that the client has to work with the data structure provided by the API. GraphQL allows the client to request exactly the data it needs and receive it in a predictable format, increasing flexibility.
+
+- **Microservice communicating** with Federation or Supergraph implementation you can easily query data from multiple microservice in one single query without code overhead or request overhead (if nothing requested from one microservice it wouldn't make a real network request for this data)