Need advice about which tool to choose?Ask the StackShare community!
Hasura vs Heroku: What are the differences?
## Introduction
This Markdown code highlights the key differences between Hasura and Heroku in a concise manner suitable for website integration.
## Key Differences Between Hasura and Heroku
1. **Deployment Flexibility**: Hasura primarily focuses on deploying and managing GraphQL APIs, offering a variety of deployment options such as serverless and container-based solutions. On the other hand, Heroku is a cloud platform that supports multiple programming languages and frameworks, providing a more general-purpose deployment environment.
2. **Databases Integration**: Hasura allows seamless integration with databases like PostgreSQL, providing instant GraphQL APIs on top of them. In contrast, while Heroku supports various databases, the setup and maintenance of these database connections require more manual configuration compared to Hasura's automated approach.
3. **Infrastructure Management**: Hasura automates many aspects of infrastructure management related to GraphQL APIs, including real-time event handling, access control, and data relationships. Heroku, being a platform-as-a-service (PaaS) solution, simplifies overall application deployment and management but may require additional configuration for specific features like real-time capabilities.
4. **Scalability and Performance**: Hasura is designed for high-traffic and scalable applications, offering features like caching, query optimization, and load balancing to enhance performance. While Heroku also supports scalability through dynos and add-ons, Hasura's focus on GraphQL APIs enables more fine-tuning for optimizing performance in real-time applications.
5. **Community Support and Ecosystem**: Hasura has a strong community of developers and contributors dedicated to improving the platform's capabilities and offering support through forums, documentation, and tutorials. While Heroku also has an active community, its ecosystem is broader due to supporting various programming languages and frameworks, resulting in a more diversified community with different areas of expertise.
6. **Cost Analysis**: Hasura offers a more cost-effective solution for projects primarily focused on GraphQL APIs, with pricing plans tailored to different use cases and scalability requirements. In contrast, Heroku's pricing structure is more generalized, covering a wider range of application types and deployment scenarios, which may result in higher costs for specific use cases compared to Hasura's optimized pricing models.
## Summary
In summary, Hasura and Heroku differ in deployment flexibility, databases integration, infrastructure management, scalability and performance features, community support, and cost analysis, catering to distinct needs in the development and deployment of web applications.
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.
We wanted to save as much time as possible when writing our back-end, therefore Apollo was out of the question, we went for an auto-generated API instead. Hasura looked good in the beginning, but we wanted to retain the ability to add a few manual resolvers and modifications to auto-generated ones, which ruled out Hasura. Postgraphile with its Plug-In architecture was the right choice for us, we never regretted it!
Pros of Hasura
- Fast23
- Easy GraphQL subscriptions18
- Easy setup of relationships and permissions16
- Automatically generates your GraphQL schema15
- Minimal learning curve15
- No back-end code required13
- Works with new and existing databases13
- Instant production ready GraphQL12
- Great UX11
- Low usage of resources4
- Simple4
Pros of Heroku
- Easy deployment703
- 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 Hasura
- Cumbersome validations3
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