Celebrating 250M Downloads and 2.0 in stable, HasuraCon'21 starts off with major announcements such as Cross Database Joins with GraphQL, schema sharing and better git-bases CI/CD workflows on Hasura Cloud.

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.

We will be building GraphQL APIs in Laravel using PostgreSQL as a database and Hasura for query and Remote Joining multiple tables in the database.

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.

We will look at how to use Gatsby Source Plugins as a Remote Schema source and federate data using Hasura Remote Joins for a unified data model and GraphQL API

After few weeks of being in beta, Hasura v1.3.0 is now released. This is one of the biggest Hasura releases till date, with 3 huge features being launched - Remote Joins, Relay support and Scheduled Triggers.

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.

Hasura is a headless GraphQL API platform which can be used by writers and developers with the right tooling to build content heavy apps for multiple platforms.