Need advice about which tool to choose?Ask the StackShare community!
Hasura vs Paz: What are the differences?
Developers describe Hasura as "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. On the other hand, Paz is detailed as "A Simple Docker PaaS Written in Node.js". A pluggable in-house service platform with a PaaS-like workflow, built on Docker, CoreOS, Etcd and Fleet.
Hasura and Paz 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, Paz provides the following key features:
- A web front-end to CoreOS' Fleet with a PaaS-like workflow
- Like a clustered/multi-host Dokku
- Beautiful web UI
Paz is an open source tool with 6 GitHub stars and 4 GitHub forks. Here's a link to Paz's open source repository on GitHub.
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 Paz
Sign up to add or upvote prosMake informed product decisions
Cons of Hasura
- Cumbersome validations3
