Need advice about which tool to choose?Ask the StackShare community!
Apollo vs Heroku: What are the differences?
Deployment Environment: One key difference between Apollo and Heroku is the deployment environment. Apollo is an open-source GraphQL server that can be self-hosted on any infrastructure, giving users complete control over the deployment process. On the other hand, Heroku is a cloud-based platform as a service (PaaS) that simplifies deployment by providing a fully managed environment for deploying web applications and services.
Scalability Options: Another important difference is the scalability options offered by Apollo and Heroku. Apollo allows users to scale their GraphQL server horizontally by adding more instances as needed, giving them flexibility in handling increased traffic and workload. Heroku, on the other hand, automatically handles scaling based on the application's needs, making it easier for users to manage resources without having to intervene manually.
Cost Structure: The cost structure differs between Apollo and Heroku. Apollo being open-source, has no direct cost associated with using the software itself, but users are responsible for the infrastructure and maintenance costs if self-hosted. In contrast, Heroku offers a pay-as-you-go model, where users only pay for the resources and services they use, making it a more convenient option for those who prefer a simple pricing structure.
Add-on Services: Heroku provides a wide range of add-on services that can be easily integrated into applications, such as databases, caching, logging, monitoring, and more. These add-ons help enhance the functionality and performance of applications deployed on Heroku. Apollo, being a server framework, does not offer similar add-on services but can be integrated with various third-party services to supplement its capabilities.
Community Support and Ecosystem: When it comes to community support and ecosystem, Apollo benefits from a large, active community contributing to its development and providing resources such as tutorials, libraries, and plugins. Heroku, being a popular PaaS platform, has a vast ecosystem of developers, partners, and integrations, making it easier for users to find solutions and resources to support their applications.
Integration Flexibility: Lastly, the integration flexibility differs between Apollo and Heroku. Apollo, being a self-hosted server, offers users more control and flexibility in integrating with other tools, services, and platforms as needed. Heroku, while providing seamless integration with its own ecosystem of add-ons, may have limitations when it comes to integrating with certain external services, requiring users to find workarounds or alternative solutions.
In Summary, the key differences between Apollo and Heroku lie in the deployment environment, scalability options, cost structure, add-on services, community support, and integration flexibility.
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 Apollo
- From the creators of Meteor12
- Great documentation8
- Open source3
- Real time if use subscription2
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 Apollo
- File upload is not supported1
- Increase in complexity of implementing (subscription)1
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