undefined | Better HN

0 pointsdanfritz3y ago0 comments

With lambda you pay for what you use. It scales endlessly and is quite cheap. Depending on your typical usage and load it can be a huge cost saver (also mentally) as lambda will scale.

With ECS Fargate it costs money even without any traffic and you are responsible for correctly implementing auto scaling.

I'm coming from 10y rails dev background and now full stack typescript. Thinking in pure lambda functions is a breath of fresh air for me.

0 comments

andrew_3y ago

if this is powering your primary API and you have 24/7 traffic, fargate can actually be cheaper in some circumstances. there's nuance in lambda config, including concurrency, temp space, and memory. pay for usage is nice until it's not.

michaelcampbell3y ago

> ... is nice until it's not.

Like everything, no? This is akin to saying "All tautologies are tautological."

Your sentence preceding this one laid out some issues; you probably could have left it at that <shrug>.

andrew_3y ago

could have done without the editorial critique as well.

j / k navigate · click thread line to collapse

0 pointsdanfritz3y ago0 comments

With lambda you pay for what you use. It scales endlessly and is quite cheap. Depending on your typical usage and load it can be a huge cost saver (also mentally) as lambda will scale.

With ECS Fargate it costs money even without any traffic and you are responsible for correctly implementing auto scaling.

I'm coming from 10y rails dev background and now full stack typescript. Thinking in pure lambda functions is a breath of fresh air for me.

0 comments

andrew_3y ago

michaelcampbell3y ago

> ... is nice until it's not.

Like everything, no? This is akin to saying "All tautologies are tautological."

Your sentence preceding this one laid out some issues; you probably could have left it at that <shrug>.

andrew_3y ago

could have done without the editorial critique as well.

j / k navigate · click thread line to collapse