Architecture Style Selector

When to Use

You need to choose or recommend an architecture style for a system. This is the culminating architecture decision — it integrates characteristics analysis, quantum analysis, and feasibility checking into a concrete style recommendation. Typical situations:

• New system — "we're building X, what architecture should we use?"
• Architecture evaluation — "should we use microservices or event-driven?"
• Migration — "we've outgrown our monolith, what should we move to?"
• Validation — "we chose microservices, was that right?"
• Post-analysis — you've identified characteristics and quanta, now pick the style

Before starting, verify:

• Are architecture characteristics identified? If not, use architecture-characteristics-identifier first — you need the top 3 driving characteristics.
• Is quantum analysis done? If components need different quality attributes, use architecture-quantum-analyzer first — quantum count determines monolith vs distributed.
• If the user is only asking whether distribution is feasible (not which style), use distributed-feasibility-checker instead.

Context & Input Gathering