6 ms·

Way to go, Ruby support!!!! I am irrationally excited about this, if I wanted to do Serverless Ruby up until now, my nearest options were (some community-suppor

by yebyen 8y ago

Way to go, Ruby support!!!! I am irrationally excited about this, if I wanted to do Serverless Ruby up until now, my nearest options were (some community-supported thing with "traveling ruby" on AWS, or...) Kubeless, or Project Riff https://www.serverless-ruby.org/ https://www.serverless-ruby.org/ We've been waiting! I thought this would never happen. Eating major crow today, as I've assumed for a long time that AWS's lack of Ruby support in Lambda was an intentional omission and sign that they are not our friends. I will change my tone starting today! (edit: Or Google Cloud Functions, or probably some other major ones I've missed...)

aantix 8y ago
You're missing Ruby on Jets. http://rubyonjets.com/ http://rubyonjets.com/ It's pretty comprehensive. And it was able to cache the execution context (and keep the cache warm) to approach native execution times. All of this obviously before native Ruby support was announced.
- yebyen 8y ago
  Awesome! Thank you
  - tongueroo 8y ago
    Happy to say that Jets is now on the official AWS Ruby runtime: https://blog.boltops.com/2018/12/12/official-aws-ruby-support-for-jets-serverless-framework https://blog.boltops.com/2018/12/12/official-aws-ruby-suppor...
jon-wood 8y ago
I had a play with it this evening implementing a basic webhook handler and it’s super smooth - I hooked a Ruby Lambda function up to API Gateway and everything just works. I suspect you could very easily create some sort of Rack shim on top as well, effectively giving near free, infinitely scalable, Ruby app servers (assuming you can keep the start time down).
- jon-wood 8y ago
  It turns out one of the samples from AWS is that shim, and it’s super elegant - at least in theory I think you could deploy almost any Ruby web app to Lambda with minimal effort.
- schappim 8y ago
  I just did the same thing, but things fall apart when you need to use gems w/ native extension (mysql). I'll need to investigate the native runtime route.
  - yebyen 8y ago
    That's interesting... gems w/ native extension, I'm not sure if that was on my test case list, but it should be. Thx...
freedomben 8y ago
You're not the only one. I have a co-worker that had inside information who said he believed it was part of a feud between Ruby and python, since there are a lot of python devs working on aws. I didn't believe him for a while, but was sort of starting too since it is clear that there is demand for Ruby on lambda
- ksec 8y ago
  So Python users are actively trying to kill Ruby? Stopping their Employers from supporting Ruby? Not the first time I heard of it. But actively trying to kill it is a whole different level.
  - yebyen 8y ago
    OK, I am skeptical of this too, but it's a thing. 10 minutes before the announcement that OP is about here, one of our architects copied this line from an AWS slide deck: > AWS Lambda supports code written in Node.js (JavaScript), Python, Java (Java 8 compatible), and C# (.NET Core) and Go. ... and intimated that, if your language is not on this list, you're not part of the dominant side of the industry. As if to say, to the large cohort of Ruby developers we have on staff, "You guys are basically irrelevant because Amazon doesn't care if you can work on the pride and joy of their platform or not." Every other week I've got a different person telling me that Ruby is a quirky niche language and I should get with the times and become a full-stack JavaScript developer instead. I get it, there's growth in other languages, but if I have years of experience that means I should throw it away? Sometimes these conversations get really personal, too. Almost like we're choosing a football team, you'd think it was politics or religion that we're debating...
    - ksec 8y ago
      So basically Ruby is now being treated like PHP.
      - yebyen 8y ago
        Hah.. bazinga! I've learned a lot since I started writing Ruby at my first permanent job in 2010, and I'm 100% sure that if I looked at any of the early Ruby code I wrote in 2010, I'd grumble and groan at it just as hard as if you showed me some PHP code that I wrote at my first co-op job as a sophomore in college. You can write great code in any language. You can also write a shanty-town or big ball of mud, in practically any language. I think it's unfair to say that PHP in and of itself represents a "bad code smell." But I'm also fairly sure from anecdotal evidence that I'm in the minority. I understand completely now. Thanks for that.

by yebyen 8y ago

aantix 8y ago

You're missing Ruby on Jets. http://rubyonjets.com/ http://rubyonjets.com/ It's pretty comprehensive. And it was able to cache the execution context (and keep the cache warm) to approach native execution times. All of this obviously before native Ruby support was announced.

yebyen 8y ago
Awesome! Thank you
- tongueroo 8y ago
  Happy to say that Jets is now on the official AWS Ruby runtime: https://blog.boltops.com/2018/12/12/official-aws-ruby-support-for-jets-serverless-framework https://blog.boltops.com/2018/12/12/official-aws-ruby-suppor...

jon-wood 8y ago

I had a play with it this evening implementing a basic webhook handler and it’s super smooth - I hooked a Ruby Lambda function up to API Gateway and everything just works. I suspect you could very easily create some sort of Rack shim on top as well, effectively giving near free, infinitely scalable, Ruby app servers (assuming you can keep the start time down).

jon-wood 8y ago
It turns out one of the samples from AWS is that shim, and it’s super elegant - at least in theory I think you could deploy almost any Ruby web app to Lambda with minimal effort.
schappim 8y ago
I just did the same thing, but things fall apart when you need to use gems w/ native extension (mysql). I'll need to investigate the native runtime route.
- yebyen 8y ago
  That's interesting... gems w/ native extension, I'm not sure if that was on my test case list, but it should be. Thx...

freedomben 8y ago

You're not the only one. I have a co-worker that had inside information who said he believed it was part of a feud between Ruby and python, since there are a lot of python devs working on aws. I didn't believe him for a while, but was sort of starting too since it is clear that there is demand for Ruby on lambda

ksec 8y ago
So Python users are actively trying to kill Ruby? Stopping their Employers from supporting Ruby? Not the first time I heard of it. But actively trying to kill it is a whole different level.
- yebyen 8y ago
  OK, I am skeptical of this too, but it's a thing. 10 minutes before the announcement that OP is about here, one of our architects copied this line from an AWS slide deck: > AWS Lambda supports code written in Node.js (JavaScript), Python, Java (Java 8 compatible), and C# (.NET Core) and Go. ... and intimated that, if your language is not on this list, you're not part of the dominant side of the industry. As if to say, to the large cohort of Ruby developers we have on staff, "You guys are basically irrelevant because Amazon doesn't care if you can work on the pride and joy of their platform or not." Every other week I've got a different person telling me that Ruby is a quirky niche language and I should get with the times and become a full-stack JavaScript developer instead. I get it, there's growth in other languages, but if I have years of experience that means I should throw it away? Sometimes these conversations get really personal, too. Almost like we're choosing a football team, you'd think it was politics or religion that we're debating...
  - ksec 8y ago
    So basically Ruby is now being treated like PHP.
    - yebyen 8y ago
      Hah.. bazinga! I've learned a lot since I started writing Ruby at my first permanent job in 2010, and I'm 100% sure that if I looked at any of the early Ruby code I wrote in 2010, I'd grumble and groan at it just as hard as if you showed me some PHP code that I wrote at my first co-op job as a sophomore in college. You can write great code in any language. You can also write a shanty-town or big ball of mud, in practically any language. I think it's unfair to say that PHP in and of itself represents a "bad code smell." But I'm also fairly sure from anecdotal evidence that I'm in the minority. I understand completely now. Thanks for that.