With a supergraph, we could create a single source of truth for definitions of every entity in our data model . . . eliminating a huge amount of maintenance work associated with these disparate graphs. For us, it was worth it.
We have our vaccine finder [where] you punch in your location and select your store. Beforehand, you would select a location, and you wouldn’t know if a COVID-19 vaccine was available at a given store. You’d have to start over. Because we’re using GraphQL, we were able to drive new fields … with REST, way too much data [would’ve been surfaced] to the client.
Centralized monolithic api services are difficult to scale now that we have 1000+ engineers in many time zones. Federation makes it easier to run an automated, centralized API service, which is fantastic. But it really works well with Apollo’s schema management tools because that’s what makes the automation actually possible
Had contracts not existed, Wayfair would’ve invested 100s of person hours building out custom infrastructure to replicate what we get “built-in,” freeing up time to focus on Wayfair customer needs and developer experience.
We introduced a new subgraph in the federated graph [for backend compliance logic when Zillow was becoming a brokerage], and it was a complete success … 70 systems migrated without any advance, and we had the deadline, right on the dot.
How fast can you onboard [a new] employee and make them productive? Effectively GraphQL takes [away] that burden of talking to the right people, finding the right endpoints…That’s absolutely critical. How are you going to build innovative products if your engineers spend most of their time trying to find where the data is coming from?