Review a design
Reviewer answers a question Architect does not: how well does the architecture I actually have — or plan to build — fit this workload? It scores a chosen architecture against the same domain-adjusted requirements and surfaces strengths, gaps, and watch-outs.
The fastest way in is from Architect: the "Review this design" link pre-loads the scenario and the winning architecture.
When to use it
- Before committing to a design — validate it against real requirements.
- Auditing an existing stack before a migration or upgrade.
- Comparing two candidate designs side by side for the same workload.
The five steps
Choose a workload scenario
Select one of the 18 scenarios, or arrive pre-loaded from an Architect recommendation.
Select the architecture to review
Pick the design under review from the ten reference architectures — the one you already run or plan to build.
Check the requirements
Review the requirements that will be scored. If a domain profile exists, they are adjusted for your domain context — the same adjustments Architect used.
Generate the review
Reviewer scores fit across all eight criteria and produces a verdict with per-criterion scoring.
Read the gaps & act
Review strengths, gaps, and watch-outs — the concrete changes that would move the fit, and the risks to keep an eye on.
Reading the verdict
- Fit score. An overall measure of how well the architecture matches the workload requirements.
- Per-criterion scores. Where the design shines and where it struggles, criterion by criterion.
- Strengths. The reasons the fit is good — reuse these in your design review write-up.
- Gaps. The highest-impact mismatches and what would close them.
- Watch-outs. Operational or long-term risks worth tracking even if the fit looks good.
Because Reviewer shares the domain context with Architect, the two verdicts are consistent: you evaluate with the same weights you review against.
Workflow tips
- Compare candidates. Run the same scenario twice with different architectures and put the verdicts side by side.
- Validate before you migrate. Review the current stack first, then the target — the gap list doubles as a migration checklist.
- Pair with the domain profile. If requirements look off, re-run Domain Context Learner — the review follows the profile.
Prefer to see it working? Follow the e-commerce example end to end →