API Gateway: Why you should use Service Proxies скачать в хорошем качестве

API Gateway: Why you should use Service Proxies

This is a preview lesson from my upcoming workshop, "Production-Ready Serverless". If you liked this, then please check out the full curriculum at https://productionreadyserverless.com. You can get 15% OFF with the code "YOUTUBE15" during checkout. Hope to see you there! Amazon API Gateway lets you integrate with other AWS directly without needing a Lambda function. This "functionless" approach allows you to eliminate Lambda functions from your architecture and all that entails. The potential cold start overhead, the cost associated with Lambda invocations and any scaling limit (such as Lambda's burst capacity limit) related to Lambda functions. This is a useful pattern for simple CRUD endpoints that do only one thing. For example, to fetch an order from a DynamoDB table and return it to the caller. But everything is a trade-off. Using this approach also means you miss out on many useful patterns that can be implemented in your Lambda function. Such as the ability to add contextual logging around errors, or using fallbacks, and many distributed tracing tools won't work without a Lambda function to collect the necessary telemetry data. ✅ Recommended playlists: Learn to build Production-Ready Serverless Applications    • AWS Lambda: When to use Function URLs?   Testing Serverless Architectures    • Serverless Testing: A Crash Course   🔔 For more free videos on YouTube, subscribe to my channel:    / @theburningmonk   💌 If you're hungry for more insights, best practices, and tips on building serverless applications, make sure to subscribe to my weekly newsletter and elevate your serverless game! https://theburningmonk.com/subscribe 📚 My courses 📚 https://theburningmonk.com/courses 👨‍🏫 My hands-on serverless workshop 👨‍🏫 https://productionreadyserverless.com 🌐 Find me here Twitter:   / theburningmonk   LinkedIn:   / theburningmonk   Blog: http://theburningmonk.com