Ruby on Jets: Like Rails but Serverless

Re:Ruby on Jets: Like Rails but Serverless by astuyvenberg on Saturday January 21, 2023 @11:56PM (#34474448)

It's typically fine - AWS bills by GB/s (in ms), not by number of functions in an account.

There are limits to the number of functions per account, and number of resources per CloudFormation stack (etc); but within those parameters it's usually a good idea to use one function for a specific controller or action. This allows you to limit IAM permissions, configure memory/CPU, and define associated resources at a per-controller level.

[ Parent | on HN ]

Re:Ruby on Jets: Like Rails but Serverless by bigfoot675 on Sunday January 22, 2023 @12:17AM (#34474558)

You will definitely run into more cold starts though, if that is a consideration for your project

[ Parent | on HN ]

Re:Ruby on Jets: Like Rails but Serverless by philwelch on Sunday January 22, 2023 @01:25AM (#34474936)

A serverless function that never cold-starts is just a container.

[ Parent | on HN ]

Re:Ruby on Jets: Like Rails but Serverless by KyeRussell on Sunday January 22, 2023 @01:48AM (#34475046)

That doesn’t mean that more cold starts aren’t bad.

[ Parent | on HN ]

Re:Ruby on Jets: Like Rails but Serverless by philwelch on Sunday January 22, 2023 @04:08AM (#34475650)

Sure but if you can’t tolerate the added latency of a cold start, serverless might not be right for you.

Conversely, if you’re doing something like processing message queues and you don’t care about latency at all, serverless is perfect.

[ Parent | on HN ]

Re:Ruby on Jets: Like Rails but Serverless by aa_memon on Saturday January 21, 2023 @11:58PM (#34474460)

I'm guessing it also helps keep deploys small (atomic?) when a controller method changes. The unmodified lambdas stay untouched.

[ Parent | on HN ]

Re:Ruby on Jets: Like Rails but Serverless by foolfoolz on Sunday January 22, 2023 @12:44AM (#34474709)

this makes logging much more difficult to search through

[ Parent | on HN ]