85 karma · joined February 24, 2010
* Paying only for compute time/requests, if the API is not being accessed for a period of time, it's free - on a regular instance, you'd be paying for idle time
* Automatic scaling
* Simple deployment
The downsides include:
* Irregular response times due to cold containers
* Slower request/response cycle due to overhead in Lambda + API Gateway
To get a large Rails app operational on Lambda, Jets is the way to go.
Seems like it is just not for you, too bad. Your comment would be more useful if you could elaborate on what it is that you find useful, though.
Say I need to run a simple background job, that would be $36/month - almost 2 linodes. And with the excellent articles on http://articles.slicehost.com, I find that setting up a vps takes no more than a few hours. Plus, it's a lot of fun and a good learning experience!
I don't see how Heroku could do it much cheaper though, when you look at the pricing of Amazon EC2 instances which their platform runs on.