3 ms·
Disclaimer: AWS Developer Advocate - Serverless One could easily configure lots of things wrong in life that would end up wasting money! That said we find that
by munns 9y ago
Disclaimer: AWS Developer Advocate - Serverless
One could easily configure lots of things wrong in life that would end up wasting money! That said we find that many customers end up saving a lot by moving workloads from more traditional "serverfull" models to Lambda and serverless application patterns. We also see entire startups starting this way and getting to fairly massive scale without ever needing to manage a host anywhere. While not a silver bullet, the use-cases for Lambda are many and proven. More here: https://aws.amazon.com/lambda/resources/#Customer_Case_Studies https://aws.amazon.com/lambda/resources/#Customer_Case_Studi...
- anonytrary 9y agoYeah this is definitely true, it's very easy to rack up huge prices when there aren't bounds, and AWS provides bounds which is great. Lambda, S3, CloudFront, APIGateway, etc. are an incredible boon for any startup. However, the way that AWS charges for throughput on DynamoDB is deceptive -- you can easily bottleneck the system with a hot spot, yet you would need to pay for bandwidth increases everywhere to raise the limit for that single hot spot. This lack of granularity seems to be due to DynamoDB's technical design, and/or lack of a better charging system. https://news.ycombinator.com/item?id=14721920 https://news.ycombinator.com/item?id=14721920 I remember reading an article on how some company ran into a bunch of problems due to their non-uniform query distribution, but I can't find it. I am not an expert, but I would avoid DynamoDB today and stick with something like Cassandra or MongoDB for general NOSQL work. Hopefully DynamoDB has changed since I last encountered it as the idea is a very good one and fits well in the serverless ecosystem.