An API First Approach to Adopting a Distributed SQL Database
summary
Shows a working pipeline that puts Hasura Cloud in front of Postgres and a geo‑distributed Yugabyte cluster to serve a unified GraphQL API, with demoed live queries, the generated SQL, and a remote countries GraphQL schema joined to order rows. Explains caching, rate limiting, edge deployment, and async cross‑region replication so reads are fast while writes replicate slowly, and demonstrates the setup actually returns joined data from Yugabyte and the external API.
AI-written summary · about
chapters (15)
- 0:00API first distributed SQL
- 1:29Data access challenges
- 3:16GraphQL solves data access
- 4:18Hasura features
- 5:22E-commerce scaling needs
- 6:47Scalable e-commerce components
- 8:59YugabyteDB distributed SQL
- 11:08Dynamic data and caching
- 13:16Frontend API and database
- 14:42Automated infrastructure
- 15:04Demo: Astra Cloud & Yugabyte
- 16:35Database schema exploration
- 17:38GraphQL queries
- 21:38Remote schemas & relationships
- 25:56Resources & community
related talks
19mBuilding Planet Scale Cloud Native Apps with GraphQL & Distributed SQL
08mScalable GraphQL Applications Powered by Cloud-ready Distributed SQL Database
28mModernizing App Development: Planet-scale GraphQL & Distributed SQL
20mSuperpowers Developers: GraphQL + DistributedSQL
24mScalable and Resilient GraphQL Subscriptions with Distributed SQL Databases
31mA Migration Journey from Amazon DynamoDB to Yugabyte YSQL and Hasura
30mBuilding Cloud Native Applications on Distributed SQL Platform
47mAnatomy of a Distributed SQL Database - YugabyteDB
