DevOps at ING Analytics
summary
ING moves its analytics from batch to continuous delivery using an engineering culture, standardized pipelines (Jenkins, GitLab) and chapters/tribes to ship a real-time decision engine built on Apache Flink and Kafka with ML models deployed via PMML. The pipeline detects event patterns (CEP), scores models for relevance, and pushes personalized propositions into the banking app; it runs in production, stops a fraud attempt and drives show/accept/success funnels. The claim: DevOps plus streaming reduces time to value and increases operational reliability.
AI-written summary · about
chapters (7)
- 0:00The importance of data
- 3:38ING's cultural journey
- 7:48DevOps and engineering culture
- 12:29Continuous analytics model
- 16:54Case study: decision engine
- 20:34Technical architecture
- 26:57Q&A and concluding remarks
related talks
46mFast Data at ING
27mData Analytics Democratization: How ING Data Analytics Platform Bootstraps New...
44mA Tale of Two Clouds: Analytics Platforms at ING
38mTaking away customer friction through streaming analytics
50mData Science in the Enterprise
51mReal Time Investment Alerts using Apache Kafka & Spring Kafka at ING Bank
26mApplying DevOps practices in Data and ML Engineering
51mFrom DevOps for data to DataOps
