Flink architecture and automation in Intesa Sanpaolo
summary
Intesa Sanpaolo runs Apache Flink on containerized OpenShift clusters with cross‑region storage replicas and a plan for active‑active cloud migration, processing peaks around Kafka throughput 17k events/sec and near 5 TB ingested over busy weekends while supporting ~1 billion mobile hops/year and 7 million active users. Automation uses ArgoCD GitOps plus config‑map driven templates and a custom operator to push job state and deployments; provisioning, job rollout and DR failover are automated and already shorten delivery and reduce manual ops.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:14Stream Architectures in Intesa Sanpaolo
- 7:56From Apache Storm to Apache Flink
- 9:23Flink's current use cases
- 12:20Our Flink architecture
- 17:21Flink's Automation design
related talks
35mApache Flink 2.0: Unified Enterprise Data Processing System and Beyond
37mBuilding and operating large-scale streaming applications at King
42mApache Flink deep-dive #bbuzz
20mAutoscaling Apache Flink Applications
42mApache Flink meets Apache Mesos and DC/OS
45mMulti-tenant Flink-as-a-Service on YARN
38mAutoscaling Flink at Netflix
34mHands-on Stateful Serverless Applications with Kubernetes and Stateful Functions
