architecture-paradigm-event-driven

Structure systems around asynchronous, event-based communication to decoupleproducers and consumers for improved scalability and resilience.Triggers: event-driven, message queue, pub/sub, asynchronous processing, event bus,real-time processing, loose coupling, event choreography, event orchestrationUse when: real-time or bursty workloads (IoT, trading, logistics), multiplesubsystems react to same events, system extensibility is high priorityDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: simple request-response patterns suffice.DO NOT use when: strong ordering guarantees are critical without careful design.Consult this skill when designing event-driven systems or implementing messaging patterns.