Build vs Buy Analysis
Whether a capability is differentiating enough to build, tested against cost, fit, time and the cost of being wrong.
The curriculum covers what an architect should know. This covers what an architect actually hands over: 55 artifacts, each with a worked example, a note on when it is worth producing, who reads it, and the ways it usually goes wrong. Filter by the artifact's type, the kind of engagement that calls for it, the stack or industry it is drawn against, or the audience it is written for.
Identify the deliverable → 42 diagrams, shown one at a time with the answer withheld. Nothing to submit.
4 of 55 deliverables shown.
Whether a capability is differentiating enough to build, tested against cost, fit, time and the cost of being wrong.
quadrantChart title Platform technologies x-axis "Retire" --> "Adopt" y-axis "Low usage" --> "High usage" quadrant-1 "Adopt — default choice" quadrant-2 "Hold — in use, do not extend" quadrant-3 "Retire — plan removal" quadrant-4 "Trial / Assess — bounded use" "Kubernetes (managed)": [0.92, 0.88] "PostgreSQL": [0.95, 0.93] "Kafka (managed)": [0.86, 0.72] "Terraform": [0.90, 0.80] "OpenTelemetry": [0.78, 0.55] "Service mesh": [0.55, 0.30] "Self-managed Elasticsearch": [0.18, 0.62] "Oracle DB": [0.12, 0.70] "Jenkins": [0.20, 0.45] "Nomad": [0.60, 0.08] "DuckDB (analytics)": [0.62, 0.12]
What the organisation has decided to adopt, trial, assess or retire — a decision record about technology choice, not a fashion report.
The full multi-year cost of an option including the people, the exit and the things that never appear on an invoice.
Options scored against weighted criteria — useful for making the reasoning inspectable, dangerous when the arithmetic is mistaken for the decision.