Mutating Meetup with GraphQL
summary
Meetup shifts to GraphQL over three years and hits three concrete problems: a Lambda primary API that fan-outs into a secondary API causing 5x duplicated requests and site instability, then fixes by routing 25% of primary API traffic directly to the secondary API and targeting $29k monthly savings. Caching improvements use GraphQL Java data loaders with a Redis value cache, which cuts read operations and saves hundreds per day, plus client/CDN caching, GraphQL Hive for schema sharing, and GitHub Actions to flag GraphQL PRs.
AI-written summary · about
chapters (5)
- 0:00Introduction to GraphQL at Meetup
- 1:24Architecture challenges with GraphQL
- 7:51Solving the caching problem
- 14:42Overcoming the learning curve
- 20:22Q&A and closing remarks








