Need advice about which tool to choose?Ask the StackShare community!
The Friendliest.app started on Heroku (both app and db) like most of my projects. The db on Heroku was on the cusp of becoming prohibitively expensive for this project.
After looking at options and reading recommendations we settled on Render to host both the application and db. Render's pricing model seems to scale more linearly with the application instead of the large pricing/performance jumps experienced with Heroku.
Migration to Render was extremely easy and we were able to complete both the db and application moves within 24 hours.
The only thing we're really missing on Render is a CLI. With Heroku, we could manage everything from the command line in VSCode. With Render, you need to use the web shell they provide.
I'm transitioning to Render from heroku. The pricing scale matches my usage scale, yet it's just as easy to deploy. It's removed a lot of the devops that I don't like to deal with on setting up my own raw *nix box and makes deployment simple and easy!
Clustering I don't use clustering features at the moment but when i need to set up clustering of nodes and discoverability, render will enable that where Heroku would require that I use an external service like redis.
Restarts The restarts are annoying. I understand the reasoning, but I'd rather watch my service if its got a memory leak and work to fix it than to just assume that it has memory leaks and needs to restart.
Pros of AWS Elastic Beanstalk
- Integrates with other aws services77
- Simple deployment65
- Fast44
- Painless28
- Free16
- Independend app container3
- Well-documented3
- Postgres hosting2
- Ability to be customized2
Pros of Google App Engine
- Easy to deploy144
- Auto scaling106
- Good free plan80
- Easy management62
- Scalability56
- Low cost35
- Comprehensive set of features32
- All services in one place28
- Simple scaling22
- Quick and reliable cloud servers19
- Granular Billing6
- Easy to develop and unit test5
- Monitoring gives comprehensive set of key indicators4
- Really easy to quickly bring up a full stack3
- Create APIs quickly with cloud endpoints3
- No Ops2
- Mostly up2
Pros of Heroku
- Easy deployment705
- Free for side projects459
- Huge time-saver374
- Simple scaling348
- Low devops skills required261
- Easy setup190
- Add-ons for almost everything174
- Beginner friendly153
- Better for startups150
- Low learning curve133
- Postgres hosting48
- Easy to add collaborators41
- Faster development30
- Awesome documentation24
- Simple rollback19
- Focus on product, not deployment19
- Natural companion for rails development15
- Easy integration15
- Great customer support12
- GitHub integration8
- Painless & well documented6
- No-ops6
- I love that they make it free to launch a side project4
- Free4
- Great UI3
- Just works3
- PostgreSQL forking and following2
- MySQL extension2
- Security1
- Able to host stuff good like Discord Bot1
- Sec0
Sign up to add or upvote prosMake informed product decisions
Cons of AWS Elastic Beanstalk
- Charges appear automatically after exceeding free quota2
- Lots of moving parts and config1
- Slow deployments0
Cons of Google App Engine
Cons of Heroku
- Super expensive27
- Not a whole lot of flexibility9
- No usable MySQL option7
- Storage7
- Low performance on free tier5
- 24/7 support is $1,000 per month2
Sign up to add or upvote consMake informed product decisions
What is AWS Elastic Beanstalk?
What is Google App Engine?
What is Heroku?
Need advice about which tool to choose?Ask the StackShare community!
What companies use AWS Elastic Beanstalk?
What companies use Google App Engine?
What companies use Heroku?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with AWS Elastic Beanstalk?
What tools integrate with Google App Engine?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17
+8
+47+39+23+25
+25+24