Diagram
A decision tree that branches on need for immediate response, resilience to spikes and outages, and edge IoT sync to choose Synchronous with Apigee or Asynchronous with Pub/Sub.
Choosing Between Synchronous and Asynchronous Patterns
Choosing between synchronous and asynchronous patterns means matching timing and coupling to the integration problem. Synchronous APIs fit immediate request-and-response work, while asynchronous messaging fits decoupled work that must survive spikes, delays, and outages. The comparison below summarizes when each pattern fits.
| Pattern | Coupling and timing | Choose when |
|---|---|---|
| Synchronous with Apigee | Caller and backend are coupled in time; caller waits for a response over Apigee, Cloud Load Balancing, and hybrid connectivity | The work needs an immediate answer, fine-grained API control, and a stable facade for legacy and modern backends |
| Asynchronous with Pub/Sub | Publisher and subscriber are decoupled in time; data flows from publisher to topic to subscriber | The work must absorb traffic spikes, tolerate intermittent connectivity, or synchronize edge, IoT, and frontend data without blocking |
Domain 6 of 12
23 practice questions
Practice this DomainLast updated