Structure — A high-level system of relationships
Abstraction — Composition and boundaries
Principles — Trade-offs and decision style
Building
Static form
Visible facade
One object
Map
Terrain and constraints
Several routes
Changing environment
Benefits
Lower initial cost
Fast deployment
Proven reliability
Vendor support
Boundary
Regular upgrades
Industry standards
Someone else's product model
Gain
Product change
Own data model
Own release rhythm
Price
Long-term costs
Security
Integration
Vendor dependencies
Spirit gives engineers a self-service path from repository to operations
Self-service — Golden paths instead of tickets
Guardrails — Quality and security in the pipeline
Feedback — SLA, observability and incidents
Architecture becomes a process, an artifact and a shared engineering practice
Prometheus — Replace a critical dependency
100M — Architecture renovation
IT as Lego — Reuse stable parts
Invest in IDP and XaaS
Develop engineer design skills
Strengthen distributed governance
Stop calling everything a platform
Design for reuse
Platform and architecture grow together
ArchDays 2024 deck
Author transcript
Spirit internal developer platform
Architecture governance cases
tellmeabout.tech
Slides, notes and links are on the site
Alexander Polomodov, Technical Director & Fellow, T-Technologies
@book_cube