Cloud strategy для банка: public, private, hybrid

Когда возникает развилка

Банк решает infrastructure strategy. Public cloud (AWS, Azure, GCP) elastic + managed services. Private (on-prem или managed) — control + residency. В УЗ — local clouds (UCell Cloud, Beeline Cloud) с regulatory positioning но limited services.

cbu.uz cloud guidelines tightening — банк должен engage early.

Per-workload criteria

Data residency. ПДн в стране — disqualifier для public cloud без local region.

Latency. ABS, card processing, payments — low latency. Public cloud distant — disqualifier.

Workload variability. Marketing campaigns spiky — public elastic. ABS steady — private cheaper.

Managed services. ML, analytics — public faster. Custom — less benefit.

Vendor lock-in. Public — managed services lock-in. Private — hardware/license.

Regulatory openness. Регулятор позиция меняется — нужно tracking.

Per-workload split typical

Customer-facing apps & decisioning — local cloud / private (latency).

CRM, marketing, analytics — public (если data residency allows).

ABS, biller, ledger — private (residency, low risk tolerance).

ML training — public для elasticity, serving — local.

DR / backup — multi-region public.

Where decisions usually go wrong

«All public» без regulatory check. Regulator complaint.

«All private» — миссес elasticity benefits.

Lift-and-shift в public — TCO higher than on-prem.

Vendor lock-in без exit story.

Что обсуждать в комитете

Data residency requirements per workload — regulator clarification.

Per-workload TCO 5-year.

Skill set audit и hire/retrain plan.

Vendor lock-in mitigation.

cbu.uz cloud guidelines update.

Связанное

• /architecture/banking-around-core-architecture/ — wrap
• /insights/banking-vendor-management/ — vendor
• /insights/banking-platform-tco/ — TCO
• /decisions/banking-abs-modernization-timing/ — ABS decision