In Event-Driven Architecture, resilience is ensured by:
Loose coupling # Services do not depend on each other's runtime availability. A failure in one service does not directly impact others.
This design minimizes cascading failures that can occur in tightly coupled systems.
Asynchronous communication and error handling help further, but loose coupling is the fundamental characteristic that limits failure propagation.
Incorrect options:
A # Robust error handling is important but not the main architectural limiter of cascading failures.
C # Centralized logging helps with troubleshooting, not failure prevention.
D # Asynchronous buffering mitigates impact but loose coupling fundamentally prevents direct propagation.