System Design Space
Knowledge graphSettings

Updated: February 21, 2026 at 11:59 PM

Cloud technologies

mid

Speech on the role of cloud technologies: IaaS/PaaS/SaaS/BaaS, elastic scaling, risks of cloud adoption and practical scenarios.

Cloud technologies

A presentation on how cloud technologies are changing product systems: from the speed of solution output to sustainability, security and architectural trade-offs.

Year:2023
Production:T-Education
Duration:38:41

Source

Article on the report

Text version and key points of the speech about cloud technologies in fintech.

Read the article

About the performance

The report examines the cloud as the foundation of modern fintech infrastructure and explains why the transition to the cloud is not only a technological step, but also a change in the company’s operating model.

Focus: Economic Model pay-per-use, managing workload growth, security risks, and designing systems that remain resilient in the face of rapidly changing business demands.

Speaker and regalia

Alexander Polomodov

  • Lecturer of the course “Fintech trends”.
  • Head of Digital Ecosystem Development Department at Tinkoff.
  • Practitioner in the field of cloud architectures and scalable fintech systems.

Key topics

Why clouds have become the basis of fintech

Cloud gives you speed of launch, infrastructure flexibility, and the ability to quickly test new product hypotheses.

Service models: IaaS / PaaS / SaaS / BaaS

Understanding layers of abstraction and how teams choose between controllability, speed, and cost of ownership.

Elastic scaling and peak loads

Fintech systems must withstand sudden surges in traffic without losing SLAs and user experience.

Risks of cloud adoption

Vendor lock-in, data protection requirements, compliance and dependence on network availability.

Providers and architectural trade-offs

Comparison of approaches of different clouds and practical trade-offs between price, functionality and operational complexity.

Where is the market heading?

Edge-cloud scenarios, blockchain direction and strengthening of hybrid architectures for regulated domains.

Related chapter

Cloud Native Overview

General map of the section: 12-factor, Kubernetes, distributed patterns and cloud operation.

Open chapter

Practical conclusions

For engineers

  • Design cloud-native services: stateless contours, auto-scaling, explicit SLO/SLA.
  • Manage provider dependencies: abstraction layer, migration plan and fallback scenarios.
  • Immediately take into account data requirements: encryption, auditing, key rotation and compliance policies.
  • Design observability as part of the architecture, not as an after-the-fact tool.

For team leads and CTO

  • Cloud strategy must be linked to business priorities, not just infrastructure fads.
  • We need a balance of speed and control: platform guardrails, security baseline, cost governance.
  • DR/BCP scripts and regular robustness checks are mandatory for fintech workloads.
  • The decision between single-cloud, multi-cloud and hybrid must be made based on risk and economics.

Links to materials

Enable tracking in Settings

System Design Space

© 2026 Alexander Polomodov