TimescaleDB 2.0 with Hasura Part 2 - Multi-Node
Blog post from Hasura
In this blog post, the author explores using TimescaleDB 2.0 alongside Hasura and discusses their experience with setting up a multi-node feature in TimescaleDB 2.0. The multi-node feature allows for creating a cluster of TimescaleDB instances to scale both reads and writes. The author shares the infrastructure setup, authentication mechanisms, and how to create distributed hypertables. They also discuss performance comparison between non-distributed and distributed hypertables, foreign key and relationship handling, continuous aggregate views, SQL functions, triggers, and caveats of using distributed hypertables. Lastly, they mention running with Hasura GraphQL Engine and the need for manual relationship definition due to foreign keys not working on a distributed hypertable.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.