[russtrotter]

A few years back, I refactored a memory/time-intensive task of an application to leverage AWS lambdas. Once the code got into production, it ended up working out fine and we were able to side-step OOM issues that were plaguing the prior incarnation. Takeaways:

* being able to scale on a per-request basis and understand your burst usage of resources is pretty useful

* the top-level comment regarding CAPEX vs OPEX was spot on. Our higher-ups always had their eyes on the AWS bill and not having to pay for instances (either spot or elastic) appeased them.

* at the time at least with Java-based lambdas, the local tooling was really clunky and slow with that nasty startup. You might have better success with node or python in that area.

* otherwise, like any other tech, there's gonna be tradeoffs. Something good to keep in your toolbox, but like most things they're no silver bullet.

[kaba0]

Unless you are doing something really short-living, or just calling FFI for IO, python is really slow compared to node or java.

[smackeyacky]

The startup time for .NET lambdas is pretty good. A good alternative to Python at least for me