Loading

Which Architecture should use for aggregator api for flight

dharmesh sharma

Hi,

I have many apis that provide same service my client want to combine and make own one. I have already implemeted these apis but i am looking some architecture so combine these apis and make one aggregatore api. so i wan to know which pattern or architecture would fit this solution so in futere i can add more apis.

thanks

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

dharmesh sharma3y ago
@Aravind Govindaraj Hi,

Thanks for your reply and answer.

That system i am already using and getting good performance but this system is design in monolithic way. If we talk about microservice my client dont want to go to cloude that request docker or kubernetes.

so i have one left only one option left to make batter architecture for Composite API pattern to increase this performace and plug in wise or make more extensible
+1
Aravind Govindaraj3y ago
Hi Dharmesh,

In this scenario we called a "Composite API pattern", your edge location will connect your single API, which acts as a point of source, and internally you will connect multiple external/internal systems.

Please find the reference for the same

https://microservices.io/patterns/data/api-composition.html
+2