Delivering Exceptional Infrastructure as Code through REST and GraphQL
summary
Platform starts with REST, adds GraphQL for SaaS then on‑prem, and scales to billions of requests per day. REST proves roughly twice as slow under load so GraphQL reduces multiple round trips to single queries and cuts GUI load time; schema rollout happens surface by surface. Engineering centralizes API ownership into a single engineering team, fixes broken versioning, adds SDKs driven by customer demand, and builds server-side helpers like eventsFromHours.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:34Welcome
- 1:20Cloud Data Management
- 9:27API Hygiene
- 15:03GraphQL
- 17:31Challenges
- 18:37SDK and tooling
- 19:12Improvements
- 20:11Outro
related talks
18mIs GraphQL the end of RESTstyle APIs
19mGraphQL: Accelerating Digital Transformation Through Modern APIs.
39mWhy REST when you can GraphQL
23mAugmenting a Legacy REST API with GraphQL
27mA no nonsense GraphQL and REST comparison
12mUsing public APIs
55mGraphQL - APIs the New Way
41mDoes Your API Need a REST? Check Out GraphQL.