Alternatives to Hasura logo

Alternatives to Hasura

Firebase, Heroku, PostGraphile, Prisma, and Apollo are the most popular alternatives and competitors to Hasura.
206
405
+ 1
104

What is Hasura and what are its top alternatives?

An open source GraphQL engine that deploys instant, realtime GraphQL APIs on any Postgres database.
Hasura is a tool in the Platform as a Service category of a tech stack.
Hasura is an open source tool with 20.8K GitHub stars and 1.8K GitHub forks. Here’s a link to Hasura's open source repository on GitHub

Top Alternatives to Hasura

  • Firebase

    Firebase

    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...

  • Heroku

    Heroku

    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling. ...

  • PostGraphile

    PostGraphile

    Execute one command (or mount one Node.js middleware) and get an instant high-performance GraphQL API for your PostgreSQL database ...

  • Prisma

    Prisma

    Prisma is an open-source database toolkit. It replaces traditional ORMs and makes database access easy with an auto-generated query builder for TypeScript & Node.js. ...

  • Apollo

    Apollo

    Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes. ...

  • GraphQL

    GraphQL

    GraphQL is a data query language and runtime designed and used at Facebook to request and deliver data to mobile and web apps since 2012. ...

  • Strapi

    Strapi

    It is an open source Node.js Headless CMS to easily build customisable APIs. It lets you manage your content and distribute it anywhere. It allows you to securely and privately serve your database of choice from your hosting and server of choice. ...

  • FaunaDB

    FaunaDB

    FaunaDB is a global serverless database that gives you ubiquitous, low latency access to app data, without sacrificing data correctness and scale. It eliminates layers of app code for manually handling data anomalies, security, and scale, creating a friendlier dev experience for you and better app experience for your users. ...

Hasura alternatives & related posts

Firebase logo

Firebase

22.7K
18.7K
1.9K
The Realtime App Platform
22.7K
18.7K
+ 1
1.9K
PROS OF FIREBASE
  • 357
    Realtime backend made easy
  • 261
    Fast and responsive
  • 233
    Easy setup
  • 206
    Real-time
  • 184
    JSON
  • 126
    Free
  • 120
    Backed by google
  • 80
    Angular adaptor
  • 62
    Reliable
  • 36
    Great customer support
  • 25
    Great documentation
  • 22
    Real-time synchronization
  • 19
    Mobile friendly
  • 17
    Rapid prototyping
  • 12
    Great security
  • 10
    Automatic scaling
  • 9
    Freakingly awesome
  • 8
    Super fast development
  • 8
    Chat
  • 8
    Angularfire is an amazing addition!
  • 6
    Awesome next-gen backend
  • 6
    Ios adaptor
  • 5
    Firebase hosting
  • 5
    Built in user auth/oauth
  • 4
    Very easy to use
  • 3
    Great
  • 3
    Speed of light
  • 3
    Brilliant for startups
  • 3
    It's made development super fast
  • 2
    Low battery consumption
  • 2
    The concurrent updates create a great experience
  • 2
    I can quickly create static web apps with no backend
  • 2
    Great all-round functionality
  • 1
    Easy Reactjs integration
  • 1
    Good Free Limits
  • 1
    .net
  • 1
    Faster workflow
  • 1
    Serverless
  • 1
    JS Offline and Sync suport
  • 1
    Easy to use
  • 1
    Large
  • 1
    Push notification
CONS OF FIREBASE
  • 26
    Can become expensive
  • 14
    No open source, you depend on external company
  • 14
    Scalability is not infinite
  • 9
    Not Flexible Enough
  • 5
    Cant filter queries
  • 3
    Very unstable server
  • 2
    Too many errors
  • 2
    No Relational Data

related Firebase posts

Tassanai Singprom

This is my stack in Application & Data

JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

My Utilities Tools

Google Analytics Postman Elasticsearch

My Devops Tools

Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

My Business Tools

Slack

See more

We are starting to work on a web-based platform aiming to connect artists (clients) and professional freelancers (service providers). In-app, timeline-based, real-time communication between users (& storing it), file transfers, and push notifications are essential core features. We are considering using Node.js, ExpressJS, React, MongoDB stack with Socket.IO & Apollo, or maybe using Real-Time Database and functionalities of Firebase.

See more
Heroku logo

Heroku

17.1K
12.9K
3.2K
Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
17.1K
12.9K
+ 1
3.2K
PROS OF HEROKU
  • 703
    Easy deployment
  • 460
    Free for side projects
  • 374
    Huge time-saver
  • 348
    Simple scaling
  • 261
    Low devops skills required
  • 189
    Easy setup
  • 174
    Add-ons for almost everything
  • 153
    Beginner friendly
  • 149
    Better for startups
  • 133
    Low learning curve
  • 47
    Postgres hosting
  • 41
    Easy to add collaborators
  • 30
    Faster development
  • 24
    Awesome documentation
  • 19
    Simple rollback
  • 18
    Focus on product, not deployment
  • 15
    Easy integration
  • 15
    Natural companion for rails development
  • 11
    Great customer support
  • 7
    GitHub integration
  • 6
    No-ops
  • 5
    Painless & well documented
  • 3
    Just works
  • 3
    Free
  • 2
    PostgreSQL forking and following
  • 2
    I love that they make it free to launch a side project
  • 2
    Great UI
  • 2
    MySQL extension
CONS OF HEROKU
  • 22
    Super expensive
  • 6
    No usable MySQL option
  • 6
    Not a whole lot of flexibility
  • 5
    Storage
  • 4
    Low performance on free tier

related Heroku posts

Russel Werner
Lead Engineer at StackShare · | 29 upvotes · 1.3M views

StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

#StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 2.2M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
PostGraphile logo

PostGraphile

66
147
33
Instant GraphQL API for your PostgreSQL database; use standalone or as a Node.js middleware; MIT-licensed OSS
66
147
+ 1
33
PROS OF POSTGRAPHILE
  • 6
    Postgres based authentication
  • 4
    Simple to set up and scale
  • 4
    Great developer support
  • 4
    Bye bye Resolvers
  • 4
    Lightning fast
  • 4
    Database first with no braking changes
  • 2
    Instant production ready GraphQL
  • 2
    Back to database first
  • 1
    9 Automatically generates your GraphQL schema
  • 1
    Easy setup of relationships and permissions
  • 1
    Works with new and existing databases
CONS OF POSTGRAPHILE
    Be the first to leave a con

    related PostGraphile posts

    Obsaa Abdalhalim
    CEO, Founder at Kafali PAY inc. · | 1 upvote · 76.8K views

    React Native NativeBase redux-saga Apollo GraphQL Node.js PostGraphile PostgreSQL PubNub . @PLAID Dwolla.js . Zube GitHub Yarn npm AWS Elastic Beanstalk

    See more
    Prisma logo

    Prisma

    272
    438
    31
    Modern Database Access for TypeScript & Node.js
    272
    438
    + 1
    31
    PROS OF PRISMA
    • 6
      Open Source
    • 5
      Auto-generated query builder
    • 5
      Type-safe database access
    • 4
      Increases confidence during development
    • 4
      Productive application development
    • 4
      Built specifically for Postgres and TypeScript
    • 3
      Supports multible database systems
    • 0
      Supports multible RDBMSs
    CONS OF PRISMA
    • 1
      Doesn't support downward/back migrations

    related Prisma posts

    Divine Bawa
    at PayHub Ghana Limited · | 15 upvotes · 271K views

    I just finished a web app meant for a business that offers training programs for certain professional courses. I chose this stack to test out my skills in graphql and react. I used Node.js , GraphQL , MySQL for the #Backend utilizing Prisma as a database interface for MySQL to provide CRUD APIs and graphql-yoga as a server. For the #frontend I chose React, styled-components for styling, Next.js for routing and SSR and Apollo for data management. I really liked the outcome and I will definitely use this stack in future projects.

    See more
    Munkhtegsh Munkhbat
    Software Engineer Consultant at LoanSnap · | 9 upvotes · 102.7K views

    In my last side project, I built a web posting application that has similar features as Facebook and hosted on Heroku. The user can register an account, create posts, upload images and share with others. I took an advantage of graphql-subscriptions to handle realtime notifications in the comments section. Currently, I'm at the last stage of styling and building layouts.

    For the #Backend I used graphql-yoga, Prisma, GraphQL with PostgreSQL database. For the #FrontEnd: React, styled-components with Apollo. The app is hosted on Heroku.

    See more
    Apollo logo

    Apollo

    1.7K
    1.3K
    16
    GraphQL server for Express, Connect, Hapi, Koa and more
    1.7K
    1.3K
    + 1
    16
    PROS OF APOLLO
    • 11
      From the creators of Meteor
    • 2
      Great documentation
    • 2
      Real time if use subscription
    • 1
      Open source
    CONS OF APOLLO
      Be the first to leave a con

      related Apollo posts

      Nick Rockwell
      SVP, Engineering at Fastly · | 42 upvotes · 1.4M views

      When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

      So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

      React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

      Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

      See more
      Adam Neary

      At Airbnb we use GraphQL Unions for a "Backend-Driven UI." We have built a system where a very dynamic page is constructed based on a query that will return an array of some set of possible “sections.” These sections are responsive and define the UI completely.

      The central file that manages this would be a generated file. Since the list of possible sections is quite large (~50 sections today for Search), it also presumes we have a sane mechanism for lazy-loading components with server rendering, which is a topic for another post. Suffice it to say, we do not need to package all possible sections in a massive bundle to account for everything up front.

      Each section component defines its own query fragment, colocated with the section’s component code. This is the general idea of Backend-Driven UI at Airbnb. It’s used in a number of places, including Search, Trip Planner, Host tools, and various landing pages. We use this as our starting point, and then in the demo show how to (1) make and update to an existing section, and (2) add a new section.

      While building your product, you want to be able to explore your schema, discovering field names and testing out potential queries on live development data. We achieve that today with GraphQL Playground, the work of our friends at #Prisma. The tools come standard with Apollo Server.

      #BackendDrivenUI

      See more
      GraphQL logo

      GraphQL

      17.4K
      13.7K
      288
      A data query language and runtime
      17.4K
      13.7K
      + 1
      288
      PROS OF GRAPHQL
      • 69
        Schemas defined by the requests made by the user
      • 62
        Will replace RESTful interfaces
      • 58
        The future of API's
      • 47
        The future of databases
      • 11
        Self-documenting
      • 10
        Get many resources in a single request
      • 5
        Ask for what you need, get exactly that
      • 4
        Query Language
      • 3
        Evolve your API without versions
      • 3
        Type system
      • 2
        Easy setup
      • 2
        Fetch different resources in one request
      • 2
        Ease of client creation
      • 2
        GraphiQL
      • 1
        Standard
      • 1
        Good for apps that query at build time. (SSR/Gatsby)
      • 1
        "Open" document
      • 1
        Easy to learn
      • 1
        Backed by Facebook
      • 1
        1. Describe your data
      • 1
        Fast prototyping
      • 1
        Better versioning
      CONS OF GRAPHQL
      • 3
        More code to type.
      • 2
        Hard to migrate from GraphQL to another technology
      • 1
        Works just like any other API at runtime
      • 1
        Takes longer to build compared to schemaless.

      related GraphQL posts

      Shared insights
      on
      Node.jsNode.jsGraphQLGraphQLMongoDBMongoDB

      I just finished the very first version of my new hobby project: #MovieGeeks. It is a minimalist online movie catalog for you to save the movies you want to see and for rating the movies you already saw. This is just the beginning as I am planning to add more features on the lines of sharing and discovery

      For the #BackEnd I decided to use Node.js , GraphQL and MongoDB:

      1. Node.js has a huge community so it will always be a safe choice in terms of libraries and finding solutions to problems you may have

      2. GraphQL because I needed to improve my skills with it and because I was never comfortable with the usual REST approach. I believe GraphQL is a better option as it feels more natural to write apis, it improves the development velocity, by definition it fixes the over-fetching and under-fetching problem that is so common on REST apis, and on top of that, the community is getting bigger and bigger.

      3. MongoDB was my choice for the database as I already have a lot of experience working on it and because, despite of some bad reputation it has acquired in the last months, I still believe it is a powerful database for at least a very long list of use cases such as the one I needed for my website

      See more
      Nick Rockwell
      SVP, Engineering at Fastly · | 42 upvotes · 1.4M views

      When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

      So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

      React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

      Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

      See more
      Strapi logo

      Strapi

      306
      699
      186
      An open-source Headless-CMS
      306
      699
      + 1
      186
      PROS OF STRAPI
      • 40
        Free
      • 29
        Open source
      • 21
        Rapid development
      • 19
        API-based cms
      • 17
        Self-hostable
      • 16
        Real-time
      • 13
        Easy setup
      • 10
        Headless
      • 9
        JSON
      • 9
        Large community
      • 3
        Social Auth
      CONS OF STRAPI
      • 7
        Internationalisation
      • 7
        Can be limiting
      • 5
        A bit buggy
      • 3
        DB Migrations not seemless

      related Strapi posts

      FaunaDB logo

      FaunaDB

      43
      62
      7
      The database built for serverless, featuring native GraphQL.
      43
      62
      + 1
      7
      PROS OF FAUNADB
      • 1
        Also supports SQL, CQL
      • 1
        Removes server provisioning or maintenance
      • 1
        No more n+1 problems (+ GraphQL)
      • 1
        Works well with GraphQL
      • 1
        Low latency global CDN's
      • 1
        Generous free tier
      • 1
        100% ACID
      CONS OF FAUNADB
      • 1
        Must keep app secrets encrypted
      • 1
        Log stack traces to avoid improper exception handling
      • 1
        Susceptible to DDoS (& others) use timeouts throttling

      related FaunaDB posts

      I would like to assess search functionality along with some analytical use cases like aggregating, faceting etc.,. I would like to know which is the best database to go with among Elasticsearch, MongoDB and FaunaDB.

      See more