Re:Google not Amazon. Make fantastic savings in a server-les...
by eropple on Wednesday July 19, 2017 @09:09PM
(#14809330)
Another devops thread, another time I end up agreeing with 'toomuchtodo. "Serverless" is sneaky-expensive. It's not a particularly practical model once you've gone past trivial stuff; maybe that'll change, but operations for instances and even your more involved boondoggles like container-fleets-on-cloud-compute are pretty well-understood at this point in ways that serverless stuff still isn't.
But yeah, they're "toys". Risk and cost? Who cares. Let's blog.
Re:Google not Amazon. Make fantastic savings in a server-les...
by sillysaurus3 on Wednesday July 19, 2017 @09:22PM
(#14809386)
Could anyone give a breakdown on why it's more expensive (and where the money goes)? Interesting stuff.
Re:Google not Amazon. Make fantastic savings in a server-les...
by eropple on Wednesday July 19, 2017 @09:28PM
(#14809402)
Both Google and Amazon charge based on compute heft per second (Amazon in GB-seconds, Google in a mix of GB-seconds and GHz-seconds). When you multiply that out, it overtakes EC2 pricing at a point; I've done the math out for different types of sites before, and it obviously varies by stack, but you hit those breakpoints a lot sooner than you might otherwise expect. One project's workload was something like 10 req/sec and the Lambda costs were more than three load-balanced m4.larges (edit: load-balanced for fault tolerance more than load) due to RAM usage that was per-request in Lambda but amortized across all requests on instances.
Serverless stuff can make a lot of sense for low-utilization tasks under this model, but for applications with nontrivial load you may be paying for a lot of GB-seconds on an ongoing basis. Couple that with the additional latency inherent to spin-up times when putting Lambda behind an HTTP endpoint, and it also runs the risk of being a kinda-janky experience for the user, too (though this can be mitigated), and I'm very not-a-fan past toy/proof-of-concept problems.
Re:Google not Amazon. Make fantastic savings in a server-les...
by toomuchtodo on Wednesday July 19, 2017 @11:10PM
(#14809797)
Perfect explanation as usual.
Re:Google not Amazon. Make fantastic savings in a server-les...
by threatofrain on Wednesday July 19, 2017 @09:12PM
(#14809349)
The author's definition of serverless was too vague and under-discussed for me to touch, but I didn't get the sense that the author was comparing the cost profile of Amazon's Lambda to Google's Cloud Functions.
Re:Google not Amazon. Make fantastic savings in a server-les...
by toomuchtodo on Wednesday July 19, 2017 @09:14PM
(#14809358)
I should've been more clear. I believe the author was comparing AWS instances to Google serverless. Serverless has its place, but moving to it wholesale with no thought to use case or workload profile is insanity.
Because serverless at scale is phenomenally expensive compared to instances + ops. Solid for prototyping or where you just need to fire off some functions though.