Synchronous vs asynchronous communication in Microservices - Architecture Patterns Compared

System Overview - Synchronous vs asynchronous communication

This system demonstrates two common ways microservices communicate: synchronous and asynchronous. Synchronous communication means services wait for a response before continuing, like a phone call. Asynchronous communication means services send messages and continue without waiting, like sending emails.

Key requirements include reliable message delivery, scalability, and clear separation of communication styles.

Architecture Diagram

User
  |
  v
Load Balancer
  |
  v
API Gateway
  |
  +---------------------------+
  |                           |
  v                           v
Service A (Sync)          Service B (Async)
  |                           |
  v                           v
Service C (Sync)          Message Queue
  |                           |
  v                           v
Database                  Service C (Async)
                            |
                            v
                         Database

Components

User

user

Initiates requests to the system

Load Balancer

load_balancer

Distributes incoming requests evenly to API Gateway instances

API Gateway

api_gateway

Routes requests to appropriate microservices

Service A (Sync)

service

Handles synchronous requests and calls Service C synchronously

Service C (Sync)

service

Processes synchronous requests and accesses the database

Service B (Async)

service

Handles asynchronous requests and sends messages to the queue

Message Queue

message_queue

Stores messages for asynchronous processing by Service C

Service C (Async)

service

Consumes messages from the queue and updates the database asynchronously

Database

database

Stores persistent data accessed by services

Request Flow - 19 Hops

User → Load Balancer

Load Balancer → API Gateway

API Gateway → Service A (Sync)

Service A (Sync) → Service C (Sync)

Service C (Sync) → Database

Database → Service C (Sync)

Service C (Sync) → Service A (Sync)

Service A (Sync) → API Gateway

API Gateway → Load Balancer

Load Balancer → User

User → Load Balancer

Load Balancer → API Gateway

API Gateway → Service B (Async)

Service B (Async) → Message Queue

Message Queue → Service B (Async)

API Gateway → Load Balancer

Load Balancer → User

Message Queue → Service C (Async)

Service C (Async) → Database

Failure Scenario

Component Fails:Message Queue

Impact:Asynchronous messages cannot be delivered, causing delays or loss of async processing. Synchronous calls remain unaffected.

Mitigation:Use message queue replication and persistent storage to prevent message loss. Implement retry mechanisms and alerting.

Architecture Quiz - 3 Questions

Which component ensures that asynchronous messages are stored until processed?

A API Gateway

B Message Queue

C Load Balancer

D Service A

Design Principle

This architecture clearly separates synchronous and asynchronous communication paths. Synchronous calls wait for immediate responses, suitable for real-time needs. Asynchronous calls use a message queue to decouple services, improving scalability and resilience by allowing processing to happen later without blocking the user.

Practice

1. Which statement best describes synchronous communication in microservices?

easy

A. The caller waits for the response before continuing.

B. The caller sends a request and continues without waiting.

C. The services communicate only through message queues.

D. The services never exchange data directly.

Solution

1. Step 1: Understand synchronous communication

   Synchronous communication means the caller waits for the response before moving on.

2. Step 2: Compare options

   The caller waits for the response before continuing. matches this definition exactly, while others describe asynchronous or unrelated concepts.

3. Final Answer:

   The caller waits for the response before continuing. -> Option A

4. Quick Check:

   Synchronous = Wait for reply [OK]

Hint: Synchronous means wait for reply before next step [OK]

Common Mistakes:

• Confusing synchronous with asynchronous communication
• Thinking synchronous means no waiting
• Assuming message queues are always synchronous

2. Which of the following is the correct way to describe asynchronous communication in microservices?

easy

A. The caller blocks until the response is received.

B. The caller uses a direct function call to get the result.

C. The services must be on the same server.

D. The caller sends a request and processes the response later.

Solution

1. Step 1: Define asynchronous communication

   Asynchronous means the caller sends a request and does not wait; it handles the response later.

2. Step 2: Evaluate options

   The caller sends a request and processes the response later. correctly describes this behavior. Options A and D describe synchronous calls, and C is unrelated.

3. Final Answer:

   The caller sends a request and processes the response later. -> Option D

4. Quick Check:

   Asynchronous = Send and continue [OK]

Hint: Async means send request, handle reply later [OK]

Common Mistakes:

• Mixing up blocking and non-blocking calls
• Assuming async requires same server
• Thinking async means no response

3. Consider this pseudocode for a microservice call:

response = callServiceSync(request)
print("Done")

What will be the output order?

medium

A. "Done" prints before the service responds.

B. "Done" prints after the service responds.

C. The code throws an error because of missing callback.

D. The code runs asynchronously without waiting.

Solution

1. Step 1: Analyze synchronous call behavior

   The function callServiceSync waits for the service response before returning.

2. Step 2: Determine print timing

   Since the call blocks, "Done" prints only after the response is received.

3. Final Answer:

   "Done" prints after the service responds. -> Option B

4. Quick Check:

   Synchronous call blocks, then prints [OK]

Hint: Sync calls block; print happens after response [OK]

Common Mistakes:

• Assuming print runs before response
• Confusing sync with async calls
• Expecting errors due to missing async syntax

4. A developer wrote this asynchronous call:

sendRequestAsync(request)
print("Request sent")
waitForResponse()

But the system blocks until the response arrives. What is the likely mistake?

medium

A. print statement should be after waitForResponse().

B. sendRequestAsync() is actually synchronous.

C. Calling waitForResponse() immediately blocks the flow.

D. The request object is malformed.

Solution

1. Step 1: Understand asynchronous call flow

   sendRequestAsync should not block, but waitForResponse() forces waiting.

2. Step 2: Identify blocking cause

   Calling waitForResponse() immediately after sends blocks the flow, negating async benefits.

3. Final Answer:

   Calling waitForResponse() immediately blocks the flow. -> Option C

4. Quick Check:

   Immediate wait blocks async [OK]

Hint: Waiting right after async call blocks it [OK]

Common Mistakes:

• Assuming async call is sync
• Misplacing print statement
• Blaming request format instead of flow

5. You design a microservice system where user requests must get immediate confirmation, but heavy processing can be delayed. Which communication pattern fits best?

hard

A. Use synchronous communication for confirmation and asynchronous for processing.

B. Use only synchronous communication for all tasks.

C. Use only asynchronous communication for all tasks.

D. Use synchronous communication for processing and asynchronous for confirmation.

Solution

1. Step 1: Analyze requirements

   Immediate confirmation requires waiting for a quick response (synchronous).

2. Step 2: Handle heavy processing

   Heavy tasks can be done later without blocking user, so asynchronous fits.

3. Step 3: Match communication patterns

   Combining synchronous for confirmation and asynchronous for processing meets both needs efficiently.

4. Final Answer:

   Use synchronous communication for confirmation and asynchronous for processing. -> Option A

5. Quick Check:

   Immediate reply = sync, heavy work = async [OK]

Hint: Immediate reply sync, heavy work async combo [OK]

Common Mistakes:

• Using only sync causes delays
• Using only async delays confirmation
• Reversing sync and async roles