API Composition Pattern in Microservices

[@AlgorithmDecoded]

Very clean, summed up everything in one place. Tho i know about composition and API gateway but I have not seen anyone covering these many challenges with API Gateway. 👏

[@Bluesky-rn1mc]

Thank you Arpit, can you also talk about design patterns in coming videos ?

[@SudhanshuShekhar6151]

Thanks again! I am learning new things just by seeing your videos.

[@matrixtoogood5601]

From what I understand, Python has parallelism (can use multiple cores) but it does not have support for true concurrency like Go (due to global interpreter lock) so only 1 thread gets executed per core.

[@ishandhar2851]

Python has GIL, so the application an have only one thread running at a time. That means only one core can be used

[@matrixtoogood5601]

@@ishandhar2851 That's not true. I have used multiprocessing on multi-core VMs using Python. The only limitation is 1 real thread per core.

[@DurgaShiva7574]

An amazing video, by an amazing teacher. have some questions though : - 1. Why the composer isn't a Single point of failure, and just a bottleneck, cannot get it, as per me, it should had been a SPoF 2. If we use a composer or doesnt use it, the number of network calls remains same right?.. only thing is the complexity is transferred from client to the composer, but, the number of network calls, thus, the latency should remain same right ? 3. there would be may clients which are calling the same composer, so as to keep a track of all the responses of different microservices, then filtering them, and finally concatinating the one which are from a same user, will increase the latency right ?... then composer makes system slow...or anything which i am missing ?

[@kgck15]

The best videos on internet. Couplebof questions. Should it always be api gateway or can it just be another microservice taking the ownership of only those APIs that needs compositions. 2). This is most common use case as we split microservices and when gui needs to show something in an particular way that needs composition. This leads to latency in gui display, is there any pattern or anything to handle such cases to avoid latency. 3) since its api gateway do these gateways have extentions capability where we can write our composition in them ?

[@ebrahimmansur9815]

why not have a sperate components that fills the reasonability of aggregation of a read model from an infrastructure that stores the events from 3 services [order, payment, logistic ]

[@harshpatel105]

Awesome stuff as always, Arpit

[@Aditya-us5gj]

Though we have distributed system but looking at the disadv. of API gateway(composer), can I say that it's making my system a single point of failure ? Also isn't it going to make our system very very complex if we add mutiple API gateways to remove this single point of failure ?

[@ravividap1227]

Can we say it's facade pattern applied at service level instead of class/obj level?

[@AsliEngineering]

Yes.

[@cris_crizon]

Está bueno el video, gracias!

[@chessmaster856]

One of the service down would be the first line as soon as you talk about multiple services not after half an hour

[@hyrdeshgangwar]

Good Stuff!

[@theSeniorSDE]

Thanks Arpit for sharing and making things easy to understand for us. What all resources or books do you follow to learn things in such detail. Please share.

[@AsliEngineering]

Most of it comes from experience. But I have been reading since a long time and have been collecting all the info in one place. Sam Newman has a great book on Microservices if you'd want to explore.

[@theSeniorSDE]

@@AsliEngineering Thanks

[@mutasimahmed8975]

where do i learn about the prereqrusites for your course ?

[@AsliEngineering]

There on the course page ArpitBhayani.me/masterclass

[@mutasimahmed8975]

@@AsliEngineering thnx

[@tuzlityreyansh5154]

useful

[@ArinSinabian]

kzbin.info/www/bejne/a6G8fZ-PqN5pnLM To me that seems to be a distributed monolith