Software Alternatives, Accelerators & Startups

graphql.js VS Hasura

Compare graphql.js VS Hasura and see what are their differences

Note: These products don't have any matching categories. If you think this is a mistake, please edit the details of one of the products and suggest appropriate categories.

graphql.js logo graphql.js

A reference implementation of GraphQL for JavaScript - graphql/graphql-js

Hasura logo Hasura

Hasura is an open platform to build scalable app backends, offering a built-in database, search, user-management and more.
  • graphql.js Landing page
    Landing page //
    2023-08-27
  • Hasura Landing page
    Landing page //
    2023-10-21

graphql.js features and specs

  • Strongly Typed
    GraphQL.js allows for strongly typed schemas, making it easier to perform validation and introspection on your data, ensuring that queries conform to a specific structure before execution.
  • Efficient Data Fetching
    GraphQL.js enables clients to request exactly the data they need which can reduce over-fetching and under-fetching compared to REST APIs.
  • Rich Developer Tooling
    The introspection capabilities in GraphQL.js allow for rich tooling, enabling better development workflows including robust IDE support and tools like GraphiQL.
  • Evolving APIs
    GraphQL.js facilitates evolving APIs without the need for versioning, providing backward compatibility by introducing non-breaking changes.
  • Community Support
    GraphQL.js has a large and active community, providing numerous resources, plugins, and tools that support smooth development processes.

Possible disadvantages of graphql.js

  • Complexity
    Implementing GraphQL.js can add complexity to projects as developers may need to learn new concepts such as schemas, resolvers, and query languages.
  • Overhead
    The flexibility of GraphQL.js can introduce performance overhead, as the server may need to parse and execute more complex and dynamic queries.
  • Cache Invalidation
    Caching strategies for GraphQL.js can be more complex compared to REST, as caching needs to account for the structure and specifics of the queries requested.
  • Over-fetching Risks
    While GraphQL.js mitigates data over-fetching, it can also expose sensitive data if developers are not meticulous in specifying and controlling the schema and access permissions.
  • Debugging Complexity
    Debugging runtime errors in GraphQL.js can sometimes be more difficult, especially with deeply nested queries and complex resolvers.

Hasura features and specs

  • Real-Time Data
    Hasura provides built-in support for GraphQL subscriptions, allowing you to easily implement real-time data updates in your applications.
  • Auto-Generated APIs
    With Hasura, you can instantly generate a fully-functional, scalable GraphQL API from your existing databases without writing any code.
  • Authorization and Authentication
    Hasura provides granular authorization controls and integrates well with various authentication services, helping to secure your data access.
  • Microservices & Event Triggers
    Hasura allows you to create event-driven architectures by allowing you to trigger webhooks based on specified database events.
  • Scalability
    Designed for performance, Hasura can handle large-scale applications by optimizing database queries and offering load-balancing capabilities.
  • Multi-Data Source Support
    Hasura can connect to multiple data sources and databases, making it a versatile choice for complex architectures.
  • Developer Productivity
    The tool significantly reduces the time required for backend development, allowing developers to focus on building frontend features and improving user experience.
  • Community and Support
    Hasura has a growing community and offers comprehensive documentation, which can be invaluable for troubleshooting and getting the most out of the platform.

Possible disadvantages of Hasura

  • Complex Initial Setup
    Although Hasura simplifies many tasks, setting it up initially can be complex and may require a good understanding of both GraphQL and your underlying database.
  • Vendor Lock-In Concerns
    Depending heavily on Hasura can create vendor lock-in situations, making it difficult to switch technologies later without significant redevelopment effort.
  • Learning Curve
    Developers unfamiliar with GraphQL, event-driven architectures, or advanced database concepts may face a steep learning curve when adopting Hasura.
  • Limited Customization
    Some advanced use cases may require lower-level customizations not easily achievable through Hasura’s auto-generated APIs.
  • Performance Overhead
    Although optimized for performance, the additional layer Hasura introduces can still introduce latency, especially in highly complex queries.
  • Debugging Complexity
    Diagnosing issues can sometimes be complicated due to the number of components involved, including the database, Hasura, and the generated APIs.
  • Cost
    While Hasura offers a free tier, advanced features and enterprise-level support come at a cost, which can add up as your project scales.

graphql.js videos

No graphql.js videos yet. You could help us improve this page by suggesting one.

Add video

Hasura videos

Scott Tries Hasura - A Realtime GraphQL API Builder

More videos:

  • Review - Evaluating Hasura
  • Review - The founder of Hasura teaching me about Hasura - FUN!

Category Popularity

0-100% (relative to graphql.js and Hasura)
Project Management
100 100%
0% 0
GraphQL
0 0%
100% 100
Development
100 100%
0% 0
Developer Tools
0 0%
100% 100

User comments

Share your experience with using graphql.js and Hasura. For example, how are they different and which one is better?
Log in or Post with

Social recommendations and mentions

Based on our record, Hasura seems to be a lot more popular than graphql.js. While we know about 122 links to Hasura, we've tracked only 8 mentions of graphql.js. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

graphql.js mentions (8)

  • Diving into Open-Source Development
    To begin, I'm going to start with GraphQL. This repo is a JS-specific implementation for GraphQL, for which projects written in JS/TS can utilize to build an API for their web app. The reason why I chose this project is because I've always been intrigued by how GraphQl challenges the standard way of building an API, a.k.a REST APIs. I have very little knowledge about this project since I've never used it before at... - Source: dev.to / over 1 year ago
  • How to define schema once and have server code and client code typed? [Typescript]
    When I asked this in StackOverflow over a year ago I reached the solution of using graphql + graphql-zeus. Source: almost 2 years ago
  • Apollo federated graph is not presenting its schema to graphiql with fields sorted lexicographically
    GraphiQL (and many other tools) relies on introspection query which AFAIK is not guaranteed to have any specific order (and many libs don't support it). Apollo Server is built on top of graphql-js and it relies on it for this functionality. Source: over 2 years ago
  • How (Not) To Build Your Own GraphQL Server
    Defining your schema and the resolvers simultaneously led to some issues for developers, as it was hard to decouple the schema from the (business) logic in your resolvers. The SDL-first approach introduced this separation of concerns by defining the complete schema before connecting them to the resolvers and making this schema executable. A version of the SDL-first approach was introduced together with GraphQL... - Source: dev.to / over 3 years ago
  • three ways to deploy a serverless graphQL API
    Graphql-yoga is built on other packages that provide functionality required for building a GraphQL server such as web server frameworks like express and apollo-server, GraphQL subscriptions with graphql-subscriptions and subscriptions-transport-ws, GraphQL engine & schema helpers including graphql.js and graphql-tools, and an interactive GraphQL IDE with graphql-playground. - Source: dev.to / over 3 years ago
View more

Hasura mentions (122)

  • Supabase Alternatives 🔄 in 2025 😼
    Hasura is a neck-to-neck competitor to Supabase as a BaaS, but with a crucial difference: its GraphQL-first approach. Unlike Supabase, Hasura doesn't bundle database services, allowing it to work with virtually any database including Supabase's own Postgres, Neon, and others. - Source: dev.to / 2 months ago
  • Automatically Generate REST and GraphQL APIs From Your Database
    Hasura and PostGraphile lead the PostgreSQL GraphQL landscape. Hasura provides real-time subscriptions and a powerful permissions system, while PostGraphile offers deep PostgreSQL integration and excellent performance for complex queries. - Source: dev.to / 5 months ago
  • The Myth of GraphQL
    Here is an example data schema we get for a query using Hasura and GraphQL-Codegen. - Source: dev.to / 7 months ago
  • Hasura CLI on NixOS: A Working Solution
    Hasura is a great tool. I was worried about a few things such as huge RAM consumption, excessive focus on new features and functions despite many outstanding issues, long time rewrite of the server in Rust, etc... - Source: dev.to / 10 months ago
  • Haskell Certification Program
    Hasura has commercial use: https://hasura.io/. - Source: Hacker News / 11 months ago
View more

What are some alternatives?

When comparing graphql.js and Hasura, you can also consider the following products

JsonAPI - Application and Data, Languages & Frameworks, and Query Languages

Supabase - An open source Firebase alternative

Apollo - Apollo is a full project management and contact tracking application.

How to GraphQL - Open-source tutorial website to learn GraphQL development

Graphene - Query Languages

GraphQl Editor - Editor for GraphQL that lets you draw GraphQL schemas using visual nodes