Cloud Native at PostFinance - Is it completely normal?
summary
PostFinance runs 300 applications, 2.5M customers and 8 PB of object data, and moves to AWS since 2022 with a hybrid digital Highlander (on‑prem egress, cloud GPUs/Bedrock for LLMs), digital twins (AKS plus on‑prem Kubernetes, Splunk on‑prem with cloud sync) and digital siblings (Cloudian S3 on‑prem vs AWS S3, Kafka stretch cluster to cloud POC that raises resiliency). Decisions hinge on concrete tools (MSK, Kinesis, Confluent, CloudWatch), costs and exit timelines (months–years for migration, minutes–hours for DR), and ongoing work on a data catalog, sandboxes and private marketplace experiments.
AI-written summary · about
chapters (15)
- 0:00Introduction and speakers
- 1:03Agenda and PostFinance overview
- 4:53Cloud strategy and hybrid approach
- 5:13Cloud native vs cloud agnostic
- 10:07Digital Highlander pattern explained
- 12:39PostFinance Highlander examples
- 14:43Digital twins pattern explained
- 17:13PostFinance twins examples
- 19:40Digital siblings pattern explained
- 21:23PostFinance siblings examples
- 24:10Alternative strategies and mix approach
- 25:35Exit strategy fundamentals
- 34:29PostFinance future outlook
- 37:04Answering the cloud native question
- 38:08Closing and resources
related talks
39mThe Power of Cloud Native in Financial Institutions
57mCreating value from confluence of technology forces (PRT250)
29mCost vs Stability in a Cloud Environment
27mHBF’s AWS cloud transformation
26mCase Study of Success
33mHybrid Cloud in Finance
30mBanking on Cloud Foundry Platform: A Case Study of Digital Business Banking Applications
55mCloud customer trends in 2020