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.

Use Hasura Remote Joins to join data from your Postgres database with user data in Okta.

Easily write a wrapper GraphQL service which calls your REST API. Add this GraphQL service as a Remote Schema in Hasura for automatic schema-stitching.