Now teams can start with a VIN, decode it to get the vehicle ID, connect to valuations, and get everything they need in one query. We can compose these proven services in ways we never could before. And considering the process would have typically required months or even a year of work from multiple engineers, Apollo Connectors saved us millions. This was monumental.
Mark Meiller
Principal Engineer of Data Services at Cox Automotive
Apollo GraphOS is a key platform for the development team to work softly with
GraphQL. It provides a bunch of tools and APIs that allow us to establish a secure
development pipeline to compose and deliver new pieces to our supergraph.
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.
In some cases, teams are almost doubling the speed at which they are releasing features and we are not even close to finishing our modernization journey ... We're just getting faster and faster.
Apollo Router and Federation are incredibly well-documented systems that are a joy to use. Whenever someone on the team wants to make an improvement to the schema, we can simply refer them to the documentation. It becomes the first point of reference for anyone on the team, and there are so many features available. It’s brilliant.
It’s been over a year since we’ve had any breaking changes. Prior to adopting Apollo, we had breaking changes as frequently as every month. We once took down our mobile home page for six hours.
With Apollo GraphOS and federated subscriptions, JUCR delivers seamless live updates to thousands of EV charging sessions across Europe, keeping our customers up-to-date in real time during their charging experience
If you’re a company that’s expecting to build more and scale more, but you still want the confidence that what you’re building is standardized and not slowing you down, then I would recommend you consider an Apollo GraphQL approach.
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.
In all our previous stacks, each individual UI built their own APIs. iOS had one API, Android had another API, TV has a different API, etc. we just couldn’t scale with the business anymore. Unifying those in a single federated GraphQL API was super valuable, and something we couldn't do before.
Bruce Wang
Director of Product Platform Systems team, Netflix
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
Really, it’s speed and agility that’s going to take you to the next level, rather than the technology itself. That’s why I get so excited about the supergraph.
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 have developed a very close working relationship with Apollo, which is critical to ensuring that we can help our customers through both good times and difficult times.
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?