21.14 Architect Playbook & Checklist
Discovery
- business outcomes defined
- domains identified
- source ownership known
- consumers identified
- data classification defined
- freshness and latency targets agreed
Architecture
- tenant topology justified
- space topology justified
- integration patterns selected
- logical data layers defined
- semantic contracts defined
- data products identified
- security architecture defined
- governance model defined
- workload model defined
Production
- lifecycle path defined
- monitoring and SLOs defined
- recovery objectives defined
- support ownership assigned
- capacity model defined
- cost ownership defined
Architecture defense
Be able to explain:
- Why Datasphere?
- Why this tenant topology?
- Why these spaces?
- Why federation versus persistence?
- Why this semantic boundary?
- Why this security boundary?
- Why this data product boundary?
- How does the architecture scale?
- How does it fail?
- How does it recover?
- What does it cost?
- What would cause a redesign?
Final principle
An enterprise architecture is successful when ownership, semantics, security, operations and technology reinforce each other.