The Power of Cloud Native in Financial Institutions
summary
mBank builds cloud landings in two public clouds plus private cloud, runs several apps across them and organizes a 77‑person Cloud Center of Excellence supporting ~600 developers. Systems use Terraform for infra, containerd/Docker images on Kubernetes (CNCF‑certified), Prometheus/VictoriaMetrics for observability and Argo CD/Flux for GitOps. Design favors microservices, feature toggles, circuit breakers and chaos tests, uses HSM customer‑managed keys, enforces Azure policies, and maintains documented exit plans tested roughly annually.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:29Agenda
- 2:21The Micro Service Architecture
- 6:20Data and System Security
- 8:46Risk Assessment
- 9:58Exit Strategies
- 10:40Guidelines for Exit Strategies
- 12:23Exit Strategy
- 12:48Migrate from Cloud Provider to on-Premise to Private Cloud
- 14:28Reference Architecture
- 15:30Exit Plan
- 20:15Micro Service Architecture
- 25:59Observability
related talks
48mCloud Security in Action! - A Financial Services Provider Moves to the Cloud
49mPublic cloud in regulated industry, not just swipe of a cred
39mCloud Native at PostFinance - Is it completely normal?
53mFuture Banks Live in The Cloud: Building a Usable Cloud with Uncompromising Security
30mCloud Foundry: The Gaps
26mCase Study of Success
19mKeynote: From COBOL to Kubernetes: A 250 Year Old Bank's Cloud-Native Journey
30mBanking on Cloud Foundry Platform: A Case Study of Digital Business Banking Applications