Session
The Bank Crash Chronicles: Why Our 11TB Oracle Exadata Architecture Failed
When dealing with 11TB of data and 10 billion records, the "standard" ways of ensuring data integrity begin to fail. Conventional read-side duplicate checks can become a bottleneck that can paralyse a system, especially under the scrutiny of financial regulators such as BaFin.
This session moves beyond the theory of database constraints and provides a battle-tested blueprint for managing massive data volumes in highly compliant environments. We will explore the architectural shift from read-side validation to a Write-Side Integrity Strategy, detailing the logic, the specific Spring-based implementation, and the performance gains realised.
Furthermore, we will break down the ongoing "Exit Strategy" from legacy Oracle Exadata to Cloud PostgreSQL. We will share best practices for a Zero-Loss Migration, ensuring 100% data integrity is maintained as we move billions of records under extreme time and regulatory pressure.
Martin Ladecký
tech lead in Commerzbank, exCTO Loono, Czech JUG organiser
Prague, Czechia
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top