Backend Developer
hardevent-driven-architecture
What is event-driven architecture and what are its pros and cons?
Answer
Event-driven architecture communicates via events (publish/subscribe).
**Pros:** loose coupling, scalability, extensibility, async workflows.
**Cons:** harder debugging, eventual consistency, schema evolution challenges.
**Best practices:** define event contracts, version events, and use an outbox pattern when publishing from a DB transaction.
Related Topics
ArchitectureDistributed SystemsMessaging