Hacker News new | past | comments | ask | show | jobs | submit login

Given how trivial it is to set up serverless Rails using something like ECS Fargate, the benefit of running specifically on Lambda is lower than migrating off a tried and tested technology.



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.


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.


> ... 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>.


could have done without the editorial critique as well.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: