Synchronous vs asynchronous communication in Microservices - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding communication types in microservices

Which statement best describes synchronous communication in microservices?

A The services use batch processing to exchange data periodically.

B The caller sends a message and continues without waiting for a response.

C The services communicate only through shared databases.

D The caller waits for the response before continuing its process.

💡 Hint

Think about whether the caller pauses or not.

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

❓ Architecture

intermediate

Choosing communication style for a payment service

You design a payment microservice that must confirm transactions immediately to the user. Which communication style is best?

A Synchronous communication with direct API calls.

B Asynchronous communication using message queues.

C Batch processing every hour to update payment status.

D Using shared database polling for updates.

💡 Hint

Immediate confirmation means waiting for the result.

Synchronous communication allows immediate response, suitable for payment confirmation.

❓ scaling

advanced

Scaling microservices with asynchronous communication

Which advantage does asynchronous communication provide when scaling microservices?

A It allows services to handle requests independently without waiting, improving throughput.

B It requires synchronous locks to maintain data consistency.

C It forces all services to be tightly coupled for faster response times.

D It reduces the need for load balancing by processing requests sequentially.

💡 Hint

Think about how waiting affects throughput.

Asynchronous communication lets services work independently, increasing throughput and scalability.

❓ tradeoff

advanced

Tradeoffs between synchronous and asynchronous communication

What is a key tradeoff when choosing synchronous communication over asynchronous in microservices?

A Synchronous communication improves fault tolerance but increases latency.

B Synchronous communication reduces latency but can cause tight coupling and blocking.

C Synchronous communication eliminates the need for retries and error handling.

D Synchronous communication always scales better than asynchronous.

💡 Hint

Consider how waiting affects coupling and blocking.

Synchronous calls reduce latency but create tight coupling and can block services if one is slow.

❓ estimation

expert

Estimating system capacity for asynchronous messaging

A microservice system uses asynchronous messaging with a queue that processes 1000 messages per second. If peak load is 5000 messages per second for 10 seconds, what minimum queue size is needed to avoid message loss?

A 5000 messages

B 10000 messages

C 40000 messages

D 6000 messages

💡 Hint

Calculate the excess messages arriving during peak load that the queue must hold.

During 10 seconds, 5000 msgs/sec arrive = 50000 msgs. Processing at 1000 msgs/sec = 10000 msgs processed. Queue must hold 50000 - 10000 = 40000 msgs.

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