Earlier quoted context omitted.
You will definitely run into more cold starts though, if that is a consideration for your project
A serverless function that never cold-starts is just a container.
That doesn’t mean that more cold starts aren’t bad.
Ruby on Jets: Like Rails but serverless
21–30 of 92 posts
Re: Ruby on Jets: Like Rails but serverless
#22Am I the only one who is kinda irritated with how AWS has effectively created a piecemeal proprietary operating system and slowly started displacing good server ops? All while "supporting" open-source development. I really don't want to be an AWS engineer. I like being able to host my own tools when I want. Sorry for the rant, serverless stuff in general is cool. As a followup... I'm curious if anyone can recommend s…
They started it, not there's many services providing this now. You don't have to go with AWS for a few years now if you want to go serverless. (Even if they are the most popular) For self hosted context there's https://fnproject.io/ for example.
Re: Ruby on Jets: Like Rails but serverless
#23Earlier quoted context omitted.
I have found the Serverless framework to be great. Never really had to deal with AWS console at any point https://www.serverless.com/
Sure its a layer of abstraction but super leaky if you want to do anything meaningful.
Well for some values of "meaningful" OK, sure.
But lots of times a plastic bucket, even with a leak, is a better tool for the job than an extruder, mold, and warehouse full of polymer.
I had to build a parallel CI pipeline once that was like: when this, run a FaaS function, then when this that or whipesnicket, run one of these other functions, then run this thing that moves some things from here to there and posts the results to zulip chat.
I literally spent 2 hours in AWS docs, got to "ugh, don't wanna know this, unlikely to use again" and then spent one hour in the serverless docs building it that way, and then it ran for 4 years. (Last year, I finally replaced it with GitHub Actions.)
Admittedly this wasn't a profound and moving tale of heroic ops or anything, but the Serverless framework proved to be pretty nifty for my use case. (Haven't used it since, but would again in a similar circumstance.)
Re: Ruby on Jets: Like Rails but serverless
#24Earlier quoted context omitted.
A serverless function that never cold-starts is just a container.
That doesn’t mean that more cold starts aren’t bad.
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.
Re: Ruby on Jets: Like Rails but serverless
#25Am I the only one who is kinda irritated with how AWS has effectively created a piecemeal proprietary operating system and slowly started displacing good server ops? All while "supporting" open-source development. I really don't want to be an AWS engineer. I like being able to host my own tools when I want. Sorry for the rant, serverless stuff in general is cool. As a followup... I'm curious if anyone can recommend s…
[deleted]
Re: Ruby on Jets: Like Rails but serverless
#26Ruby syntax with a focus on fine grained transforming functions. Isn’t that essentially exactly what Elixir/Phoenix tries to provide, but without the Amazon lock-in or price tag?
[deleted]
Re: Ruby on Jets: Like Rails but serverless
#27Am I the only one who is kinda irritated with how AWS has effectively created a piecemeal proprietary operating system and slowly started displacing good server ops? All while "supporting" open-source development. I really don't want to be an AWS engineer. I like being able to host my own tools when I want. Sorry for the rant, serverless stuff in general is cool. As a followup... I'm curious if anyone can recommend s…
we're building open serverless-centered cloud-like p2p network to aolve exactly this issue. to eliminate vendor lock and make it open so anyone can both provide and consume compute resources and develop backends on top of that.
Re: Ruby on Jets: Like Rails but serverless
#28Does it really make sense to map each controller method to a lambda? Wouldn’t it make more sense to have gateway route to a single function per controller and then do the method routing inside that function? You’re going to get a lot of lambda functions otherwise.
Nothing prevents you from routing everything to a single function, no need to even split by controller.
The disadvantage of having a huge number of Lambdas is the ratio of cold starts. The advantage is that you can granularly tweak resource utilization on a per-operation basis.
Re: Ruby on Jets: Like Rails but serverless
#29Wondering why this framework isn't more talked about, especially amongst rails devs to take advantage of AWS Lambda.
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.
Re: Ruby on Jets: Like Rails but serverless
#30"Like Rails but serverless", I wonder what's their definition of servers?
As far as I understand it relies on .. AWS servers!