3 ms·
Looks great. For someone who's not taken the plunge into Serverless yet, how would the costs compare to the more traditional options of hosting an app? i.e. a R
by jack_riminton 6y ago
Looks great. For someone who's not taken the plunge into Serverless yet, how would the costs compare to the more traditional options of hosting an app? i.e. a Rails/React app on Heroku
Of course 'it depends', but roughly speaking?
- jayair 6y agoYeah it does depend. But the numbers that get touted are at around 70-80%. But here are the caveats. If your usage patterns are 24/7 and very predictable. You can design your infrastructure to be cheaper than the Lambda. However for most other cases, including us at Seed (we use serverless extensively). It's so much more cheaper that we wouldn't do it any other way. If you have a hobby project, it'll be in the free tier. Some more details here — https://serverless-stack.com/chapters/why-create-serverless-apps.html https://serverless-stack.com/chapters/why-create-serverless-...
- jack_riminton 6y agoGreat reply, thanks will give it a go once I learn how!
- jayair 6y agoOh I'll add, Seed is heavily influenced by Heroku. It's a little like Heroku but for Serverless.
- loosescrews 6y agoIsn't Heroku serverless? It is a PaaS offering similar to Lambda and Google's various PaaS offerings that generally get branded as serverless.
- jayair 6y agoI should clarify, when I mentioned serverless, I really meant serverless on AWS. Broadly speaking PaaS is similar to serverless. The main thing I look for as a user is, the per millisecond billing, the ability to scale up instantly and scale all the way down to zero.