Alternatives to graphql-yoga logo

Alternatives to graphql-yoga

Prisma, GraphQL, Apollo, Altair GraphQL, and GraphQL Voyager are the most popular alternatives and competitors to graphql-yoga.
52
114
+ 1
2

What is graphql-yoga and what are its top alternatives?

Easiest way to run a GraphQL server: Sensible defaults & includes everything you need with minimal setup.;Includes Subscriptions: Built-in support for GraphQL subscriptions using WebSockets.;Compatible: Works with all GraphQL clients (Apollo, Relay...) and fits seamless in your GraphQL workflow.
graphql-yoga is a tool in the GraphQL Tools category of a tech stack.
graphql-yoga is an open source tool with GitHub stars and GitHub forks. Here’s a link to graphql-yoga's open source repository on GitHub

Top Alternatives to graphql-yoga

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

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

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

  • Altair GraphQL

    Altair GraphQL

    A beautiful feature-rich GraphQL Client IDE for all platforms. Enables you interact with any GraphQL server you are authorized to access from any platform you are on. Much like Postman for GraphQL, you can easily test and optimize your Grap ...

  • GraphQL Voyager

    GraphQL Voyager

    Represent any GraphQL API as an interactive graph. It's time to finally see the graph behind GraphQL. ...

  • Serverless AppSync

    Serverless AppSync

    It allows you to easily and quickly deploy GraphQL APIs on AWS, and integrate them with AWS Lambda, DynamoDB & others. It supports all AWS AppSync features, while offering sane defaults that makes working with AppSync a lot easier without compromising on flexibility. ...

  • GraphQL Editor

    GraphQL Editor

    Visual GraphQL Editor is a visual backend editor that speed's up software development and improve's communication with non-tech people. It's a is a bridge between tech and non-tech users. Professionals can import their previously written code and visualize it on diagram while newbies can link visual blocks and editor will transform them into code. Our tool makes understanding GraphQL schema a lot easier. ...

  • GraphQL Nexus

    GraphQL Nexus

    It is a declarative, code-first and strongly typed GraphQL schema construction for TypeScript & JavaScript. ...

graphql-yoga alternatives & related posts

Prisma logo

Prisma

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

related Prisma posts

Divine Bawa
at PayHub Ghana Limited · | 16 upvotes · 305.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
Munkhtegsh Munkhbat
Software Engineer Consultant at LoanSnap · | 9 upvotes · 137K 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
GraphQL logo

GraphQL

23.1K
19K
293
A data query language and runtime
23.1K
19K
+ 1
293
PROS OF GRAPHQL
  • 70
    Schemas defined by the requests made by the user
  • 62
    Will replace RESTful interfaces
  • 59
    The future of API's
  • 47
    The future of databases
  • 12
    Self-documenting
  • 11
    Get many resources in a single request
  • 5
    Ask for what you need, get exactly that
  • 4
    Query Language
  • 3
    Type system
  • 3
    Evolve your API without versions
  • 3
    Fetch different resources in one request
  • 2
    Ease of client creation
  • 2
    Easy setup
  • 2
    GraphiQL
  • 1
    Good for apps that query at build time. (SSR/Gatsby)
  • 1
    Backed by Facebook
  • 1
    Easy to learn
  • 1
    "Open" document
  • 1
    Better versioning
  • 1
    Standard
  • 1
    1. Describe your data
  • 1
    Fast prototyping
CONS OF GRAPHQL
  • 3
    Hard to migrate from GraphQL to another technology
  • 3
    More code to type.
  • 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 · | 44 upvotes · 1.8M 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
Apollo logo

Apollo

1.9K
1.5K
18
GraphQL server for Express, Connect, Hapi, Koa and more
1.9K
1.5K
+ 1
18
PROS OF APOLLO
  • 12
    From the creators of Meteor
  • 3
    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 · | 44 upvotes · 1.8M 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
    Altair GraphQL logo

    Altair GraphQL

    20
    43
    6
    A beautiful feature-rich GraphQL Client for all platforms
    20
    43
    + 1
    6
    PROS OF ALTAIR GRAPHQL
    • 1
      Easy setup
    • 1
      Available in all platforms
    • 1
      Multiple windows
    • 1
      Well designed UI
    • 1
      Open source
    • 1
      Easy to use
    CONS OF ALTAIR GRAPHQL
      Be the first to leave a con

      related Altair GraphQL posts

      GraphQL Voyager logo

      GraphQL Voyager

      19
      47
      0
      GraphQL Voyager – Represent Any GraphQL API as an Interactive Graph
      19
      47
      + 1
      0
      PROS OF GRAPHQL VOYAGER
        Be the first to leave a pro
        CONS OF GRAPHQL VOYAGER
          Be the first to leave a con

          related GraphQL Voyager posts

          Serverless AppSync logo

          Serverless AppSync

          15
          35
          0
          Easily and quickly deploy GraphQL APIs on AWS
          15
          35
          + 1
          0
          PROS OF SERVERLESS APPSYNC
            Be the first to leave a pro
            CONS OF SERVERLESS APPSYNC
              Be the first to leave a con

              related Serverless AppSync posts

              GraphQL Editor logo

              GraphQL Editor

              14
              46
              17
              Online GraphQL IDE, visualize your GraphQL Schema
              14
              46
              + 1
              17
              PROS OF GRAPHQL EDITOR
              • 3
                Visual GraphQL Editor
              • 3
                Web based GraphiQL
              • 3
                Visualize your code on diagram
              • 3
                Generate queries for front end
              • 3
                Fake / mocked backend
              • 2
                Generate code from diagram
              CONS OF GRAPHQL EDITOR
                Be the first to leave a con

                related GraphQL Editor posts

                GraphQL Nexus logo

                GraphQL Nexus

                14
                14
                2
                Code-First, Type-Safe, GraphQL Schema Construction
                14
                14
                + 1
                2
                PROS OF GRAPHQL NEXUS
                • 1
                  Use with Apollo
                • 1
                  Code first
                CONS OF GRAPHQL NEXUS
                  Be the first to leave a con

                  related GraphQL Nexus posts