You want to add a new feature that analyzes historical user actions using event replay. Which design choice best supports this without affecting live system performance?

hard📝 Trade-off Q15 of 15

Microservices - Event-Driven Architecture

AReplay events asynchronously from a separate event store copy

BReplay events synchronously on the main database during user requests

CReplay only the latest event repeatedly for analysis

DSkip event replay and query live data directly

Step-by-Step Solution

Solution:

Step 1: Understand impact of replay on live system
Replaying events synchronously during user requests can slow down or disrupt the live system.
Step 2: Choose design for performance and safety
Using a separate copy of the event store and replaying asynchronously isolates analysis from live traffic, preserving performance.
Final Answer:
Replay events asynchronously from a separate event store copy -> Option A
Quick Check:
Async replay on copy = no live impact [OK]

Quick Trick: Use async replay on separate store to avoid live system load [OK]

Common Mistakes:

MISTAKES

Replaying synchronously blocking live requests
Analyzing only latest event missing history
Ignoring benefits of event replay for analysis

Master "Event-Driven Architecture" in Microservices

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Arch Try Challenge Design Recall Scale

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Microservices Quizzes

You want to add a new feature that analyzes historical user actions using event replay. Which design choice best supports this without affecting live system performance?

Step 1: Understand impact of replay on live system

Step 2: Choose design for performance and safety

Final Answer:

Quick Check:

Want More Practice?