I just built a tiny application in Ruby for AWS Lambda using the Serverless Framework. It's a fallback application that only needs to catch SMS messages from Tw

I just built a tiny application in Ruby for AWS Lambda using the Serverless Framework. It's a fallback application that only needs to catch SMS messages from Twilio when our main application falls down. So a perfect fit for always available but seldom running and cold starts shouldn't matter. I implemented services such as a cron job and sending email (for a daily administrative report) in just a line of two of code. Compared to Rails, there's hardly any code. But compared to Rails, there's a lot of configuration of infrastructure (in one serverless.yml file) and it wasn't easy to find blog posts or examples. Implementing logging? Shouldn't be difficult but it was because of the AWS permissions structure. Ruby gems? Complicated especially for any that have native extensions. And yes, Amazon and Serverless have documentation but the wonderful Rails community has created much richer resources for solving every little problem. I'm eager to try implementing our application in Jets to compare it to the Serverless Framework implementation. It'd be nice to stand up an application on AWS as easily as we build a Rails application and deploy to Heroku. That said, maybe after figuring out how to use the Serverless Framework, there's not much reason to use Jets. I'm curious.