4 ms·
If you use a lambda on aws you get 1 million requests for free each month and after that factions of a penny per invoke.
by vorticalbox 7y ago
If you use a lambda on aws you get 1 million requests for free each month and after that factions of a penny per invoke.
- therein 7y agoThat's wonderful. Now you can use those requests to read from or write to SQS, do DynamoDB stuff and play in the AWS walled garden where things seem cheap at first but things add up. You can then keep telling yourself you have a stable, managed infrastructure and you're cutting on operational expenses and able to move fast while the engineers in your organization are working harder to make things work with generic services with shortcomings, making your product actually work in less than optimal ways. Managed services feel like they are helping with operational costs but they have a cost when you're building your product. I worked on projects that would have ended up being simpler and cheaper to operate on physical dedicated servers, but instead they are running on "ASG's that autoscale and have zero downtime" with "ALBs that send traffic to any and all hosts when all origins report unhealthy". Things in the managed world is far less than ideal because one size doesn't fit all.
- opportune 7y agoThe issue with lambda is that at high loads it's a lot more expensive than using a server. I looked into doing something with lambda that would take about ~10b invocations/day and it was so expensive compared to just standing up a microservice. So I've never deployed a lambda before and I'm sure at low loads it's fine, but I would be afraid of taking a dependency on lambda/functions in an application architecture.