Slide contents

1. 1. Architecture in a Large Fintech

   How to design solutions and preserve integrity at scale

2. 2. Alexander Polomodov

   Alexander Polomodov, Technical Director, T-Bank

   Architecture and delivery management

   Client interfaces and marketing

   Company-wide architecture practices

3. 3. Architecture is shared decision language

   Structure — Significant system decisions

   Boundaries — Trajectory and allowed change

   Integrity — One model for participants

4. 4. The domain determines architecture effort

5. 5. Complexity needs different operating modes

6. 6. Distant strong coupling costs most

7. 7. Architecture starts beyond one team

8. 8. 02. Integrity needs a system

   Organisation, platform and written process must support one architecture

9. 9. Communication becomes architecture

10. 10. A platform makes standards self-service

11. 11. A decision leaves verifiable traces

12. 12. The document connects to production

    Design

    Markdown

    PlantUML / Structurizr

    RFC / ADR

    MR review

    Runtime

    Observability

    Service SLOs

    Incident management

    Performance tests

13. 13. Architecture connects decisions

    Effort follows the domain

    Coupling has a price

    Team boundaries matter

    Platforms encode standards

    Runtime tests the model

    Integrity is created together

14. 14. Core models in the source

    Booch · Software Architecture

    Learning Domain-Driven Design

    Balancing Coupling in Software Design

    Team Topologies

15. 15. Thank you!

    tellmeabout.tech

    Slides, notes and links are on the site

    Alexander Polomodov, Technical Director & Fellow, T-Technologies

    @book_cube