Why events decouple services in Microservices - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to show how an event helps services communicate without direct calls.

Microservices

serviceA.publish([1])

Drag options to blanks, or click blank then click option'

A"OrderCreatedEvent"

B"SynchronousRequest"

C"DirectCall"

D"TightlyCoupledCall"

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing direct or synchronous calls which tightly couple services.

Publishing an event like "OrderCreatedEvent" allows services to communicate without direct calls, enabling decoupling.

2fill in blank

medium

Complete the code to show how a service listens for an event to react asynchronously.

Microservices

eventBus.subscribe("OrderCreatedEvent", [1])

Drag options to blanks, or click blank then click option'

AhandleOrderCreated

BcallServiceDirectly

CsendSyncRequest

DblockUntilResponse

Attempts:

3 left

💡 Hint

Common Mistakes

Using direct calls or blocking functions which reduce decoupling.

Subscribing with a handler function like handleOrderCreated allows reacting to events asynchronously.

3fill in blank

hard

Fix the error in the code to properly decouple services using events.

Microservices

serviceB.processOrder()  # Incorrect direct call
serviceA.[1](orderData)  # Correct event publish

Drag options to blanks, or click blank then click option'

AcallDirectly

BinvokeService

CpublishEvent

DsendSyncRequest

Attempts:

3 left

💡 Hint

Common Mistakes

Keeping direct calls which tightly couple services.

Using publishEvent sends an event instead of a direct call, decoupling services.

4fill in blank

hard

Fill both blanks to complete the event-driven communication pattern.

Microservices

eventBus.[1]("PaymentProcessed", [2])

Drag options to blanks, or click blank then click option'

Apublish

BhandlePayment

Csubscribe

DsendRequest

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up publish and subscribe methods.

Subscribing to the "PaymentProcessed" event with handlePayment decouples services.

5fill in blank

hard

Fill all three blanks to complete the event-driven service interaction.

Microservices

serviceA.[1]("UserRegistered", data)

serviceB.[2]("UserRegistered", [3])

Drag options to blanks, or click blank then click option'

Aemit

Bsubscribe

ChandleUserRegistration

DcallDirectly

Attempts:

3 left

💡 Hint

Common Mistakes

Using direct calls instead of events.

Service A emits the "UserRegistered" event, and Service B subscribes to it with handleUserRegistration to stay decoupled.

Practice

1. Why do events help decouple microservices in a system?

easy

A. Because events force services to share the same database

B. Because events require services to be tightly connected

C. Because services communicate by sending events without waiting for direct responses

D. Because events make services dependent on each other's code

Solution

1. Step 1: Understand event communication

   Events allow services to send messages asynchronously without expecting immediate replies.

2. Step 2: Analyze coupling impact

   This asynchronous communication means services don't need to know about each other's internal details or be directly connected.

3. Final Answer:

   Because services communicate by sending events without waiting for direct responses -> Option C

4. Quick Check:

   Events enable loose coupling = B [OK]

Hint: Events mean no direct calls between services [OK]

Common Mistakes:

• Thinking events require shared databases
• Believing events increase tight connections
• Assuming events force code sharing

2. Which of the following is the correct way to describe event-driven communication between microservices?

easy

A. Service A calls Service B's API and waits for a response

B. Service A publishes an event to a message broker and continues processing

C. Service A directly updates Service B's database

D. Service A shares its memory space with Service B

Solution

1. Step 1: Identify event-driven communication

   Event-driven means a service publishes events to a broker without waiting for immediate replies.

2. Step 2: Match options to event-driven style

   Only publishing to a message broker and continuing processing fits event-driven communication.

3. Final Answer:

   Service A publishes an event to a message broker and continues processing -> Option B

4. Quick Check:

   Publish and forget = C [OK]

Hint: Event-driven means publish and continue, not wait [OK]

Common Mistakes:

• Confusing direct API calls with event publishing
• Thinking services share databases directly
• Assuming shared memory is used

3. Consider this code snippet in a microservices system using events:

eventBus.publish('OrderCreated', { orderId: 123 });
// Service B listens for 'OrderCreated' and processes the order asynchronously

What is the main benefit of this event-based approach?

medium

A. Service A directly calls Service B's function to create the order

B. Service A waits for Service B to finish processing before continuing

C. Service B must be available before Service A publishes the event

D. Service A and Service B are loosely coupled and can operate independently

Solution

1. Step 1: Analyze event publishing behavior

   Service A publishes an event and does not wait for Service B to process it immediately.

2. Step 2: Understand coupling impact

   This means Service A and Service B do not depend on each other's availability or internal logic, enabling loose coupling.

3. Final Answer:

   Service A and Service B are loosely coupled and can operate independently -> Option D

4. Quick Check:

   Asynchronous event handling = A [OK]

Hint: Events let services work independently without waiting [OK]

Common Mistakes:

• Assuming Service A waits for Service B
• Thinking Service B must be online before event publish
• Confusing direct calls with event publishing

4. A developer wrote this code snippet for event communication:

eventBus.publish('UserCreated', userData);
userService.createUser(userData);

What is the main problem with this approach regarding decoupling?

medium

A. The event is published before the user is created, causing inconsistency

B. The userService call is synchronous, blocking the event publishing

C. The eventBus and userService are tightly coupled by calling both directly

D. There is no problem; this is a fully decoupled event-driven design

Solution

1. Step 1: Check event timing relative to action

   The event 'UserCreated' is published before the actual user creation happens.

2. Step 2: Understand impact on consistency and decoupling

   This can cause other services to react to an event for a user that does not yet exist, breaking consistency and decoupling principles.

3. Final Answer:

   The event is published before the user is created, causing inconsistency -> Option A

4. Quick Check:

   Publish event after action = D [OK]

Hint: Publish events only after the action completes [OK]

Common Mistakes:

• Publishing events before the actual state change
• Assuming synchronous calls improve decoupling
• Thinking calling both is fully decoupled

5. In a large microservices system, why does using events to decouple services improve system scalability and fault tolerance?

hard

A. Because events allow services to process messages independently and retry on failure

B. Because events force all services to run on the same server

C. Because events require services to be tightly synchronized

D. Because events eliminate the need for any service monitoring

Solution

1. Step 1: Understand event-driven processing benefits

   Events let services handle messages independently, so they can scale by adding more instances and retry failed processing without blocking others.

2. Step 2: Analyze impact on fault tolerance and scalability

   This independence isolates failures and allows the system to continue working smoothly, improving overall reliability and scalability.

3. Final Answer:

   Because events allow services to process messages independently and retry on failure -> Option A

4. Quick Check:

   Independent processing and retries = A [OK]

Hint: Events enable independent retries and scaling per service [OK]

Common Mistakes:

• Thinking events force services to share servers
• Assuming tight synchronization improves scalability
• Believing events remove need for monitoring