Event-Driven Microservices

Read-only decision skill. Do not implement the architecture unless the user asks after the brief.

Grounded in Bellemare: a durable, replayable data communication layer of schematized event streams, not point-to-point messages that vanish after consume.

Outcome

• Result: a decision brief with one verdict and the next concrete move.
• Next consumer: the user, or a planning skill after they accept the verdict.
• Done: every required brief field is filled; every load-bearing claim cites repo evidence or is marked assumed; rejected alternatives are named; the next move is one action, not a roadmap.
• Intent: stop two failures — adopting EDM when a modular monolith is cheaper, and building EDM without a data communication layer (implicit schemas, shared DBs, CDC as the destination).

Verdicts: adopt | hybrid | hold | review-fix | migrate-slice

State these four leitwörter by name as you decide, not only in headings: