Custom Business Logic

Hasura gives you CRUD + realtime GraphQL APIs with authorization & access control. However, there are cases where you would want to add custom/business logic in your app. For example, in the todo app that we are building, before inserting todos into the public feed we want to validate the text for profanity.

Custom business logic can be handled in a few flexible ways in Hasura:

Actions (Recommended)

Actions are a way to extend Hasura’s schema with custom business logic using custom queries and mutations. Actions can be added to Hasura to handle various use cases such as data validation, data enrichment from external sources and any other complex business logic.

Actions architecture

Actions can be either a Query or a Mutation.

  • Query Action - If you are querying some data from an external API or doing some validations / transformations before sending back the data, you can use a Query Action.
  • Mutation Action - If you want to perform data validations or do some custom logic before manipulating the database, you can use a Mutation Action.

Remote Schemas

Hasura has the ability to merge remote GraphQL schemas and provide a unified GraphQL API. Think of it like automated schema stitching. This way, we can write custom GraphQL resolvers and add it as a remote schema.

Remote schema architecture

If you are choosing between Actions and Remote Schemas, here's something to keep in mind:

  • Use Remote Schemas if you have a GraphQL server or if you're comfortable building one yourself.
  • Use Actions if you need to call a REST API

Event Triggers

Hasura can be used to create event triggers on tables in the Postgres database. Event triggers reliably capture events on specified tables and invoke webhooks to carry out any custom logic. After a mutation operation, triggers can call a webhook asynchronously.

Use case for the todo app

In the todo app backend that you have built, there are certain custom functionalities you may want to add:

If you want to fetch profile information from Auth0, you need to make an API call to Auth0 with the token. Auth0 only exposes a REST API and not GraphQL. This API has to be exposed to the GraphQL client.

We will add an Action in Hasura to extend the API. We will also see how the same thing can be done with a custom GraphQL server added as a Remote Schema.

  • Get notified via email whenever a new user registers in your app. This is an asynchronous operation that can be invoked via Event trigger webhook.

We will see how these 2 use-cases can be handled in Hasura.