API Orchestration with Connectors: Thinking in Entities

Connectors
, , ,
1

Hey everyone,

I just published a new blog post on the Apollo blog about a fresh approach to API orchestration using Connectors—a new concept that makes working with APIs more intuitive by focusing on entities rather than endpoints.

When building APIs, we often think in terms of individual services and how they interact. But what if we flipped that perspective? What if, instead of orchestrating APIs based on service boundaries, we built around the actual entities that developers care about? In the post, I explore how Connectors allow us to take this entity-first approach, making API composition more seamless, scalable, and resilient.

I also cover common API patterns and how you can expose the entity structures in your connectors a couple different ways. You probably have some API patters like:

  • /foo/:foo_id – where the API response contains bar_id
  • /bar/:bar_id

or even

  • /foo/:foo_id
  • /foo/:foo_id/bar

and you can get some concrete examples of how to design these patterns into your schema now :tada:

:book: Read the full post here: API Orchestration with Connectors: Thinking in Entities

Drop your thoughts, questions, and ideas below! I’d love to hear how this approach could help in your API projects. :rocket:

14 Likes