Volvo Cars is on a journey to have at least 50% of their sales online by 2025. To achieve this goal, the organization needed to create a consistent and intuitive user experience across its website. However, Volvo’s system landscape was so complex that it was taking developers over a week to figure out how to combine APIs into new experiences. To complicate matters further, there were site delays that caused abandonment and shoppers weren’t seeing accurate pricing information or graphics.
In his Champions Corner webinar, Stephan Lonntorp, Senior Engineering Manager at Volvo Cars, shares how implementing a supergraph with Apollo GraphOS is helping Volvo address these challenges to build a better digital car buying experience that increases online sales.
Struggling to scale with a GraphQL monolith
When Stephan started on this journey, he began with a GraphQL monolith. He replaced different API gateways with a schema that brought context to the data, abstracting away the complexity of how it’s pieced together. But, as more teams started using the graph, the monolith strained his team. Changes took a long time to implement and experiences broke daily without warning. (A typical incident being that not every car would show on the website.)
The central graph team was always called to troubleshoot, which meant they couldn’t work on anything else – even though the incidents were due to underlying systems breaking.
Unlocking agility with the supergraph
After realizing the monolithic graph wouldn’t scale, he adopted a supergraph, powered by Apollo GraphOS, to allow each team to own and manage their data end to end. A new layer in the tech stack, the supergraph unifies all cloud data and services into a single connected map that developers can query with GraphQL.
GraphOS also delivers visibility into what APIs are being used, so his teams can safely evolve their subgraphs and know who to talk to about potential breaking changes. Today, unplanned breaking changes are fully eliminated.
And, since the supergraph aggregates data from 40 different REST endpoints into one single source of truth, frontend developers are finding the data they need 99.5% faster.
The supergraph is also inspiring developers to experiment with the data they now have at their fingertips. Stephan says, “First, you understand what the supergraph is and what it can do for you. Then you realize you can ask for whatever data you want. Just because you’re working on a certain part of the website doesn’t mean you can’t ask for data they’re displaying somewhere else. If you have an idea you can go to the supergraph and start experimenting.”
Stephan was promoted to run engineering for the online fleet sales business and build out its online service offering. Since most of the data they needed was already in the supergraph, they only had to add a few pieces to the business domain supergraph to build the new products.
One new area they built out is company car policies, which enables a fleet manager to set up rules specific to a company and then the car configurator would just show the options allowed by that policy. They built the initial prototype for that new feature in two and a half weeks.
Stay in our orbit!
Become an Apollo insider and get first access to new features, best practices, and community events. Oh, and no junk mail. Ever.
Make this article better!
Was this post helpful? Have suggestions? Consider so we can improve it for future readers ✨.