Thanks for explaining the API Gateway in microservices so clearly You made it really easy to understand how it helps manage, secure, and direct traffic between services. The examples you gave made everything click. Really helpful and practical looking forward to more videos like this.
Load Balancer vs API gate way Loade balance just distributes api calls across multiple instances API gate way serves calls to different micro services, it has intelligence to make a differentiate between microserivces. uses of API Gateway 1. API Composition Mulitple APIs can be called at same place 2. Authorization Only one time authorization call is required and it can be serve to call multiple apis 3. Rate Limiting Throttling , IP based blocking 4. Service Discovery
Best explanation of API Gateway. Thanks, Shreyansh! I hope you start a microservices series soon because I notice that most channels or courses jump directly into implementation without first explaining the theory.
API composition can also be done by GraphQL queries and they allow highly dynamic queries, with minimal data send over the network than a API gateway which sends predefined structure
I had also, similar kind of questions related to API gateway (e.g. if API gateway is single entry point, how does it handles requests at scale etc) You've nicely explained concepts and industry practices related API Gateway.
Hats off to the explanation dude!! I work at a big PBC and these videos are gem if you dont want to invest your time in books. Still what is your source of book?
Thanks for the details. Could you please help clarify, Service discovery in the API Gateway level, checks only the health of load balancers or the individual services too ? Is Load Balancers consults with Service Discovery to locate the active services ?
From where do you gain your knowledge? it is very easy to follow. Can you give shoutout to the resources you follow. Also i was wondering, where does kubernates fit in here?
Thanks for the video, the first question that how API gateway can handle million of requests is clear to me, i.e. how does it scale horizontally. Maybe I did not understand, please correct me if I am wrong?
I don't think API gateway will distribute traffic among availability zones, it's cloud providers responsibility (AWS). Our API gateway is deployed as similar as other Microservices in different availability zones. It can transfer between Microservices based on path based routing
I think you have mixed Authentication and Authorization concept. OAuth is used for authorization. But any ways kudos to you for your effort you put in.
00:04 API Gateway routes client requests to correct backend services based on API endpoint. 02:43 API Gateway intelligently routes requests based on device type 05:26 API Gateway features 08:11 API Throttling and Rate Limiting 10:52 API Gateway acts as a single entry point for microservices and handles request routing and transformation. 13:37 API Gateway acts as a single entry point for routing traffic to multiple instances of microservices using load balancers. 16:21 API gateway acts as a single entry point for multiple instances of microservices in different availability zones. 18:52 API Gateway routes traffic based on user location and API type. 21:02 DNS-based load balancers distribute traffic intelligently 23:19 API Gateway acts as a single entry point for microservices architecture
API Gateway is acting as a proxy is what I understood from the lecture, How is API gateway different from Proxy if that is the case ? A Proxy can also route request to endpoints, but API gateway can do a service discovery which a proxy can't. Apart from is there any other major differences between a proxy and API Gateway ?
- Advanced routing and aggregation: API Gateway can handle complex routing and response aggregation; a proxy cannot. - Security: API Gateway includes authentication, authorization, and rate limiting; a proxy does not. - Request/response transformation: API Gateway can transform data formats; a proxy lacks this. - Monitoring and analytics: API Gateway offers built-in analytics; a proxy has basic logging only.
Let’s assume we have an API gateway configured with a rate limit of 500 requests per minute (RPM). If an end user sends 501 RPM to Region 1, the excess request will be blocked. However, if the same user redirects their requests to Region 2 (assuming that it is possible..), which also has an API gateway with a 500 RPM limit but has not yet reached its limit, will the user’s requests be served by Region 2? If so, does this mean the user can continuously receive responses by alternating requests between regions, effectively bypassing the rate limit?
Here I have doubt from long time, is api gateway not a single point of failure ? or is it like multiple instance of api gateway runs, if yes then there how the routing is handled ? Doubt is cleared here: ruclips.net/video/dkgxvnk8cWw/видео.html
still I have doubt, API Gateway in one particular region can have thousands of reqeust per sec, how its handling it? as API gateway is a single point of contact btw client and load balancer
i do have 1 doubt what would happen if suupose more millions request are coming from the same region then dns would be sending all the request to the api gateway of that region
Api gateway doesnt have any orchestration right , if one micro service is dependent on another , and the dependent one is down , in that case we cant achieve high availability right
If api gateway is smart, cant we ask the gateway to route the requests directly to load balancer of appropriate services instead of look up into service discovery?
That's why he told you can include the service discovery functionality within the gateway itself. But since libraries like Eureka gives easy integration of service discovery and dashboards to visualize different service addresses, it is preferred.
Finally!!!................. after a decade, video on HLD, I thought the playlist was dead!
I would say you are one of the gems in these over crowded videos on the internet..
Thanks for explaining the API Gateway in microservices so clearly You made it really easy to understand how it helps manage, secure, and direct traffic between services. The examples you gave made everything click. Really helpful and practical looking forward to more videos like this.
Thank you very much with video. It helped me clear many doubts.
Load Balancer vs API gate way
Loade balance just distributes api calls across multiple instances
API gate way serves calls to different micro services, it has intelligence to make a differentiate between microserivces.
uses of API Gateway
1. API Composition
Mulitple APIs can be called at same place
2. Authorization
Only one time authorization call is required and it can be serve to call multiple apis
3. Rate Limiting
Throttling , IP based blocking
4. Service Discovery
Best explanation of API Gateway. Thanks, Shreyansh! I hope you start a microservices series soon because I notice that most channels or courses jump directly into implementation without first explaining the theory.
API composition can also be done by GraphQL queries and they allow highly dynamic queries, with minimal data send over the network than a API gateway which sends predefined structure
I had also, similar kind of questions related to API gateway (e.g. if API gateway is single entry point, how does it handles requests at scale etc)
You've nicely explained concepts and industry practices related API Gateway.
The best Explanation in depth...Thanks a lot for the Amazing Videos.
Wow. So easy to understand. Thanks a lot.
Best and easy explanation. Beginner friendly!
Man you are doing great work in every video...pls keep up the momentum of new videos.
Take a bow 🙇♂️ man. Very well explained ❤😊.
Thanks a lot for this video! Information packed video! Learnt a lot new things, many doubts got resolved! 🙏
Well explained and detailed documentation. Thank you very much!!!
Very nicely explained. Thank you so much !!!!
Hats off to the explanation dude!! I work at a big PBC and these videos are gem if you dont want to invest your time in books. Still what is your source of book?
Thank you very much bro. making vedio on microservices
Thanks for this, can you also redo your previous videos for High level design in english please?
Thank you sir , you made it clear
Thanks for the details. Could you please help clarify,
Service discovery in the API Gateway level, checks only the health of load balancers or the individual services too ?
Is Load Balancers consults with Service Discovery to locate the active services ?
From where do you gain your knowledge? it is very easy to follow. Can you give shoutout to the resources you follow. Also i was wondering, where does kubernates fit in here?
Thanks for the video, the first question that how API gateway can handle million of requests is clear to me, i.e. how does it scale horizontally. Maybe I did not understand, please correct me if I am wrong?
Really amazing and informative content👍
Very well explained....good work bro 👍
1. API Composition
2. Authentication
3. Rate limiting
4. SSL Termination
Awesome ❤, Do you have hand's on for the same? So we can practical
Thanks a lot for this video🙏🏻
I don't think API gateway will distribute traffic among availability zones, it's cloud providers responsibility (AWS). Our API gateway is deployed as similar as other Microservices in different availability zones. It can transfer between Microservices based on path based routing
I think you have mixed Authentication and Authorization concept. OAuth is used for authorization. But any ways kudos to you for your effort you put in.
Excellent explanation
00:04 API Gateway routes client requests to correct backend services based on API endpoint.
02:43 API Gateway intelligently routes requests based on device type
05:26 API Gateway features
08:11 API Throttling and Rate Limiting
10:52 API Gateway acts as a single entry point for microservices and handles request routing and transformation.
13:37 API Gateway acts as a single entry point for routing traffic to multiple instances of microservices using load balancers.
16:21 API gateway acts as a single entry point for multiple instances of microservices in different availability zones.
18:52 API Gateway routes traffic based on user location and API type.
21:02 DNS-based load balancers distribute traffic intelligently
23:19 API Gateway acts as a single entry point for microservices architecture
In LB we can define route based also , Please check again
manh this is gold!!!!!!!!!!!!!!!!!!
API Gateway is acting as a proxy is what I understood from the lecture, How is API gateway different from Proxy if that is the case ? A Proxy can also route request to endpoints, but API gateway can do a service discovery which a proxy can't. Apart from is there any other major differences between a proxy and API Gateway ?
- Advanced routing and aggregation: API Gateway can handle complex routing and response aggregation; a proxy cannot.
- Security: API Gateway includes authentication, authorization, and rate limiting; a proxy does not.
- Request/response transformation: API Gateway can transform data formats; a proxy lacks this.
- Monitoring and analytics: API Gateway offers built-in analytics; a proxy has basic logging only.
Hi bro , please make video of implementation on aws, and also if its on kubernates how it will b implemented
HI Shrayansh
Please create a video on Back in the envelop estimation.
@@akashmaharana4384 hi kindly check the HLD playlist, its there already
can you please provide a deployment and impl. process for better understanding thanks!
Awesome dude
Akamai is another example for dns based load balancing
Please make a video on AWS
Let’s assume we have an API gateway configured with a rate limit of 500 requests per minute (RPM). If an end user sends 501 RPM to Region 1, the excess request will be blocked. However, if the same user redirects their requests to Region 2 (assuming that it is possible..), which also has an API gateway with a 500 RPM limit but has not yet reached its limit, will the user’s requests be served by Region 2? If so, does this mean the user can continuously receive responses by alternating requests between regions, effectively bypassing the rate limit?
please also add this video in your udemy lld+hld course playlist
yea will do
Earning opportunity laine jese kai backed apis bana ni hao database design karna ho, fronted ka kuch work
Bro, Could you please post a video for @ApiOperation annotation and documentation using swagger. Thanks in advance
Here I have doubt from long time, is api gateway not a single point of failure ? or is it like multiple instance of api gateway runs, if yes then there how the routing is handled ?
Doubt is cleared here: ruclips.net/video/dkgxvnk8cWw/видео.html
I have the same doubt like you too
still I have doubt, API Gateway in one particular region can have thousands of reqeust per sec, how its handling it? as API gateway is a single point of contact btw client and load balancer
could someone pls explain why there will be multiple instances of microservices ??
i do have 1 doubt what would happen if suupose more millions request are coming from the same region then dns would be sending all the request to the api gateway of that region
Api gateway doesnt have any orchestration right , if one micro service is dependent on another , and the dependent one is down , in that case we cant achieve high availability right
right, api gateway do not have orchestrator built in. we generally write our own.
If api gateway is smart, cant we ask the gateway to route the requests directly to load balancer of appropriate services instead of look up into service discovery?
@@gunam3876 yes many new api gateways does that.
That's why he told you can include the service discovery functionality within the gateway itself. But since libraries like Eureka gives easy integration of service discovery and dashboards to visualize different service addresses, it is preferred.
If we implement in form of coding it will really code
Boss I am a member but still not able to find the notes . can you help me please
for this video? i will add by evening
@@ConceptandCoding Thanks.
Does this subscription continue to charge ₹199 every month?
How API GATEWAY secvice scale??? there is only single instance there
Bro please update spring boot course I'm going take membership just for that
sir please upload in udemy
done pls check
😎👍🏻
Bro itne long time baad series continue krte, kisi ek series pr focus krke complete kro spring boot
will do, got this question asked in latest system design interview, so thought to add it, else i will loose track of this question.