Database Hub

Another new feature exclusive to the Hasura 2.0 release is support for multiple Postgres database types. In just a few clicks you can add an an extra database, existing or new, track the tables, enable relations, and unlock the power of GraphQL.

Performance and High availability are critical challenges in production. Although TimescaleDB solves performance problems, we still need to care about remaining parts. In this article, I suggest some high availability setup for single-node as well as explore multi-node replication solutions.

Multi-node is the most interesting feature of version TimescaleDB 2.0 that provides the ability to create a cluster of TimescaleDB instances to scale both reads and writes.

TimescaleDB 2.0 is a major version upgrade that has many improvements from version 1. It introduces new interesting features and capabilities, especially horizontal multi-node scaling. Because it is a PostgreSQL extension, it mostly works well with Hasura.

Aurora is the new kid in the block. It leverages AWS’s infrastructure to deliver a 1-click enterprise-grade database system. You’ll have in this post the ins-and-outs of Aurora, whether it works with Hasura (hint: it does), and how to set it up with Hasura Cloud.

As a recent joiner to the Hasura team, I find myself learning, and exploring, GraphQL through the lens of my prior experience. In this series, I am going to share my point-of-view on Evolutionary Database Design, GraphQL, and schema migrations.

This post shows how to optimize your GraphQL API using some of Postgres' most popular features. These will help with data validations, data representation and performance enhancement.

Hasura GraphQL Engine has implicit support for Postgres UUID type, which means that UUID values can be provided as strings.

Date/Time types are one of the basic types every database supports, and Postgres has robust support for a large set of date and time types…