GraphQL API Composition

Didier Micoud
Didier Micoud Expedia Group - Vrbo

The increased interest in exposing APIs to external partners has caused some headaches in building a consistent and cohesive set of APIS.
We have been maintaining legacy SOAP or REST Like APIs that still provide value to our consumers but have been considering GraphQL as a way to expose capabilities and features in a unified way.
While GraphQL has been primarily considered for the flexibility of the query language, we saw an opportunity to preserve our domain driven design architectural approach in building reusable modules to allow for Graphcomposition.

  • Why GraphQL: Customer Centricity, Consistency, Extensibility
  • Composition and Separation of concerns: Domain Driven Design calls for bounded domains while experiences need composition
  • Building an experience graph: GraphQL Components, Apollo Federation
Smarter Tech Decisions Using APIs

Smarter Tech Decisions Using APIs

API blog

High impact blog posts and eBooks on API business models, and tech advice

API conferences

Connect with market leading platform creators at our events

API community

Join a helpful community of API practitioners

API Insights Straight to Your Inbox!

Can't make it to the event? Signup to the Nordic APIs newsletter for quality content. High impact blog posts on API business models and tech advice.

Join Our Thriving Community

Become a part of our global community of API practitioners and enthusiasts. Share your insights on the blog, speak at an event or exhibit at our conferences and create new business relationships with decision makers and top influencers responsible for API solutions.