Slide contents
1. Architecture at T-Bank: Yesterday, Today, Tomorrow
2. Architecture guides significant decisions
Structure — A high-level system of relationships
Abstraction — Composition and boundaries
Principles — Trade-offs and decision style
3. Architecture reveals the terrain
Building
Static form
Visible facade
One object
Map
Terrain and constraints
Several routes
Changing environment
4. Scale changed the architecture response
5. Packaged software accelerates the start
Benefits
Lower initial cost
Fast deployment
Proven reliability
Vendor support
Boundary
Regular upgrades
Industry standards
Someone else's product model
6. In-house code restores control
Gain
Product change
Own data model
Own release rhythm
Price
Long-term costs
Security
Integration
Vendor dependencies
7. In-house development complicates the pipeline
8. 03. Platforms turn complexity into service
Spirit gives engineers a self-service path from repository to operations
9. The platform connects build and run
10. An IDP works only through adoption
Self-service — Golden paths instead of tickets
Guardrails — Quality and security in the pipeline
Feedback — SLA, observability and incidents
11. 04. Governance connects autonomy
Architecture becomes a process, an artifact and a shared engineering practice
12. Experience becomes a standard
13. Changes need different strategies
Prometheus — Replace a critical dependency
100M — Architecture renovation
IT as Lego — Reuse stable parts
14. Architecture stays with engineers
15. The next stage is reusable architecture
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
16. The story is source-verifiable
ArchDays 2024 deck
Author transcript
Spirit internal developer platform
Architecture governance cases
17. Thank you!
tellmeabout.tech
Slides, notes and links are on the site
Alexander Polomodov, Technical Director & Fellow, T-Technologies
@book_cube