Fintech Trends: Cloud Technologies

A cloud provides a pool of resources that can be allocated and reconfigured as demand changes. Drawing on van Steen and Tanenbaum, the lecture distinguishes four layers: hardware, virtualized infrastructure, platforms, and applications. Application users do not manage server cooling, and developers using a platform service need not know which physical machine holds an object. The layers define different boundaries between customer and provider responsibilities.

IaaS, PaaS, and SaaS map onto these layers. FaaS moves execution of a function into the provider's environment. A Bank of Russia paper adds BaaS for the financial market. Its distinction from banking SaaS concerns what the customer buys: a ready-made accounting or operational process, rather than an application in which the customer still needs to establish that process.

A hierarchy-of-needs analogy explains the motivation: the business wants useful applications, while hardware, infrastructure, and an execution environment remain necessary underneath. A platform team takes responsibility for that foundation so that product teams can concentrate on business features. The benefit is not merely moving servers elsewhere; it is giving developers a usable interface to capabilities they would otherwise have to assemble themselves.

Kubernetes illustrates this approach through declarative deployment, an established ecosystem, and managed offerings in public clouds. Building and maintaining an internal platform is nevertheless complex. The lecture does not turn Kubernetes into a universal recommendation: a large organization must weigh the value of a shared foundation against the development and operating effort required to sustain it.

Using the Bank of Russia's materials, the author distinguishes a niche fintech company, a distributor, a product factory, and a technology company. Their capabilities complement one another: they develop financial services, bring competing offerings to customers, or provide technical integration. The resulting cloud ecosystem extends beyond renting compute capacity to services such as security, data exchange, and access to payment systems.

Placing critical banking operations in a cloud requires attention to regulation and the risks of outsourcing functions. Other factors include capital versus operating expenditure, capacity in the required region, non-functional requirements, and migration costs. The supplementary part introduces edge computing and different forms of distributed ledgers. These broaden the overview without removing the need to choose infrastructure for the requirements of a particular system.