We’ll be building a GraphQL API backend with Hot Chocolate GraphQL and integrating it to Hasura via Remote Schema.

Open source implementations of the GraphQL spec are now available in most popular languages. In this post we will look at the most popular libraries for each language for anyone to get started with and ways to add production ready features like Authorization, Rate Limiting, Caching etc.

Remote schema joins provides the most simple approach to federated data. Provide a GraphQL endpoint, identify the connection parameters, and give the new field a name and you have two disparate data sources from different systems resolving under a single API.

In this walkthrough, we're going to go through creating a simple GraphQL authentication service using Django Graphene, meshing it into your Hasura service, and creating a few sample requests.

In this post, we will look at building a GraphQL API backend with Deno and create a unified GraphQL layer with Hasura and Deno to solve custom business logic requirements of the app.

Announcing Hasura 1.4.0.apha1. 1.4 is not a ‘small release’. In fact, the list of features is substantive and incredibly exciting. If you’ve attended a recent Hasura Community Call you may well have seen recent demos of these capabilities.

In this example, we will look at the ability to add an API source that GraphQL Mesh creates as a Remote Schema in Hasura. Going one step further we will try to establish relationships between Hasura's GraphQL API and APIs sourced via GraphQL Mesh.

Hasura Remote Joins lets developers treat data across different data sources as if it were one database without having to modify or affect the existing data source.

Have you been wondering about best practices with Hasura? Here’s a quick rundown of some of our recent FAQ’s.