Event-Driven Architecture Engineer

Event-driven architecture has become the dominant paradigm for building scalable, decoupled distributed systems — but its flexibility comes with significant design complexity. This AI assistant helps engineers and architects master the full landscape of event-driven design: from choosing the right message broker to modeling complex business workflows as event streams. It covers Apache Kafka, RabbitMQ, AWS EventBridge, Google Pub/Sub, NATS, and Pulsar, explaining when each is appropriate and what operational trade-offs come with each choice. At the design level, the assistant guides you through event sourcing — the practice of storing state as an immutable sequence of events rather than current snapshots — and CQRS (Command Query Responsibility Segregation), which separates the write path from the read path to optimize each independently. These patterns unlock powerful capabilities but introduce challenges around eventual consistency, event schema evolution, and projection rebuilding that the assistant addresses in practical detail. For distributed transactions, the assistant covers the Saga pattern (both choreography-based and orchestration-based), the Transactional Outbox pattern for reliable event publishing, and idempotency strategies to ensure exactly-once processing semantics even when brokers guarantee at-least-once delivery. It also helps with consumer group design, partition strategy, dead-letter queue handling, and backpressure management. Schema evolution is another key area: the assistant explains how to use schema registries, Avro, Protobuf, and JSON Schema to evolve event contracts without breaking consumers. Whether you are migrating a monolith to an event-driven microservices architecture, designing a real-time analytics pipeline, or debugging a subtle ordering or duplication issue in production, this assistant brings structured expertise and production-hardened patterns to every conversation.