How can you use a Lambda to respond to an HTTP request? There are more ways than ever to do it. We have API Gateway REST APIs, Lambda support for Application Load Balancer, and now Function URLs. But which one should you use, and when? In this episode of AWS Bites podcast, we will give you a quick and simple guide to picking the best way to build APIs with Lambda. In this video, we're going to pitch Function URLs against API Gateway in a battle for the ages! Function URLs offer a simple and quick way to get a public URL to invoke a Lambda function, with fewer configuration options and cheaper pricing. They are suitable for private webhooks, simple backend functions, and machine learning inference backend. However, they lack authorization and DDoS protection, making them unsuitable for public webhooks. On the other hand, API Gateway offers more features and control, making it suitable for public APIs. API Gateway comes in two flavors: REST and HTTP with some subtle differences. Finally, we will also cover Application Load balancer and explore when and why it can be a convenient alternative to both Function URLs and API Gateway.

💰 SPONSORS 💰

AWS Bites is sponsored by ⁠⁠fourTheorem⁠⁠, an AWS Consulting Partner offering training, cloud migration, and modern application architecture.

In this episode, we mentioned the following resources:

Article by AJ Stuyvenberg reporting that Function URLs have a latency of 8.35ms
GitHub repository with all the material we used in our evaluation

You can listen to AWS Bites wherever you get your podcasts:

Why Britain needs to wake up to extremism

Coffee House Shots

Failures to name and confront Islamist violence

The AI-powered Podcast Player