"Like Rails but serverless ", I wonder what's their definition of servers? As far as I understand it relies on .. AWS servers!
[deleted]
Ruby on Jets: Like Rails but serverless
31–40 of 92 posts
Re: Ruby on Jets: Like Rails but serverless
#32Ruby 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?
Because Ruby is OOP, Elixir is functional. Some people just get used to OOP to structure program.
Re: Ruby on Jets: Like Rails but serverless
#33Wondering why this framework isn't more talked about, especially amongst rails devs to take advantage of AWS Lambda.
Why though? what benefits does that give us?
Re: Ruby on Jets: Like Rails but serverless
#34"Like Rails but serverless ", I wonder what's their definition of servers? As far as I understand it relies on .. AWS servers!
Locking yourself into servers of one company doesn't sound like progress to me
Re: Ruby on Jets: Like Rails but serverless
#35Does 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.
> granularly tweak resource utilization on a per-operation basis
This is a really good point. Either I took a thorny path learning Lambda or they don't make it terribly obvious that when you pre-allocate larger amounts of RAM (thus more $$$ in GB/s cost) you also gain substantially better CPU performance.
So when you have a compute intensive task with a low memory footprint and want to improve latency, you may actually want to allocate lots of unused RAM.
Re: Ruby on Jets: Like Rails but serverless
#36Wondering why this framework isn't more talked about, especially amongst rails devs to take advantage of AWS Lambda.
Why though? what benefits does that give us?
I’m not entirely sure I wanted to see what HN thought. I was thinking if one’s already using rails+aws are there workloads that are not core app functionality, not frequent, but that when they run need to serve a large number of requests that Jets might be the right tool for the job?
Re: Ruby on Jets: Like Rails but serverless
#37Am 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…
If it was only AWS.
Cloud OSes are nothing more than a return back to timesharing in new clothes.
The pendulum has swung back into thin clients, browsers and mobile OSes are the new terminals.
Re: Ruby on Jets: Like Rails but serverless
#38Wondering 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.
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.
Re: Ruby on Jets: Like Rails but serverless
#39It looks like Ruby on Jets makes you 100% dependent on 1 company: AWS/Amazon; not an evolution I'd welcome.
Re: Ruby on Jets: Like Rails but serverless
#40It looks like Ruby on Jets makes you 100% dependent on 1 company: AWS/Amazon; not an evolution I'd welcome.
Yeah I'd agree, this was the instant turnoff for me, I don't like Amazon. But I totally understand people trying to build a more modern Ruby framework.