3 ms·
As an alternative to Lambdas I can see this being useful. However, the overhead concerns me. This would only make sense in a situation where the function in qu
by bovermyer 3y ago
As an alternative to Lambdas I can see this being useful.
However, the overhead concerns me. This would only make sense in a situation where the function in question takes long enough that the startup overhead doesn't matter or where the main application is running on hardware that can't handle the resource load of many instances of the function in question.
I'm still, I think, in the camp of "monoliths are best in most cases." It's nice to have this in the toolbox, though, for those edge cases.
- cchance 3y agoHe commented in another post that they use pooling so you don't really pay the cold start penalty as often as you'd think so maybe not a issue?
- freedomben 3y agoI don't think this goes against "monoliths are best in most cases" at all. In fact it supports that by letting you code like it's all one monolith, but behind-the-scenes it spins up the instance. Resource-wise if you had a ton of unbounded concurrency then that would be a concern as you could quickly hit instance limits in the backend, but the pooling strategy discussed lower in the post addresses that pretty well, and gives you a good monitoring point as well.