How an anonymized USD 100B+ regional bank in Southeast Asia moved from batch-driven risk visibility to near real-time monitoring while protecting core banking stability.
Case Snapshot
| Field | Detail |
|---|---|
| Industry | Financial Services |
| Region | Southeast Asia |
| Customer profile | Regional bank with USD 100B+ in assets and 1,000+ branches |
| Use case | Real-time risk management |
| Source system | Oracle 19c core banking database |
| Target environment | Risk data warehouse in a controlled country-specific environment |
| Deployment model | On-premises Deltaplex deployment |
| Daily scale | Approximately 50 million transactions and 2TB of data processed daily |
Executive Summary
A leading regional bank in Southeast Asia needed to modernize the data foundation behind its risk management operations. Its core banking environment supported millions of daily transactions, but downstream risk systems still depended on scheduled batch ETL. As a result, transaction and account data often arrived 4-6 hours after business events occurred.
That latency limited the bank's ability to monitor suspicious activity, respond to risk events, and support regulatory expectations for timely oversight. Increasing batch frequency created more operational pressure, but did not solve the underlying architectural issue.
The bank deployed Deltaplex as an on-premises, log-based Change Data Capture (CDC) layer between its Oracle core banking system and downstream risk data warehouse. Instead of repeatedly querying production tables, Deltaplex captured committed changes from database transaction logs and delivered them continuously to risk systems.
The result was a production-grade real-time risk data foundation with less than 5 seconds of end-to-end latency, no additional query workload on the core banking database, stronger audit visibility, and a reusable architecture for future risk, compliance, and analytics use cases.
Results at a Glance
| Area | Before Deltaplex | After Deltaplex |
|---|---|---|
| Data latency | 4-6 hours | Less than 5 seconds |
| Data movement model | Scheduled batch ETL | Continuous log-based CDC |
| Source system impact | Periodic extraction load | No additional query workload on production tables |
| Fraud response | Dependent on batch refresh cycles | Reported 40% faster response time |
| Compliance visibility | Fragmented logs and manual tracing | Centralized pipeline monitoring and audit trail |
| Deployment model | Legacy ETL infrastructure | On-premises Deltaplex platform |
The Challenge: Risk Systems Were Waiting on Stale Data
The bank's risk management systems depended on transaction and account data from its core banking environment. The data was extracted through scheduled ETL jobs and delivered to downstream systems several times per day.
For historical reporting, this architecture had been acceptable. For modern risk management, it was no longer enough. Fraud patterns, suspicious transfers, abnormal account activity, and compliance-sensitive transactions can develop quickly. With a 4-6 hour data delay, risk teams were often making decisions with stale context.
The bank faced four major constraints.
1. Batch ETL created unacceptable latency
The existing pipelines ran on fixed schedules. Even when the team increased batch frequency, the architecture still could not provide true real-time visibility. More frequent extraction also introduced more job dependencies, more source-system pressure, and more failure points.
2. Regulatory expectations were increasing
Across the region, financial institutions were under growing pressure to improve risk detection, auditability, and data governance. The bank needed a data architecture that could support faster monitoring while preserving traceability across the data lifecycle.
3. Data sovereignty requirements limited cloud-only options
Sensitive banking data could not freely move into unmanaged third-party environments. The bank needed a deployment model that kept data inside approved infrastructure and jurisdictional boundaries while still supporting real-time processing.
4. Core banking performance could not be compromised
The core banking system was mission-critical. Any modernization project had to avoid additional query load, downtime, or operational instability. Real-time data movement was required, but not at the expense of production system safety.
The Solution: Log-Based CDC for Real-Time Risk Data
The bank deployed Deltaplex as the real-time data integration layer between its Oracle core banking system and risk data warehouse.
Instead of repeatedly scanning production tables, Deltaplex captured committed changes from Oracle transaction logs. This allowed the bank to stream transaction changes continuously while avoiding intrusive extraction workloads on the core banking system.
The solution was designed around four principles.
Low-impact capture
Deltaplex used log-based CDC to capture committed database changes without running heavy queries against production tables.
Continuous delivery
Transaction and account updates flowed continuously into the bank's risk data warehouse, enabling near real-time monitoring and downstream analysis.
Controlled deployment
Deltaplex was deployed on-premises inside the bank's controlled environment, supporting internal governance requirements and data sovereignty controls.
Production resilience
The pipeline was configured for high availability, monitored latency, alerting, and operational recovery so that risk data delivery could be managed as critical infrastructure.
Technical Architecture
The production architecture connected the bank's Oracle-based core banking system with its downstream risk data warehouse.
Oracle 19c Core Banking System
↓
Deltaplex Log-Based CDC
↓
Schema Evolution and Pipeline Monitoring
↓
Risk Data Warehouse
↓
Fraud Detection, Risk Monitoring, Compliance Reporting
Architecture profile
| Component | Description |
|---|---|
| Source system | Oracle 19c core banking database |
| Target system | Risk data warehouse in a controlled country-specific environment |
| Data volume | Approximately 50 million transactions and 2TB processed daily |
| Availability design | High-availability production deployment |
| Deployment model | On-premises Deltaplex platform |
| Governance model | Role-based access, audit trail, pipeline monitoring |
This architecture allowed the bank to deliver fresh transaction data to risk systems while isolating the core banking workload from heavy extraction processes.
Implementation: From Pilot to Production in 12 Weeks
The implementation took 12 weeks from kickoff to production. The joint project team included two Deltaplex engineers and three bank engineers across architecture design, pipeline configuration, validation, and production rollout.
Phase 1: Pilot - 2 weeks
The first phase validated the CDC approach against selected Oracle 19c tables from the core banking system.
The pilot tested:
- Log-based change capture
- End-to-end latency
- Data consistency between source and target
- Source-system performance impact
- Recovery behavior during controlled failure scenarios
The pilot confirmed that Deltaplex could deliver transaction changes in seconds without adding measurable workload to the core banking database.
Phase 2: Rollout - 8 weeks
After the pilot, the team expanded the pipeline to cover the bank's risk management data scope.
During this phase, the team configured:
- CDC pipelines from Oracle 19c
- Target delivery to the risk data warehouse
- Schema evolution handling for frequent core system updates
- Monitoring dashboards for pipeline health and latency
- Alerting rules for operational incidents
- Role-based access controls for data operations
Because the core banking system changed frequently, schema evolution was a key requirement. Deltaplex was configured to detect schema changes, classify their impact, and apply predefined handling policies.
Low-risk changes, such as adding nullable columns, could be synchronized automatically. Higher-risk changes, such as type changes or key-related changes, triggered alerts and review before downstream application.
Phase 3: Optimization - 2 weeks
The final phase focused on performance tuning, high-availability validation, and operational handover.
The team optimized:
- Replication throughput
- End-to-end latency
- Failover behavior
- Monitoring thresholds
- Recovery procedures
- Runbooks for the bank's data engineering team
By the end of the implementation, the bank had a production-ready real-time data pipeline supporting critical risk management workloads.
Results: Real-Time Risk Visibility with Production Control
After go-live, the bank reduced risk data latency from 4-6 hours to less than 5 seconds.
This created immediate operational value. Risk teams could monitor transaction activity with near real-time visibility, while fraud detection systems received fresher signals for faster decisions.
Faster risk detection
Risk systems no longer had to wait for scheduled batch jobs. New transaction data became available almost immediately after being committed in the core banking system.
Lower production risk
Because Deltaplex captured changes from transaction logs, the bank avoided heavy extraction queries against the core banking database. This helped protect production performance and stability.
Stronger compliance support
The deployment supported data sovereignty requirements by keeping sensitive data within approved infrastructure. Pipeline monitoring and audit trails also improved traceability for internal governance and regulatory review.
Reduced infrastructure complexity
The bank retired four legacy batch ETL jobs, reducing operational overhead and simplifying the data movement architecture.
Better operational resilience
With high availability, alerting, and built-in monitoring, the data engineering team gained stronger control over pipeline health, latency, and recovery.
Customer Perspective
"Deltaplex gave us real-time visibility without adding workload to our core banking system. That was the game-changer."
- Head of Data Engineering, Regional Bank in Southeast Asia
Why the Bank Chose Deltaplex
The bank selected Deltaplex because it could meet three requirements at the same time: real-time performance, production system safety, and enterprise-grade governance.
For financial institutions, these requirements are often difficult to balance. Real-time data movement can create risk if it increases load on core systems. Cloud-only platforms may create data sovereignty concerns. Custom-built pipelines can work in the short term but are expensive to maintain at scale.
Deltaplex provided a controlled path:
- Log-based CDC enabled real-time data delivery without repeated production queries.
- On-premises deployment kept sensitive banking data inside approved infrastructure.
- Schema evolution handling helped reduce pipeline breakage during source system changes.
- Monitoring and auditability made the pipeline easier to operate as production infrastructure.
- High availability supported critical risk management workloads.
Conclusion
For the regional bank, real-time risk management was not just a data engineering upgrade. It became a business-critical capability.
By replacing batch ETL with Deltaplex CDC, the bank moved from delayed risk visibility to near real-time monitoring. It reduced latency from hours to seconds, improved fraud response, strengthened compliance support, and protected the stability of its core banking system.
The project also created a reusable real-time data foundation for future use cases across fraud detection, compliance reporting, customer analytics, and operational intelligence.
For financial institutions operating in highly regulated environments, the lesson is clear: real-time data does not have to mean higher production risk. With the right architecture, banks can move faster, stay governed, and keep mission-critical systems safe.
Ready to modernize risk data without disrupting core systems?
Deltaplex helps financial institutions build real-time data pipelines with log-based CDC, on-premises deployment, schema evolution handling, and production-grade observability.