Architecture Finder
“What architecture should I use?” Answer questions about team size, deployment independence, scaling characteristics, data ownership, reliability and complexity tolerance. Every recommendation says why, what the risks are, and what the alternatives were — and it starts from the simplest option that could work.
Describe one call between two components. The finder decides whether the caller waits, hands the work to a queue, or publishes an event — and when the honest answer is "synchronous, but protected". Asynchrony is not free: it trades a visible timeout for an invisible backlog.
A price, an authorisation, a stock check: the response depends on it. An email, a thumbnail, an analytics event: the response does not. Be honest about "nice to show immediately" versus "cannot respond without".