Microservices Aggregation Techniques | API Gateway, GraphQL or nothing?

Microservices architecture allow us to parallelize the implementation of different areas of our system. However, this approach introduces some challenge when we need to combine data from multiple subdomains.

The need for data aggregation is very evident in the user interface. Whether we are trying to render a dashboard or just a product listing, the information might be stored in different microservices, which means multiple API requests are necessary to render the complete view.

The main issue with concurrent API requests on the browser is performance especially in poor connections like wifi and cellular networks.

To mitigate this issue we can use the API Aggregation Pattern or create a gateway service in any language we like. Additionally, we can employ a query language like GraphQL that will also help us return just the pieces of information required by our clients.

Further optimization could be reached with gRPC. There is also hope the HTTP/3 will solve head-of-line blocking at the protocol layer once and for all!

0:00 Intro
1:12 Gateway Aggregation Pattern
2:39 GraphQL
4:44 API-First Approach
5:40 Conclusion

Connect with me:

#ddd #microservices #systemdesign #softwarearchitecture #softwaredevelopment

[MarcoLenzo]

Which Aggregation solution do you use in your projects? Let us know! 🤓🤓🤓

[powell.christopher]

Well explained. I agree with the approach of going API-First and only adding aggregation on need when you are sure you need it (you have a problem to solve). Good job on the b-roll footage as well! Made following along a much easier and enjoyable experience.

[niranjannt]

which software you used to create these awesome presentation?