Event-driven architecture benefits in MDC3?

• A. Monolithic Synchronous Processing
• B. Tightly Coupled Components
• C. Event-Driven Architecture Uses Events To Trigger Decoupled Processing Via Messaging; Benefits Include Scalability And Responsiveness
• D. Increased Latency

Answer: (C)

Event-driven architecture focuses on decoupling through asynchronous messaging, where events trigger processing in independent components. Because producers just publish events and producers don’t call specific consumers, parts of the system can operate, scale, and evolve separately.

This setup brings scalability because each event handler can be scaled horizontally to match the load, without needing to scale the entire application. It also boosts responsiveness since work begins as soon as events arrive, often in parallel, reducing bottlenecks and latency in processing flows.

Additional context helps: in an online store, an event like orderPlaced can be consumed by multiple services—payments, inventory, and notifications—each handling its task independently. If demand spikes, you add more instances of those handlers without reworking the producer.

The other options describe patterns that aren’t benefits of this approach. Monolithic synchronous processing is blocking and tightly coupled, which limits scalability and resilience. Tightly coupled components reduce flexibility and increase risk of cascading failures. Increased latency is not a benefit; the goal of event-driven design is to improve throughput and responsiveness, though certain edge cases may introduce overhead, the overall direction is toward lower latency and better scalability.