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 who calls the API and what they need from it. REST is the default for anything public or cacheable; the finder leaves it only for a named reason — server push, many client shapes, typed high-throughput internal calls, or events you must deliver to someone else.
Step 1
Who calls this API?
The consumer decides more than the data does: you control internal clients and can regenerate them; you cannot regenerate a partner's integration.