Distributed Architecture Feasibility Checker

When to Use

Someone is proposing or considering distributed architecture (microservices, service-based, event-driven) and you need to evaluate whether it's actually justified and feasible. Typical situations:

• "Let's move to microservices" — but has anyone checked if the team is ready?
• Growing pains with a monolith — but is distribution the right solution?
• CTO or tech lead pushing for distribution based on industry hype
• Pre-requisite sanity check before architecture-style-selector
• Post-quantum-analysis: you've identified multiple quanta, now check if the team can actually operate distributed

Before starting, verify:

• Is there a genuine architectural problem to solve? (If the monolith is working fine, distribution adds cost without benefit)
• Has quantum analysis been done? If not, distribution may not even be needed (use architecture-quantum-analyzer first)

Context & Input Gathering

Input Sufficiency Check