Need advice about which tool to choose?Ask the StackShare community!
Hasura vs Stackato: What are the differences?
What is Hasura? An open source GraphQL engine that deploys instant, realtime GraphQL APIs on any Postgres database. An open source GraphQL engine that deploys instant, realtime GraphQL APIs on any Postgres database.
What is Stackato? Enterprise ready private PaaS based on the Cloud Foundry open-source project and Docker. Stackato runs on top of your cloud infrastructure, and is the middleware from which your applications are launched. Developers simply upload their application source files to Stackato via IDE or command-line. Stackato automatically configures the required language runtimes, web frameworks, and data and messaging services.
Hasura and Stackato belong to "Platform as a Service" category of the tech stack.
Some of the features offered by Hasura are:
- Stack-agnostic
- Cloud-agnostic
- Git push to deploy
On the other hand, Stackato provides the following key features:
- Web console
- Activity timeline
- Multi-tenancy
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 Stackato
- Compliance - Owning the data helps with SOX, etc2
Sign up to add or upvote prosMake informed product decisions
Cons of Hasura
- Cumbersome validations3
