Alternatives to graphql.js logo

Alternatives to graphql.js

GraphQL, Cube, Apollo, SQL, and Prisma are the most popular alternatives and competitors to graphql.js.
93
85
+ 1
0

What is graphql.js and what are its top alternatives?

Lightest GraphQL client with intelligent features. You can download graphql.js directly, or you can use Bower or NPM.
graphql.js is a tool in the Query Languages category of a tech stack.
graphql.js is an open source tool with 2.3K GitHub stars and 96 GitHub forks. Here’s a link to graphql.js's open source repository on GitHub

Top Alternatives to graphql.js

  • 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. ...

  • Cube
    Cube

    Cube: the universal semantic layer that makes it easy to connect BI silos, embed analytics, and power your data apps and AI with context. ...

  • 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. ...

  • SQL
    SQL

    SQL is designed for managing data held in a relational database management system (RDBMS), or for stream processing in a relational data stream management system (RDSMS). ...

  • 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. ...

  • Oracle PL/SQL
    Oracle PL/SQL

    It is a powerful, yet straightforward database programming language. It is easy to both write and read, and comes packed with lots of out-of-the-box optimizations and security features. ...

  • Oracle PL/SQL
    Oracle PL/SQL

    It is a powerful, yet straightforward database programming language. It is easy to both write and read, and comes packed with lots of out-of-the-box optimizations and security features. ...

  • JSON API
    JSON API

    It is most widely used data format for data interchange on the web. This data interchange can happen between two computers applications at different geographical locations or running within same hardware machine. ...

graphql.js alternatives & related posts

GraphQL logo

GraphQL

33.8K
27.1K
310
A data query language and runtime
33.8K
27.1K
+ 1
310
PROS OF GRAPHQL
  • 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
CONS OF GRAPHQL
  • 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

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 · | 46 upvotes · 3.2M 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
Cube logo

Cube

86
252
30
Bring context to your data apps
86
252
+ 1
30
PROS OF CUBE
  • 8
    API
  • 6
    Caching
  • 6
    Open Source
  • 6
    Visualization agnostic
  • 4
    Rollups orchestration
CONS OF CUBE
  • 1
    Incomplete documentation
  • 1
    Doesn't support filtering on left joins
  • 1
    Poor performance
  • 1
    No ability to update "cubes" in runtime
  • 1
    Cannot use as a lib - only HTTP

related Cube posts

Apollo logo

Apollo

2.7K
1.8K
25
GraphQL server for Express, Connect, Hapi, Koa and more
2.7K
1.8K
+ 1
25
PROS OF APOLLO
  • 12
    From the creators of Meteor
  • 8
    Great documentation
  • 3
    Open source
  • 2
    Real time if use subscription
CONS OF APOLLO
  • 1
    File upload is not supported
  • 1
    Increase in complexity of implementing (subscription)

related Apollo posts

Nick Rockwell
SVP, Engineering at Fastly · | 46 upvotes · 3.2M 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
SQL logo

SQL

7.7K
184
0
It is a domain-specific language used in programming
7.7K
184
+ 1
0
PROS OF SQL
    Be the first to leave a pro
    CONS OF SQL
      Be the first to leave a con

      related SQL posts

      Prisma logo

      Prisma

      1.2K
      923
      54
      Modern Database Access for TypeScript & Node.js
      1.2K
      923
      + 1
      54
      PROS OF PRISMA
      • 12
        Type-safe database access
      • 10
        Open Source
      • 8
        Auto-generated query builder
      • 6
        Supports multible database systems
      • 6
        Increases confidence during development
      • 4
        Built specifically for Postgres and TypeScript
      • 4
        Productive application development
      • 2
        Supports multible RDBMSs
      • 2
        Robust migrations system
      CONS OF PRISMA
      • 2
        Doesn't support downward/back migrations
      • 1
        Doesn't support JSONB
      • 1
        Do not support JSONB
      • 1
        Mutation of JSON is really confusing
      • 1
        Do not support JSONB

      related Prisma posts

      Divine Bawa
      at PayHub Ghana Limited · | 16 upvotes · 481.6K 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
      Collins Ogbuzuru
      Front-end dev at Evolve credit · | 11 upvotes · 24.3K views
      Shared insights
      on
      GraphQLGraphQLPrismaPrismaAWS LambdaAWS Lambda

      We are starting to build one shirt data logic, structure and as an online clothing store we believe good ux and ui is a goal to drive a lot of click through. The problem is, how do we fetch data and how do we abstract the gap between the Front-end devs and backend-devs as we are just two in the technical unit. We decided to go for GraphQL as our application-layer tool and Prisma for our database-layer abstracter.

      Reasons :

      GraphQL :

      1. GraphQL makes fetching of data less painful and organised.

      2. GraphQL gives you 100% assurance on data you getting back as opposed to the Rest design .

      3. GraphQL comes with a bunch of real-time functionality in form of. subscriptions and finally because we are using React (GraphQL is not React demanding, it's doesn't require a specific framework, language or tool, but it definitely makes react apps fly )

      Prisma :

      1. Writing revolvers can be fun, but imagine writing revolvers nested deep down, curry braces flying around. This is sure a welcome note to bugs and as a small team we need to focus more on what that matters more. Prisma generates this necessary CRUD resolves, mutations and subscription out of the box.

      2. We don't really have much budget at the moment so we are going to run our logic in a scalable cheap and cost effective cloud environment. Oh! It's AWS Lambda and deploying our schema to Lambda is our best bet to minimize cost and same time scale.

      We are still at development stage and I believe, working on this start up will increase my dev knowledge. Off for Lunch :)

      See more
      Oracle PL/SQL logo

      Oracle PL/SQL

      738
      574
      8
      It is a combination of SQL along with the procedural features of programming languages
      738
      574
      + 1
      8
      PROS OF ORACLE PL/SQL
      • 2
        Multiple ways to accomplish the same end
      • 2
        Powerful
      • 1
        Not mysql
      • 1
        Massive, continuous investment by Oracle Corp
      • 1
        Extensible to external langiages
      • 1
        Pl/sql
      CONS OF ORACLE PL/SQL
      • 2
        High commercial license cost

      related Oracle PL/SQL posts

      Oracle PL/SQL logo

      Oracle PL/SQL

      738
      574
      8
      It is a combination of SQL along with the procedural features of programming languages
      738
      574
      + 1
      8
      PROS OF ORACLE PL/SQL
      • 2
        Multiple ways to accomplish the same end
      • 2
        Powerful
      • 1
        Not mysql
      • 1
        Massive, continuous investment by Oracle Corp
      • 1
        Extensible to external langiages
      • 1
        Pl/sql
      CONS OF ORACLE PL/SQL
      • 2
        High commercial license cost

      related Oracle PL/SQL posts

      JSON API logo

      JSON API

      193
      197
      0
      One of many data formats that is often applied to REST
      193
      197
      + 1
      0
      PROS OF JSON API
        Be the first to leave a pro
        CONS OF JSON API
          Be the first to leave a con

          related JSON API posts