Supported by Curity Logotype

Session

With Great Power: How Responsibility Shifts When API Orchestration Is Almost Free

Andrew Carlson
Andrew Carlson Apollo Graph

Orchestration is everywhere. Any application that uses more than 1 service does some kind of API orchestration – and how many experiences only use 2? On average, most apps use somewhere between 26 and 50 APIs, according to Postman in 2024.
Getting data from all of these APIs into the right shape for our users is complex. We need to consider error handling, retries, parallelization, caching, and so many more functional and non-functional requirements. We’ve historically handled this orchestration logic in a bunch of different ways – and they’re all costly. Costly to those of us writing the apps, and even our users. But what would happen if we could reduce the cost of API orchestration to basically $0?

In this talk, we’ll explore different approaches to API orchestration from the client to the server, imperative to declarative, and see what happens when the time it takes to integrate an API goes from months to days.

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.

By clicking below, you agree that we process your information per the terms in our Privacy Policy.

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.