Open Source, Graphs and GraphQL: The next frontier of modern applications
summary
Argues that databases are shipping GraphQL APIs so teams stop hand-coding resolvers and web servers, showing concrete options: Dgraph built-in GraphQL (distributed graph DB for feeds/recommendations), Hasura over Postgres (instant GraphQL layer and service stitching), Fauna (SaaS proprietary), MongoDB and Neo4j support. Recommends picking by data model, trust/operational comfort and whether business logic must run in the native query language; uses a 30k–50k user attendance app and large social feed as concrete examples.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:32Overview
- 3:54Architecture
- 4:47Advantages of out of the box GraphQL support for DBS
- 5:42Hasura (GraphQL on RelationalDB)
- 7:02Dgraph (GraphQL on GraphDB)
- 8:19FaunaDB (GraphQL on NoSQL DB)
- 9:38Make the right choice of DB, Don't directly jump into the GraphQL bandwagon!
- 15:09What if you want the best of all worlds?
- 15:53Solution: GraphQL as data access and aggregation layer
related talks
28mModernizing App Development: Planet-scale GraphQL & Distributed SQL
24mI’ve finally seen the light, the future is a graph
45mBuilding Scalable APIs: PostgreSQL Meets GraphQL
35mGraphQL in the Enterprise
27mExploring GraphQL
58mThe Future of GraphQL panel
32mModernize development and activate legacy data with GraphQL
51mAccelerating Application Development with GraphQL Data Mesh