mercurius VS transferred-stepzen-schemas

GraphQL Gateway is primarily responsible for serving GraphQL queries to consumers. It takes a query from a client, breaks it into smaller sub-queries, and executes that plan by proxying calls to the appropriate downstream subgraphs. When we started our journey, there was only Apollo Federation in the arena, and we used it. Still, now you can look at other options (e.g. Mercurius, Conductor, Hot Chocolate, Wundergraph, Hasura Remote Schemas), compare benchmarks and decide what's important and preferable for your needs. The Gateway provides a unified API for consumers while giving backend engineers flexibility and service isolation.

If you're using Fastify with Mercurius as your GraphQL adapter, you may be looking for some advanced usages. In this article, we'll explore a real world example with Dynamic GQL queries with Mercurius.

Loader: it is a built-in DataLoader-Like solution that is quick to set up and use.

In this post I will show you how to implement NestJS😻 with GraphQL in code first mode, using Mercurius and the "platform" to Fastify.

What this does is to overwrite or augment the types exposed by the pointed module, and can be used (for example) when relying on autogenerated code. One interesting case of this is GraphQL to TypeScript code generation, and how this is integrated with the amazing Mercurius library (made by some of my colleagues at NearForm! 😜).

When moving away from Apollo Server, and you're looking for a replacement built with JavaScript or TypeScript, let me give you some options. If you want to keep building your GraphQL API schema first, you might want to consider Mercurius (which relies on Fastify) or GraphQL Yoga. If you're going to build your GraphQL API code or resolver first, have a look at TypeGraphQL or Nexus. Alternatively, there are great GraphQL-as-a-Service solutions such as StepZen in case you no longer want to build, maintain and host your own GraphQL API.

Let's start with data. We live in amazing times and it's really easy and cheap (or free) to get started with storing and working with data online. Take for example a PlanetScale MySQL-compatible database, Fastify Node.js Server, Prisma database mapper and a GraphQL connector like Mercurius and you have an entire backend stack. For this example we assume you already have a backend or you want to connect to a 3rd party database like the GitHub GraphQL API.

In this chapter, we assume a basic understanding of GraphQL and focus on how to work with the built-in @nestjs/graphql module. The GraphQLModule can be configured to use Apollo server (with the @nestjs/apollo driver) and Mercurius (with the @nestjs/mercurius). We provide official integrations for these proven GraphQL packages to provide a simple way to use GraphQL with Nest. You can also build your own dedicated driver (read more on that here).

Why would I want to use Apollo Client? So far in my career I have used some server graphql scaffolding (webonyx/graphql-php for PHP and mercurius for Node) and just used the fetch API (or whatever ajax API around XMLHttpRequest) against that server with the body being an object with

Only for people who are clueless. Apollo server is probably the worst node.js server to use for your graphql schema. It's terribly slow. You should look into https://mercurius.dev

Go to stepzen.com and click on the start for free button.

Either way, I'm not too familiar with RxDB but looking at the docs you can also use StepZen to create the GraphQL layer that you use for replication. With StepZen you can build and deploy a GraphQL API based on multiple datasources (including MSSQL) in minutes. That way you only have to worry about building the logic that pulls and push replicates data to and from GraphQL. How you structure the MSSQL database would become the most important part of this project, to ensure a smooth replication.

There are multiple ways to get a GraphQL API on top off a Postgres database. If you want to have a GraphQL abstraction layer that runs as a hosted service and needs almost no code, have a look at StepZen. You can build a GraphQL API for the Postgres database by following the docs here. StepZen introspects the database (using stepzen import postgresql) and let it create the schema for you based on all the tables and columns of your database. Including a set of queries to get started with.

If you’re looking for a managed service, have a look atStepZen. You can combine multiple GraphQL schemas into one cloud GraphQL API. Instead of writing a gateway yourself, you can use SDL to merge different schemas. Besides GraphQL APIs you can also “federate” other data sources like SQL or REST

There are many of them, including StepZen which is language/framework agnostic and let you create a GraphQL server with GraphQL SDL only - in a declarative way

I’ve seen more products letting you join/merge GraphQL schemas independent of schema stitching or federation. Have a look at GraphQL Mesh or StepZen.

You can save yourself the hassle of having to build a GraphQL server, resolvers and database connections with StepZen (https://stepzen.com). It’s a product that is based solely on GraphQL SDL and you set the database connections with directives. Also, you can use it to connect other APIs

There is one thing I can say for sure: I love the spirit of open source. I've had a wonderful time working with open source communities of different sizes (e.g. Seneca-CDOT, StepZen, Appwrite, and Zulip). Fortunately, all of them are fantastic and patient with beginners.

If the only thing you're trying to do is converting a REST API to GraphQL, you should have a look at https://stepzen.com/

StepZen filed an issue about writing a GraphQL schema to integrate SpaceX REST API into their React application. I found this as an excellent opportunity for me to learn GraphQL.