Need advice about which tool to choose?Ask the StackShare community!
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.
I host my stuff with Hetzner in large part because their tools are straighforward and easy to use and they're based in a country whose laws respect privacy.
If you're hosting with a company that's US-based, you have to worry about their laws affecting your site, which isn't an acceptable requirement in my opinion.
DigitalOcean was where I began; its USD5/month is extremely competitive and the overall experience as highly user-friendly.
However, their offerings were lacking and integrating with other resources I had on AWS was getting more costly (due to transfer costs on AWS). Eventually I moved the entire project off DO's Droplets and onto AWS's EC2.
One may initially find the cost (w/o free tier) and interface of AWS daunting however with good planning you can achieve highly cost-efficient systems with savings plans, spot instances, etcetera.
Do not dive into AWS head-first! Seriously, don't. Stand back and read pricing documentation thoroughly. You can, not to the fault of AWS, easily go way overbudget. Your first action upon getting your AWS account should be to set up billing alarms for estimated and current bill totals.
Pros of Amazon EC2
- Quick and reliable cloud servers644
- Scalability515
- Easy management391
- Low cost276
- Auto-scaling269
- Market leader88
- Backed by amazon80
- Reliable78
- Free tier66
- Easy management, scalability57
- Flexible12
- Easy to Start10
- Web-scale9
- Widely used8
- Elastic8
- Node.js API7
- Industry Standard4
- Lots of configuration options3
- GPU instances2
- Amazing for individuals1
- Extremely simple to use1
- All the Open Source CLI tools you could want.1
- Simpler to understand and learn1
Pros of Firebase
- Realtime backend made easy357
- Fast and responsive261
- Easy setup233
- Real-time206
- JSON184
- Free126
- Backed by google120
- Angular adaptor80
- Reliable62
- Great customer support36
- Great documentation25
- Real-time synchronization22
- Mobile friendly19
- Rapid prototyping17
- Great security12
- Automatic scaling10
- Freakingly awesome9
- Chat8
- Super fast development8
- Angularfire is an amazing addition!8
- Awesome next-gen backend6
- Ios adaptor6
- Firebase hosting5
- Built in user auth/oauth5
- Very easy to use4
- Brilliant for startups3
- It's made development super fast3
- Great3
- Low battery consumption2
- The concurrent updates create a great experience2
- I can quickly create static web apps with no backend2
- Great all-round functionality2
- Speed of light2
- Easy to use1
- Good Free Limits1
- .net1
- Serverless1
- Large1
- JS Offline and Sync suport1
- Easy Reactjs integration1
- Faster workflow1
- Push notification1
Pros of Heroku
- Easy deployment703
- Free for side projects460
- Huge time-saver374
- Simple scaling348
- Low devops skills required261
- Easy setup189
- Add-ons for almost everything174
- Beginner friendly153
- Better for startups149
- Low learning curve133
- Postgres hosting47
- Easy to add collaborators41
- Faster development30
- Awesome documentation24
- Simple rollback19
- Focus on product, not deployment18
- Easy integration15
- Natural companion for rails development15
- Great customer support11
- GitHub integration7
- No-ops6
- Painless & well documented5
- Just works3
- Free3
- PostgreSQL forking and following2
- I love that they make it free to launch a side project2
- Great UI2
- MySQL extension2
Sign up to add or upvote prosMake informed product decisions
Cons of Amazon EC2
- Ui could use a lot of work13
- High learning curve when compared to PaaS6
- Extremely poor CPU performance3
Cons of Firebase
- Can become expensive25
- No open source, you depend on external company14
- Scalability is not infinite14
- Not Flexible Enough9
- Cant filter queries5
- Very unstable server3
- Too many errors2
- No Relational Data2
Cons of Heroku
- Super expensive22
- No usable MySQL option6
- Not a whole lot of flexibility6
- Storage5
- Low performance on free tier4