Appreciate the feedback and I’m interested to see if it picks up momentum. Our functions repo is public; feel free to x-link an issue between there and here!
Unfortunately I’m not holding my breath at this point for additional language support. There have been many requests for Python as well as Ruby in other threads (What Function-ality would you like to see?) (Python lambda functions?) for months now. I understand this stuff takes time, but “it’s on our feature request list” isn’t really an answer. Is Ruby support actually planned? Q3? Q4? To add fuel to the fire, I’ll soon be releasing a new Ruby microframework for serverless functions that will work on Vercel, OpenFaaS, or any Rack-compatible configuration—perfect for running alongside Bridgetown, Jekyll, Middleman, etc.—and I’d love to support Netlify Functions as well. But if it’s not under active development…
I think you’re wise not to hold your breath, and to find a different way to make this happen such as deploying to your own AWS account directly.
You’re one of less than 10 people to ask for this, so the demand isn’t there for us to even begin investigating implementing it yet. To clarify, “having an open feature request” does not mean “Netlify plans to implement it”, so the amount of time ago it was requested, or how long it might take you to implement does not really impact anything on our side.
Rather, it means:
- that our Product Management team has been made aware of the request
- that our Support team will make sure to respond in this thread (and individually to any helpdesk cases that have been opened on the topic) in case we either implement it, or decide never to implement it. Neither of these things has happened or is likely to happen soon, just to set expectations. TL;DR it’s not a bad idea, but we’ve got a few hundred different ideas, most of which will enable thousands of workflows, rather than dozens
Your framework is a very interesting data point to consider in those plans, so thank you much for raising it! I will make sure our product team is aware of this specific post, rather than the request in general, but I know what is on our roadmap for the next couple of quarters it is pretty full, so even if it becomes popular amongst our highest-paying customers, that might not move the needle much considering the work we already have planned. Or it might - fortunately I am not the one choosing what we do
We don’t give timelines for releases that may not happen, so what you can be sure of based on our lack of saying anything is that we have no solid plans to release this feature (yet).
Hopefully that clears things up, but let me know if not.
Thanks for such an in-depth response! That’s a real bummer. I know of plenty of other Ruby hosting options but it does make it more challenging to stick with Netlify for the static part. Anyway, once again I appreciate the info.
Yeah, this is a tough one. My full time role right now is actually that of a RoR back end with a massive PWA front end, so I totally understand both sides of the equation. Honestly though, I haven’t written more than 2 Lambdas in Ruby even though it’s been out for a while now - it’s sort of just a late addition to an already-set status quo of “Lambda === JS”
@jaredwhite while I too would love to see Netlify grant Ruby Function support (although I’m not sold that I would actually use it tbh), I think the best thing you could do is convince the community to want it Netlify’s product team’s goal is always to provide the biggest number of folks the enhancements they want as fast as reasonable… if you can get more folks on board with the desire, the Product team will definitely hear that!
Yeah, I see it is a bit of a chicken and egg thing… People aren’t always going to demand something that doesn’t exist yet… I think the serverless computing mindset hasn’t really taken hold in many sectors of the Ruby community, but the flipside is the tooling often hasn’t been there in the first place. Plus Ruby isn’t as popular in DevOps as something dedicated to massive performance gains such as Go or Rust for example.
All that being said…for general web server framework coding I think Ruby still shines brightly and that’s why I’m hoping to get the microframework/functions story to take off as well.
OK folks — this is a pre-pre-release, but I think I’ve gotten it off to a pretty decent start now. I’ve been working on a micro-framework called Phaedra that’s well-suited for use in serverless function contexts (and also Docker). In a nutshell, you can add
/api/* to your Bridgetown (or Jekyll, or Middleman) sites.
There’s a section in the Readme about how to use Netlify’s proxy rewrites to set up the
/api endpoint. One easy way to get Phaedra up and running to use use Fly.io. Using Docker you can deploy the API app to a global network of container hosts in minutes.
I could envision this being super helpful for providing services like authentication, paywalled content, payment processing (Stripe, etc.), and other bits of functionality on the “A” side of JAMstack.
Another thing I’ve been experimenting with is connecting to a MongoDB database using something like ScaleGrid or Atlas. Makes it super-easy to store and retrieve JSON “in the cloud” right from your Ruby API.
Anyway, I welcome your feedback and suggestions!
We use a Ruby backend as well, and the repo is massive. We run it on hosts, not in functions, because functions aren’t suitable for so much of what it does:
- long billing runs
- asynchronous “can be done eventually” work
- some calls longer than 26 seconds, though generally not for functions that would be called synchronously from a webpage
- can make dozens of database calls
I know that some people really do have small, synchronous tasks that run from Ruby and could reliably work as a function. But I think that others (like us) have ruby that really needs a long-running server process rather than trying to cram everything into a lambda.
Note that we have NO intention of becoming a general purpose ruby/php/node host and running server-side code like that.
Hey, that’s super awesome—I didn’t realize Netlify used a bunch of Ruby in its own backend.
Good points about functions vs. larger server-side applications. What’s exciting to me is there are so many opportunities now to pick exactly the right hosting environment for the job. Run the gamut from Static Builds -> Functions -> Docker containers -> Cloud VMs -> Own your own metal… (that last one is probably not too applicable anymore, but I suspect it’s still best for a tiny % of apps)