Learn AI ↗

Deliverables

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.

Type Any Structural View8 Behavioural View7 Data View7 Deployment & Infrastructure View7 Security View7 Governance Artifact8 Planning Artifact5 Analysis Artifact6
Use case Any Greenfield Build29 Legacy Migration19 Cloud Landing Zone13 Data Platform Build10 AI / ML Platform2 Integration Programme13 Security Uplift12 Cost Optimisation12 Merger & Acquisition Integration14 Regulatory Remediation11 Resilience Programme9 Vendor Selection10
Technology Any Cloud-Agnostic55 Azure2 AWS2 Kubernetes4 Kafka2 Databricks1 Hybrid3
Domain Any Cross-Industry55 Retail & E-Commerce3 Banking & Payments12 Healthcare & Pharma8 Insurance1
Audience Any CxO25 Architecture Review Board38 Engineering36 Operations & SRE22 Security12 Finance9 Regulator & Audit8

3 of 55 deliverables shown. 

flowchart TB
  subgraph l1["Experience"]
    direction LR
    e1["Web"] --- e2["Mobile"] --- e3["Partner Portal"]
  end
  subgraph l2["Channel & API"]
    direction LR
    c1["API Gateway"] --- c2["BFF"] --- c3["Event Ingress"]
  end
  subgraph l3["Business Services"]
    direction LR
    b1["Ordering"] --- b2["Pricing"] --- b3["Fulfilment"] --- b4["Billing"]
  end
  subgraph l4["Integration"]
    direction LR
    i1["Message Broker"] --- i2["Adapters"] --- i3["File Transfer"]
  end
  subgraph l5["Data"]
    direction LR
    d1["Operational Stores"] --- d2["Analytical Platform"] --- d3["Cache"]
  end
  subgraph l6["Infrastructure"]
    direction LR
    f1["Compute"] --- f2["Network"] --- f3["Storage"]
  end
  l1 --> l2 --> l3 --> l4 --> l5 --> l6

  sec["Security<br/>&<br/>Identity"]
  ops["Observability<br/>&<br/>Operations"]
Structural View

Layered Architecture Diagram

The solution as horizontal capability tiers with cross-cutting concerns as vertical bars — the picture executives expect and the one most often drawn without meaning.
Reference Models Design 
flowchart TB
  u(["Users"]) --> gslb["Global traffic manager<br/><i>health + latency routing</i>"]

  subgraph ra["Region A — write primary"]
    direction TB
    a1["Edge + API"]
    a2["Services"]
    a3[("Primary DB<br/><i>accepts writes</i>")]
    a1 --> a2 --> a3
  end

  subgraph rb["Region B — read + standby"]
    direction TB
    b1["Edge + API"]
    b2["Services"]
    b3[("Replica<br/><i>read only · lag &lt; 2s</i>")]
    b1 --> b2 --> b3
  end

  gslb -->|"reads: nearest"| a1
  gslb -->|"reads: nearest"| b1
  gslb -->|"writes: always A"| a1
  b2 -.->|"write forwarding<br/>+45ms"| a2
  a3 ==>|"async replication"| b3
  arb{{"Failover arbitration<br/><i>manual promote · documented<br/>RPO &le; 2s · RTO 15 min</i>"}}
  arb -.-> a3
  arb -.-> b3
Deployment & Infrastructure View

Multi-Region Topology

How many regions serve traffic, where writes are allowed, how data converges, and what the split-brain answer is.
Multi-Region Rollout Design