[HN Gopher] Designing a Ruby Serverless Runtime
___________________________________________________________________
Designing a Ruby Serverless Runtime
Author : kiyanwang
Score : 29 points
Date : 2021-01-22 12:07 UTC (1 days ago)
(HTM) web link (daniel-azuma.com)
(TXT) w3m dump (daniel-azuma.com)
| xal wrote:
| This is really well designed. Kudos.
|
| Especially good is treating the Gemfile.lock as input for the the
| file system image and requiring it.
| crazydoggers wrote:
| Is there a specific reason Procs weren't used? I didn't see a
| reason mentioned in the article.
| config_yml wrote:
| This looks really well done, congrats!
|
| How are people managing Cloud Functions these days? Any ruby
| tools around this topic? I'm excited to try this on the weekends.
|
| edit: also huge thanks for unbundling the google-cloud ruby gems.
| metaskills wrote:
| Glad Google is catching up with Ruby. But if you really want to
| learn how I am doing this with AWS and how easy it is to handle
| Rails on Lambda, check out the Lamby work here.
| https://lamby.custominktech.com
| sam0x17 wrote:
| Hey Daniel this is super cool and I appreciate all you've done
| over the years to support our use of Ruby on App Engine.
|
| This is extremely exciting -- I've always loved the idea of
| running Ruby in a serverless context, and I've always preferred
| Google Cloud Functions to Lambda for its simplicity. This is
| super good news in general.
|
| I definitely recommend taking a look at Ruby on Jets for
| inspiration, which brings a very rails-like serverless Ruby
| framework to fruition in AWS Lambda.
___________________________________________________________________
(page generated 2021-01-23 23:01 UTC)