Need advice about which tool to choose?Ask the StackShare community!

GraphQL

33.8K
27.1K
+ 1
310
JSONata

13
10
+ 1
0
Add tool

JSONata vs GraphQL: What are the differences?

Developers describe JSONata as "JSON query and transformation language". It is a declarative open-source query and transformation language for JSON data. On the other hand, GraphQL is detailed as "A data query language and runtime". 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.

JSONata and GraphQL can be categorized as "Query Languages" tools.

Some of the features offered by JSONata are:

  • Lightweight query and transformation language for JSON data
  • Inspired by the location path semantics of XPath 3.1
  • Sophisticated query expressions with minimal syntax

On the other hand, GraphQL provides the following key features:

  • Hierarchical
  • Product-centric
  • Client-specified queries

GraphQL is an open source tool with 13K GitHub stars and 995 GitHub forks. Here's a link to GraphQL's open source repository on GitHub.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of GraphQL
Pros of JSONata
  • 75
    Schemas defined by the requests made by the user
  • 63
    Will replace RESTful interfaces
  • 62
    The future of API's
  • 49
    The future of databases
  • 13
    Self-documenting
  • 12
    Get many resources in a single request
  • 6
    Query Language
  • 6
    Ask for what you need, get exactly that
  • 3
    Fetch different resources in one request
  • 3
    Type system
  • 3
    Evolve your API without versions
  • 2
    Ease of client creation
  • 2
    GraphiQL
  • 2
    Easy setup
  • 1
    "Open" document
  • 1
    Fast prototyping
  • 1
    Supports subscription
  • 1
    Standard
  • 1
    Good for apps that query at build time. (SSR/Gatsby)
  • 1
    1. Describe your data
  • 1
    Better versioning
  • 1
    Backed by Facebook
  • 1
    Easy to learn
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Cons of GraphQL
    Cons of JSONata
    • 4
      Hard to migrate from GraphQL to another technology
    • 4
      More code to type.
    • 2
      Takes longer to build compared to schemaless.
    • 1
      No support for caching
    • 1
      All the pros sound like NFT pitches
    • 1
      No support for streaming
    • 1
      Works just like any other API at runtime
    • 1
      N+1 fetch problem
    • 1
      No built in security
      Be the first to leave a con

      Sign up to add or upvote consMake informed product decisions

      - No public GitHub repository available -

      What is 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.

      What is JSONata?

      It is a declarative open-source query and transformation language for JSON data.

      Need advice about which tool to choose?Ask the StackShare community!

      What companies use GraphQL?
      What companies use JSONata?
      See which teams inside your own company are using GraphQL or JSONata.
      Sign up for StackShare EnterpriseLearn More

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with GraphQL?
      What tools integrate with JSONata?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      Blog Posts

      GitHubDockerReact+17
      40
      36168
      GitHubPythonNode.js+47
      54
      72281
      What are some alternatives to GraphQL and JSONata?
      gRPC
      gRPC is a modern open source high performance RPC framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking...
      Falcor
      Falcor lets you represent all your remote data sources as a single domain model via a virtual JSON graph. You code the same way no matter where the data is, whether in memory on the client or over the network on the server.
      React
      Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.
      graphql.js
      Lightest GraphQL client with intelligent features. You can download graphql.js directly, or you can use Bower or NPM.
      MongoDB
      MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.
      See all alternatives