Realtor.com's Technological & Cultural Transformation with GraphQL
summary
Realtor.com migrates from hundreds of inconsistent REST endpoints to an Apollo GraphQL supergraph with Federation, building automated subgraph templates, a GraphQL guild and Graph Guardians governance to stop the core-graph monolith and speed teams back up. Early adopters in security and growth validate a single secured entrypoint and shared, product-shaped fields (price formatting and price-drop UI logic) so clients stop reimplementing business rules. The tech works but only after heavy stakeholder storytelling, cross-functional buy‑in and continual comms to overcome cultural resistance.
AI-written summary · about
chapters (12)
- 0:00Introduction and context
- 1:46Meet the speakers
- 3:30Realtor.com's tech strategy
- 6:03Why adopt GraphQL
- 10:20Building consensus for change
- 12:26Overcoming resistance
- 16:19The Supergraph decision
- 18:05Creating momentum
- 20:09GraphQL governance
- 22:57APIs as product experience
- 28:12Cultural shift challenges
- 32:24Path forward and conclusion
related talks
26mKeynote: Apollo's Journey with GraphQL: Transforming Enterprise APIs for the Future
23mBuilding the Graph at Booking.com
22mInverse Conway Maneuver, with GraphQL
35mA Wild GraphQL Rollercoaster Ride a Federated GraphQL Adoption Story
23mBuilding the Graph at Booking.com
30mDeep Learnings Migrating legacy services to Federated GraphQL
38mGraphQL Federation in the Wild
25mGraphQL, the Domain Way