This is a good video. This video definitely informs; however, it will KEEP you employed. You'll get tons of interviews (not that you're looking for them now). IMO, if you haven't already, you should post this to your Linkedin feed.
@@REXTECH9 I'm a long time product manager and fairly technical. I always knew there was a deficiency in other PMs from a tech stand pt and that was always my advantage in getting certain jobs. I recently saw this one guy create a Cohort for product managers called "Technical Foundations" and he is getting pretty good traction. That and really more so, your video has convinced me that I need to produce just a few short videos starting with something similar to yours and put them on my LinkedIn feed. To be totally transparent...only for views that will help lead to continued employment leads.
Thanks for the video! Just a question, would u consider using the feature of function url in Lambda instead of api gateway? This could mean 1 less resource to maintain. Correct me if i am wrong.
Thank you! And yes, even though Lambda Function URLs my seem simpler they lack many features that API Gateway natively provides. So API Gateway offers request and response transformations, integrates with AWS services like Cognito for advanced authentication and authorization and it also supports rate limiting and throttling to protect your backend from like DDos attacks and other malicious web attacks. It even allows for custom domain names and provides waay more granular CORS control. Also with API Gateway, it integrates with CloudWatch for detailed monitoring and logging of request, and offers WAY more security options like say TLS and of course WAF integration. One other huge benefit of API Gateway over Url Lambda is, when it comes to scaling, API Gateway scales better with multi-stage deployments, versioning and canary deployments, so its much more ideal for growing applications. Lastly. I want to mention that for more advanced use cases like real-time data streaming, WebSockets or adding some complex routing, API Gateway is a waay better fit, because Lambda Function URLs just can't really handle such scenarios. Hope this helps!!!
👏👏nice, really understood a lot.
Yess! My pleasure, first time doing this so I'm glad that it resonated!
this is a very good explanatory video. it has been insightful for a project i am working on
Thank you so much and I'm glad that it was able to help you in your project!
This is so deep. You should definitely do more videos as these. And thanks for this one here.
Okay...I'm stuck on the light to the left. That light is FIRE!
Haha I gotta do an office setup video for yal!
Love the video style, great stuff!
Ayyyee! Thanks brooo! I really appreciate it man
Love your videos! kindly drop a roadmap/guide for interested individuals looking to follow your path to becoming a Cloud Eng.
Thanks a lot and I will !!
Really enjoyed every bit of it. Looking forward to more of your videos.
I really appreciate the support and feedback! Thanks!
This is a good video. This video definitely informs; however, it will KEEP you employed. You'll get tons of interviews (not that you're looking for them now). IMO, if you haven't already, you should post this to your Linkedin feed.
You're speaking facts here maaan! Haha I did post it and it did really well. I'm going to be doing much more videos like these and keep them going!
@@REXTECH9 I'm a long time product manager and fairly technical. I always knew there was a deficiency in other PMs from a tech stand pt and that was always my advantage in getting certain jobs. I recently saw this one guy create a Cohort for product managers called "Technical Foundations" and he is getting pretty good traction. That and really more so, your video has convinced me that I need to produce just a few short videos starting with something similar to yours and put them on my LinkedIn feed. To be totally transparent...only for views that will help lead to continued employment leads.
Great video. The prop piano was important 😂
haha you see it!! :) Thank you!
Great Video, We need more please 😅
More on the way soon. I promise lol :)
This is really helpful. Thank you
You're most welcome!!
👏🏾👏🏾👏🏾 Love how you explained everything!
Thanks bro! Tried to do it one take too, its crazy watching all the funny stuff in it lol
Loved it!
Thank you!!
Thanks for the video! Just a question, would u consider using the feature of function url in Lambda instead of api gateway? This could mean 1 less resource to maintain. Correct me if i am wrong.
Thank you! And yes, even though Lambda Function URLs my seem simpler they lack many features that API Gateway natively provides. So API Gateway offers request and response transformations, integrates with AWS services like Cognito for advanced authentication and authorization and it also supports rate limiting and throttling to protect your backend from like DDos attacks and other malicious web attacks. It even allows for custom domain names and provides waay more granular CORS control.
Also with API Gateway, it integrates with CloudWatch for detailed monitoring and logging of request, and offers WAY more security options like say TLS and of course WAF integration.
One other huge benefit of API Gateway over Url Lambda is, when it comes to scaling, API Gateway scales better with multi-stage deployments, versioning and canary deployments, so its much more ideal for growing applications.
Lastly. I want to mention that for more advanced use cases like real-time data streaming, WebSockets or adding some complex routing, API Gateway is a waay better fit, because Lambda Function URLs just can't really handle such scenarios.
Hope this helps!!!