Lambdas - good for deploying quickly.
Overall Satisfaction with AWS Lambda
We use Lambdas as the primary deployment mechanism for our APIs. It provides flexible ways to deploy without worrying too much about infrastructure, server resilience, or load.
Pros
- It scales automatically with demand.
- It reduces operational overhead significantly.
- It integrates seamlessly with other AWS services.
- It provides easy ways to deploy and get to prod.
Cons
- Cold starts are still a pain sometimes.
- Deployment can feel clunky. The zipped files can still become really bulky and fail.
- Local debugging isn't always straightforward; it's challenging to set up on my machine for dummy Lambda instances.
- Less server stuff to manage probably saves some cash.
- Scales itself, so we aren't paying for idle servers all the time.
- It's quicker to get things out there, so we can focus on the product roadmap instead of deployment.
- Amazon Elastic Compute Cloud (EC2), Azure Functions and Cloudflare Workers
It's fine, it works as the others would have, except EC2. We are migrating back to EC2 for dedicated compute because we have scaled to a point where we have consistent traffic. The tradeoff of maintaining infrastructure in-house outweighs the benefits of moving quickly through our roadmap.
Do you think AWS Lambda delivers good value for the price?
No
Are you happy with AWS Lambda's feature set?
Yes
Did AWS Lambda live up to sales and marketing promises?
Yes
Did implementation of AWS Lambda go as expected?
Yes
Would you buy AWS Lambda again?
Yes

Comments
Please log in to join the conversation