Pattern 12 / COMMS

Request-Response (Synchronous)

Use this when asking another component for an immediate answer.

Pressure
Asking another component for an immediate answer
Mechanism
Client sends a request and blocks until the server returns success, failure, or timeout
Toll
Latency and failures propagate directly through synchronous call chains
Architecture plate12
Diagram for Request-Response (Synchronous)
Executive brief

Request-Response (Synchronous) fits when asking another component for an immediate answer. Mechanism: client sends a request and blocks until the server returns success, failure, or timeout. Use it for user-facing APIs, authentication, validation, reads, and simple command flows. The toll: latency and failures propagate directly through synchronous call chains.

Use when

User-facing apis, authentication, validation, reads, and simple command flows.

Example

Mobile app calling an api to fetch account balance.

Review framing

Describe the pressure first, then the mechanism, then the cost. That keeps the design grounded.

Same pressure family

Communication Patterns

13Message Queue (Asynchronous)14Publish-Subscribe (Pub/Sub)15Event-Driven Architecture16Webhooks17Server-Sent Events (SSE)18Bidirectional Streaming (WebSockets / gRPC Streaming)
โ† 1113 โ†’