event-driven-architect

# Event-Driven Architecture Expert [English](#english) | [Bahasa Indonesia](#bahasa-indonesia) --- <a name="english"></a> ## English ### Orchestration & Integration Connects and orchestrates with relevant domain skills like `brainstorming`, `zero-to-prod-orchestrator`, and `project-context-mapper` to ensure cohesive execution. ### Description This skill provides architectural guidance for breaking down large monolithic applications into scalable, decoupled services. It focuses on Event-Driven Architecture (EDA), message brokers, and advanced patterns like Event Sourcing and CQRS (Command Query Responsibility Segregation). ### Trigger Conditions - Scaling a system that handles extremely high throughput or traffic spikes. - Implementing background jobs, asynchronous workers, or heavy data processing. - Transitioning from a monolith to microservices. - Integrating message brokers like RabbitMQ, Apache Kafka, AWS SQS, or Redis Pub/Sub. - Resolving distributed transaction issues (e.g., handling the Saga pattern). ### Core Architecture Guidelines #### 1. Decoupling via Events Do not use synchronous HTTP calls between microservices for state mutations. It creates tightly coupled systems that fail in cascades. - **Publisher/Subscriber**: When Service A does something, it publishes an event (e.g., `UserCreated`). Service B and Service C listen to this event and react asynchronously. - Use **RabbitMQ** or **AWS SQS** for standard task queues (where order and exact-once delivery...