MICROSERVICES ARCHITECTURE | API GATEWAY | PART - 5 

Who downvoted this - everything this guy does is gold!

One of the best tech teaching videos I’ve seen on RU-vid.

I enjoyed most of your videos, However I have to say API Gateway concept which you explain here is not 100% correct. 1. API Gateways main purpose is to help in RAD (Rapid App Development). Team can creates microservices and security part which is the most time consuming and complex part (and keep changing) will be handle by API Gateway. 2. API Gateway will keep a check on abuse of any api by having a rate limit. Security is the biggest reason why API Gateway becomes so important. Combining multiple microservice call into one call will take away all the advantage what microservice has to offer and I respectfully disagree with that part. Great work, however I feel you might have to revisit this video.

I had such a time struggling with the concept of why API gateways were needed. This answered so many of my questions, and was super clear. Thank you so much, I'm learning so much from watching your videos!

I think API gateway is for some features like routing, security. It doesn't combine the response from multiple microservices as what if there is error in one microservice? the whole response will be affected. Example payment service is down but search and rest services are working.

So much gold in just this one video. This series is amazing

BFF good way to add humor to the presentation 🙂 thanks for putting this together, keep up the good work!

Good one. And it's crystal clear. Keep continuing the great work

Excellent clarity in explanation , Thank you so much 👍

You made it very simple mate...thanks and keep making up the vids on microservices!

Thanks for the video, very informative

Thank you so much, Very clear understanding of API Gateway.

I learned so much from your channel. Thank you!

I think API gateways should be kept behind LoadBalancers instead of them itself acting as a load balancer. That way API gateway can communicate with microservices independently instead of managing load as well.

Great video! Nice and concise.

Thank you! You are a very good teacher

Hi Sir please make a video on api gateway and service discovery, where they sit in the architecture and how they are used with one another

Loved the video, Thank you so much

amazing the best explanation about the subject

Where have you been for the past weeks, can't be this same RU-vid, me struggling with role based acl, and how the other services would take care of that, i could have just jettisoned the api functionality of proxying request to the services and bring those routes to the gateway and use the services as needed on that business process. wow

Woww amazing explaination thankyou

I liked the 'Best Friend Forever' analogy it's more 'Best F*ck Friend' lmao xD

Thank you so much, you sir have helped a lot of people. Great explanation.

Great video series !!!!

Great explanation of ideas. Thanks so much :D

Thanks Bro.. Very useful information at a high level.

Amazing ! Could this be added as a disadvantage of API Gateway that we cannot monitor the health of the API Gateway easily?

Thank you so much, awesome explanation 👍

would another consequence be the face that its a single point of failure? if so how do we work around that? my guess is to have multiple replicas? thank you so much for your videos

Thanks for wonderful vedios on microservices. Have a question how exception handling work in microservices? Suppose data updated by 2 microservices in DB and then third microservice failed???

fantastic demo!! Thank you!

Thanks for the knowledge

Does API Gateway do network traffic balancing like load balancer or do you need that along with API Gateway?

Wonderfully explained! 👍

Great explanation.

one question- if a common API gateway is there to use multiple BE services(for exp-lambda) then how would this API gateway manage the load since it has a limit call/sec- 10k ? cant we use a separate API gateway for each BE service?

Have you created the videos to implement all these stuff. Or you have covered theoretical concept only ?

Nice explanation.

Isolation also allows for hiding private APIs and their execution roles. The api from the client only need access rights to call the gateway therefore protecting APIs endpoints and access roles.

super awesome!!

Good one, thank you so much!.

But what if the client only wants ratings & review service response? The API gateway arch which you explained seems like client will make a call to API-G & API gateway will call all services and return response? The client does not need data from all services everytime

... and API gateway finally turns whole application into monolith. I guess API Gateway concept is the basis for server-side service discovery

very nice explanation :) +1

1) Should API Gateway (software) be on a dedicated VM? 2) Should we need to have many gateways across the globe? (to have low latency)? 3) Should we have many gateways at each location (different datacenter?) to avoid single point of failure? 4) Usually how many requests can a gateway server/vm take? 5) Is load balancer different from gateway or both are same? 6) For example, a client (eg: mobile) connects to gateway to interact with the system. Should that gateway be different from API gateway? In other words, should API Gateway be the first and only point of contact (in system) for the client? Thanks in advance

At 14:38 you said , may be you put in vkc (not able to heard it properly) could you please explain what is that

If we have listed an end point that calls 2-3 services, how will the api gateway combine the response and send it back to client, does that mean we need to deploy an another service , at API end point level

Thanks for the excellent video. Question, how should the communication between the microservices be? directly using the API gateway or should I use an API Composition call for that? Thanks in advance.

Thanks Naren for sharing this. One quick question, when you say API gateway can have LB, how actually it happens, is it kind of installation of haproxy on APIGateway or is there any different mechanism ?

Ah pas mal !

Thank u sir!👌🏻

Can API gateway be the single point of failure? If it goes down nothing works, If it holds true doesn't it brings down the whole idea of microservice architecture?

how to implement API gateway? is it another micro service whose purpose is to re-translate client calls?

my company is using nginx web server and kong api gateway but i dont understand why they are using both let me know if u know this.. thanks

Thanx🙏👏

hi could you please make videos of how to secure rest api and debugging of microservices

Is there any api gateway implemented in open source project which I can look at as a case study?

Why we don't use 1 api gateway for web, 3rd and devices?

Thanks, bro.

I wanted to ask you earlier but I didn't... But now I'm asking... ...Software design vs system design Both are same terms or different... Plz tell me

So having more than one api gateway is a new pattern called BFF? Not following why this wouldn't just be part of the "Api Gateway Pattern". W/e just semantics

Does the API Gateway handles sessions or how does it handle state on a web app?

also later we'll need a gateway(s) for the gateways 😂

Pls suggest the best way to implement insulation

Is it bad practice to use GraphQL as API Gateway?

API gateway becomes the single point of failure of the system, can you elaborate how to mitigate that?

am not getting your Part 1 to 4 videos

another disadvantage is api gateway not support tcp

So basically, there's no direct connection between Client and Server but there's a deputy-client which will talk to server on behalf of Client. So the load is shifted to this deputy. I don't see any advantages in this.

if someone directly jump on our main micro services. then how to prevent?

please provdie the example for this

at the first glance, I thought ur name is " teach dummies " LOL

Isn't this already solved by web servers like NGINX or Caddy? Why use API gateway instead of them? All of this can be done with any web server

you need api gateway cuz your boss likes the next big thing

Thanks but you could have explained it in 5 mins.