Application Load Balancer (ALB) Vs API Gateway // Pros Cons Comparison
ฝัง
- เผยแพร่เมื่อ 31 พ.ค. 2024
- In this video we will start with what is Amazon Application Load Balancer (ALB) and Amazon API Gateway, then we will dive deep into the comparison - feature differences, pros cons, limitations, price difference etc. Finally we will go over conclusion. Timestamps below.
💰👨🎓 Get my courses with max discount and 30 day moneyback guarantee: bit.ly/3Eku9RH
🙏Please Subscribe: bit.ly/2Yk0Kbb
*Connect with me*
🤳 Instagram: / cloudwithraj
🏢 LinkedIN: / cloudwithraj
🐦Twitter: / cloudwithraj
🖼 Facebook: / cloudwithraj
TIMESTAMPS:
00:00 Intro
00:44 Brief intro to ALB
01:37 Brief intro to API Gateway
02:27 Differences between ALB and API Gateway
13:16 Conclusion - วิทยาศาสตร์และเทคโนโลยี
My Rocking Systems Design course is out now in Udemy! Limited time discounted link to get the course for $9.99 - bit.ly/3Eku9RH
I haven't met such an excellent teacher in a while. Thank you very much Raj for these videos. They are the best!
Comparing the services with small examples and use cases will be much intresting way to understand
This is what I was looking for, very informative. Thank you for uploading
One of the ultimate videos that I have ever watched in this ecosystem. Very informative and thoroughly put. Thank you.
Thanks Sanjeev, glad it was helpful!
Awesome!! Im addicted to your videos watch them first thing every day and when I have even a break of 10 mins!!!
Glad you like them!
Lot of questions regarding Static IP with ALB. This is a brand new feature. This is done pairing Global Accelerator and ALB with one click. You don't need to provision a NLB separately for this. AWS announcement here - aws.amazon.com/about-aws/whats-new/2020/07/aws-global-accelerator-launches-one-click-acceleration-for-application-load-balancers/
Raj, your content is simply amazing. Thank you for putting these videos out!!
Glad it was helpful Zan
Very Informative Raj..Thanks
Excellent JOB Raj, I always loved the way to represent the things in your videos, the videos which are available on the TH-cam under your channel are always priceless Pearls for me.
I would like to request to add few points like, 1. Synchronous and Asynchronous Invocation Methods, Payload Difference to travel from source to Destination and Return, Type of Data/payload to be send or received while call the invocation/msg forwarding, Layer-Specification on Functionality. I hope, the things which I have mentioned might be helpful or can be considering for the comparisons. Let me know if I am wrong. Thanks
Absolutely, well summarized Amar!
Thanks for the great session 🙏🏽
Great video, thanks!
Excellent video.. Thank you Raj.
My pleasure
Bruh, Nice setup!
Thanks, Dude! Great Work!!!!!!!
Thanks Douglas for watching.
Very nice , Thanks!
Raj great video. We can use ALB with IP address as target for my backend targets in different account with TGW for communication?
Awesome Raj. Thank you so much.
Thanks Soumya for watching. I am glad you found this helpful.
Good video. Thanks.
Thanks Raj. It was really good information
Thanks Vinit for watching. I am glad it was useful.
Thanks for the informative video, how do you version the API?
Hi Raj It’s very informative Thank you
Thanks and welcome
Thanks for the excellent video!!
Thanks Anirban :). Glad you found it useful.
+1 for the shirt! And the content
Very informative video, thank you 😊
Glad it was helpful!
Very informative video. Thanks.
Glad it was helpful!
Great Video.. I believe ALB can have cross-region/ acconut targets by leveraging VPC peering and registering targets by IP address..
Yes, you are right Anshika, however it is little involved. I was covering out of the box features. Thanks for pointing out. Keep learning and keep rocking!
thanks but i found my record is inactive in Create DNS records in Amazon Route 53 page
Rocking !!!
Very informative video. I came across this while trying to find an answer on whether we need a load balancer when we plan to have an api gateway in our system design. From this video I understand the key differences a load balancer has - static ip address, ability to handle more requests per second (?) and larger timeout limit. There is a mention about health checks but that's something API gateways like WSO2, Kong, Krakend also have these days.
Is there any key feature that mandates the need of having a load balancer in the system infrastructure when an api gateway is already present?
Thanks.
Thanks Amit for the kind feedback. True, some API gateways have health checks, however I wanted to focus on the AWS managed API Gateway. Kong, Ambassador is good but application team need to manage the infra, scaling etc. In certain cases if you need private integration then you need to use API Gateway > LB > EKS/ECS
@@cloudwithraj bro may I know what's difference betweeen private integration and normal integration?
Hey Raj, Karthik here.happy to see, remember we met in Detroit a couple months ago.... I was searching for something and your video popped up. Awesome video , all my questions clarified
Thanks a ton Karthik! Glad to connect in Detroit 🙌
I don't think you mentioned it, but both support https/SSL termination. Thanks for the video Raj!
Good point Kent, ty!
Wow RGB to the next level, Linus proud of you
Thanks brother! Linus is GOD of RGB hahaha
Sir what is load balanced rest api ??
One like on your video is equal to 9999 likes in any entertainment video. Quality matters. Keep doing the great work.
Thank you so much 😀
Great Tutorial
Glad it was helpful!
Thanks Raj for your awesome work, btw AFAIK the ALB IPs are all dynamic, just the DNS name of the ALB is static. Can you please elaborate more on this?
Hello Hamidullah, When you provision a load balancer in AWS it provides us a URL to access it which is its DNS name. That name is permanent. But when you will try to do a IP lookup of the loadbanacer URL you will get two public IPs. These IPs will change in sometime automatically that is why it is called dynamic IP. So we cannot rely on IP but the LoadBalancer static name.
Thank you
You're welcome
Thanks for the explaination... When can we use both like API Gateway -> ALB -> ECS? If possible could u please put a video for the same..
Noted Sonali, will try to do a video on this.
Hi Raj .. Video was really informative like all your other videos.. You have listed that its possible to get static IP in ALB ..However, AWS site says that its not possible to have a static IP and we have to use it in conjunction with NLB or Global Accelerator ... I am a bit confused on this point.
AWS Link I am referring above : aws.amazon.com/blogs/networking-and-content-delivery/using-aws-lambda-to-enable-static-ip-addresses-for-application-load-balancers/
Just realized that you have already answered my above question in your comments.
Great video! Is there an option where we can utilise benefits of both API gateway and ALB. The key limitation of API gateway is restriction to serve 10,000 RPS which is not there in ALB , I wanted to get over limit and utilise the request /response mapping capabilities.
No such option currently out of the box. You can split the API in different accounts/regions to bypass the limits.
Thank you 😊
You're welcome 😊
Sir, please let us know, how to create web development or real client level infrastructure development with AWS compute database and other components...
Will keep in mind for future videos. Thanks for the suggestion!
@cloudwithraj
Is it possible to connect api http gateway with ecs service without using an application load balancer. Will the gateway act as a load balancer?
Even i have the same question. could you please tell @cloudwithraj?
nice session man
Ty bro, glad you found it helpful
Hey Raj , thanks for the informative video. I have one question that might be basic and naive but it will help if you can clarify. where does CDN comes into picture if you are using and API gateway or load balancer? thanks
Hey Simran, your question is neither basic, not naïve! CDN is a content delivery network. It will sit in front of an API (or ALB). Whatever the API returns, CDN can cache it and makes it faster for other viewers to retrieve the data. Hope this helps.
@@cloudwithraj thank you so much for responding , helps a lot
I am bit confused , can we use LB along API gateway ?
Also does every api call for different action need different resource. Means if I have 3 actions like /v1/activate , /v1/pickup, /v1/drop do I need 3 resources to process the request from these 3 apis?
Hey! Yes you can use LB as the backend of an API Gateway API. Assuming v1 is stagename, you can create three resources - activate, pickup, and drop to achieve that under one API. You don't need to create three different APIs for this
@@cloudwithraj thanks Raj, how about the endpoints , does all threes actions from this api will have three lambda or only one lambda or ec2 instance
good one
Thanks :)
Hei Dude, one question, is static IP just for NLB, ins't?
Douglas, not anymore, check out pinned comment, added it this morning.
Hi raj can you make a video on AWS gateway load balancer
Will keep in mind for future videos Siva
👌👌👌
This tutorial was very informative...
Glad you liked it. Thanks for watching.
Api gateway win by far, what's the reason to use ALB?
ALB has good use cases too Ming - if you need greater connection timeout, out of the box health checks, direct integration with kubernetes as ingress etc. Also most on prem apps use load balancer and when they migrate to cloud they just start using load balancer rather than redesigning with API gateway.
can't use API gateway with ks8?
@@mming_my Not directly, have to be API Gateway to LB (working with ingress) then to pods. You can install a third party API gateway like kong directly on kubernetes and expose without load balancer but with Amazon API gateway you need a load balancer. Hope this helps
High five to a fellow Rick and Morty fan!
PICKLEEEEE RIIIICK
Really good video… but the only irritating part is the fake accent and I cannot somehow divert my focus from that. One piece of advice:- Not sure which accent you are trying to put but neither UK nor US sounds like that. Thank god, I don’t work with you professionally.