Big Data 17 min read

How Flink Powers Real‑Time Process Operations in China Construction Bank

This article details how China Construction Bank's fintech subsidiary leveraged Apache Flink to ingest, join, and analyze massive front‑end, request, and response logs in real time, overcoming data silos, latency challenges, and state‑management issues to enable end‑to‑end process visibility and operational optimization.

Alibaba Cloud Developer
Alibaba Cloud Developer
Alibaba Cloud Developer
How Flink Powers Real‑Time Process Operations in China Construction Bank

Company Introduction

Jianxin FinTech is the fintech subsidiary of China Construction Bank, transformed from the bank's software development center, dedicated to driving the “new finance” ecosystem and supporting the digital transformation of the bank and digital China.

Company Introduction
Company Introduction

Business Background and Challenges

Modern applications use front‑back separation; each transaction in the bank generates three messages: front‑end trace, HTTP request, HTTP response. Hundreds of scenarios (cash delivery, credit‑card approval, etc.) produce massive, fragmented data that is isolated across systems, making unified analysis difficult.

The goal is to ingest all logs, reconstruct business processes from a business‑centric view, and provide real‑time analytics for various roles (customers, staff, managers).

Data Flow Architecture
Data Flow Architecture

Solution Evolution and Technical Challenges

Three‑stage evolution:

Version 1.0 – sliding‑window join with Redis for state; low throughput, Redis pressure.

Version 2.0 – Flink interval‑join using RocksDB; OOM and large checkpoint size.

Version 3.0 – custom keyedProcessFunction with manual state management, reducing state by 90 % and improving stability.

Key challenges include multi‑source data, high latency tolerance (up to one hour), massive data volume (hundreds of billions per day), and the need for a one‑to‑one join of request, response, and trace.

State Management Evolution
State Management Evolution

Process Indicators

Two iterations of real‑time metrics:

1.0 – hybrid Flink‑Spark pipeline with minute‑level latency, data flow: Kafka → Flink → Kafka → Spark → GP → Oracle.

2.0 – pure Flink pipeline writing directly to Oracle, achieving second‑level latency.

Metrics cover channel, product, and institution dimensions, such as approval rates, activation rates, and average processing times.

Real‑time Metrics Architecture
Real‑time Metrics Architecture

Business Impact

Real‑time process reconstruction enables end‑to‑end visibility, risk intervention, resource optimization, and supports the bank’s digital transformation.

Process Visualization
Process Visualization

Future Outlook

The solution will be productized and extended to other industries, bringing financial‑grade process operations beyond the bank.

Future Vision
Future Vision
Flinkbankingprocess mining
Alibaba Cloud Developer
Written by

Alibaba Cloud Developer

Alibaba's official tech channel, featuring all of its technology innovations.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.