Evidence before architecture acceptance
A convincing diagram is a starting point. This edition asks what the customer actually owns, which HLD claims have a source and what evidence allows a migration to proceed.
Start with the decisionOne question across three boundaries
SaaS delegates much of the implementation, while the customer still owns its channel, identity, data and integrations. The exercise establishes boundaries and evidence for behaviour the customer depends on.
AI can organise vendor documents and produce an HLD. It can also turn an unknown into a plausible statement. The tutorial retains sources and visible gaps.
Google’s ISTIOD retirement announcement gives a concrete lifecycle decision. Across all three topics, ask who owns the result, what was agreed and how it will be demonstrated.
In this edition
- 01 · Practice
The provider delivers SaaS. Do you need to know its architecture?
Distinguish implementation details from information needed to assess responsibility and risk.
Read the material → - 02 · Foundations
SaaS architecture due diligence: what the customer needs to know
Seven review areas and a responsibility → requirement → evidence matrix.
Read the material → - 03 · Anti-pattern
It is SaaS, so the provider architecture is none of our concern
Service responsibilities cannot be reduced to an API and SLA.
Read the material → - 04 · Architect + AI
AI drafted an HLD from vendor documents. What do we know, and what did it invent?
A source register, visible unknowns and design-changing questions.
Read the material → - 05 · Architecture in motion
Cloud Service Mesh retires ISTIOD: plan a boundary migration
The 1 March 2028 deadline, two migration paths and evidence before moving traffic.
Read the material →
Three more dilemmas from our editorial work
These are practice prompts, not accounts of confirmed incidents.
A conditional decision: who verifies completion?
Name an owner, evidence, an acceptance criterion and a launch decision.
Three places show different standards. Which one applies?
Establish an authoritative source, version and owner.
An agent checks publication hourly. Who completes it?
Separate monitoring from an executable process with states, an owner and recovery.
Continue the discussion with practitioners
The catalogue includes current dates, confirmation limits and organiser links.
Browse events