undefined

points

[-]

I'm curious how that plays out when you factor in other infrastructure components like DB and load balancers.

On Lambda, load balancing is handled out of the box but you may need to introduce things like connection poolers for the DB you could have gotten away without on EC2

Think it also depends if you're CPU or memory constrained. Lambda seemed more expensive for CPU heavy workloads since you're stuck with certain CPU:mem ratios and there's more flexibility on EC2 instance types

by themafia6 hours ago|

parent|

[-]

I wouldn't know. I use DynamoDB almost exclusively. These simply aren't considerations that occur with that product.

It is true that it can be hard to size workloads into lambdas rather unusual CPU configuration; however, the real beauty of lambda is, you can just fork several parallel copies of your function. We can sometimes fork up to 250 instances just for a single "job."

If you're in the same boat we are where your workloads parallelize easily then Lambda has been incredibly cost effective for this use case.