3 ms·
I thought commenter W. Van Dam made some good points: “ First, you don't need API Gateways if you use an AWS SDK. Like this guide shows. And of course you don
by gigatexal 7y ago
I thought commenter W. Van Dam made some good points:
“ First, you don't need API Gateways if you use an AWS SDK. Like this guide shows. And of course you don't need a load balancer, because that's precisely one of the things that serverless takes care of for you :-)
More importantly, you didn't actually compare serverless to your current situation.
With serverless solutions you can typically save cost in terms of server management. Serverless isn't maintenance free, but you should be able to reduce your monthly cost (e.g. lower labor cost).
You're right to research whether it actually works for you, but I think you're not done yet ;-)
Also, perhaps CloudFlare Workers are of interest to you. It's a rather new offer in the market. They charge 0.50 dollar per million requests, with a time limit of 50ms per request. Sounds like this combination would work well for you in comparison to AWS Lambda”
- scarface74 7y agoYou can do the same thing with Lambda @ Edge and CloudFront for .60 per million requests and there is a free tier. (https://aws.amazon.com/lambda/pricing/ https://aws.amazon.com/lambda/pricing/)
- gigatexal 7y agoYeah I just wanted to point out like the authors whose post I copied here that the way of going serverless taken by the story author was probably not ideal.
- zackbloom 7y agoWorkers are pretty significantly different. They don't have a meaningful cold-start time, for one.
- scarface74 7y agoLambdas @ edge don’t either. There are different optimizations than regular lambdas and you wouldn’t use a heavyweight environment and of course they wouldn’t be running attached to a network.