From Monolith to Microservices and Back
summary
The talk examines GraphQL as part of a broader trend from fragmented-data architectures and microservices toward more unified, centralized engineering organizations. It explains how large companies plan team organization around a single Graph approach and describes unique GraphQL technical constructs and tools that help achieve unification.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:06Monolith to microservices at Uber
- 13:50Microservice distributed issues
- 21:16Uber adopted GraphQL
- 28:20Building GraphQL schemas
- 36:04GraphQL centralization risks
- 45:25GraphQL vs Protobuf
- 54:02Adopting GraphQL in teams
- 1:07:27Q&A
related talks
51mWhy GraphQL is Perfect for Microservices
27mWhy GraphQL is Perfect For Microservices
36mDistributed Graphs and Microservices at Prom.ua
50mDistributed GraphQL APIs: Breaking Down Monoliths & Unlocking Agility for Dev Teams
37mGraphQL and Microservices or How we learned to be big and small at the same time
59mBuilding Distributed GraphQL APIs
24mI’ve finally seen the light, the future is a graph
46mMoving to GraphQL