5 ms·

So, I came across this when I was looking for Lambda support for Ruby (aws). I came to the same conclusion as this thread (and FooBarWidget is here evidently t

by yebyen 8y ago

So, I came across this when I was looking for Lambda support for Ruby (aws). I came to the same conclusion as this thread (and FooBarWidget is here evidently telling us we're not wrong), that it was unmaintained and won't be maintained again soon, unless someone steps up. I'm just wondering does anyone use Lambda with Ruby (with this or otherwise?) Is it as kludgy as it looks? I found a couple of better looking options to do FaaS-style development on Kubernetes with Ruby, namely riff and kubeless, but I don't expect supporting code to come for AWS or from Amazon any time soon. Anyone who uses Ruby disagree?

pmontra 8y ago
I used Lambda with mRuby, the embeddable version of the language. The (subset of) Ruby code is compiled into a bytecode that is linked to a C program that is run in Lambda and interprets it. The downside is that you either write all your Ruby code or use the few Ruby gems that work in mRuby. They must also be compiled and linked to the main C program. https://github.com/mruby/mruby https://github.com/mruby/mruby A getting started from 2012 https://matt.aimonetti.net/posts/2012/04/25/getting-started-with-mruby/ https://matt.aimonetti.net/posts/2012/04/25/getting-started-...
- yebyen 8y ago
  Thanks for that! I wasn't going to find that on my own. You said 'used' as in past-tense... mind sharing why you moved on and what you moved on to? (Did you implement serverless but in another language? mRuby was too cumbersome from what it sounds like, did you keep Ruby but ditch serverless? How is your stuff hosted today?)
  - pmontra 8y ago
    It was an experiment to get used with mRuby. I didn't build anything serious with serverless technologies because my customers are not on them. Some other experiments with Nodejs on Lambda, that's all. However my feeling is that the extra steps from source to binary obe had to take with mRuby are not worth the effort. If one stays within the 100 ms billing unit of Lambda (is it still like that?) it's much easier to deploy interpreted code than compiled one.

by yebyen 8y ago

pmontra 8y ago

I used Lambda with mRuby, the embeddable version of the language. The (subset of) Ruby code is compiled into a bytecode that is linked to a C program that is run in Lambda and interprets it. The downside is that you either write all your Ruby code or use the few Ruby gems that work in mRuby. They must also be compiled and linked to the main C program. https://github.com/mruby/mruby https://github.com/mruby/mruby A getting started from 2012 https://matt.aimonetti.net/posts/2012/04/25/getting-started-with-mruby/ https://matt.aimonetti.net/posts/2012/04/25/getting-started-...

yebyen 8y ago
Thanks for that! I wasn't going to find that on my own. You said 'used' as in past-tense... mind sharing why you moved on and what you moved on to? (Did you implement serverless but in another language? mRuby was too cumbersome from what it sounds like, did you keep Ruby but ditch serverless? How is your stuff hosted today?)
- pmontra 8y ago
  It was an experiment to get used with mRuby. I didn't build anything serious with serverless technologies because my customers are not on them. Some other experiments with Nodejs on Lambda, that's all. However my feeling is that the extra steps from source to binary obe had to take with mRuby are not worth the effort. If one stays within the 100 ms billing unit of Lambda (is it still like that?) it's much easier to deploy interpreted code than compiled one.