Answers are grounded in this paper and cite their sources.
Financial institutions have long operated between two inadequate extremes: the data warehouse, which offers governance and reliability but resists the scale and flexibility that modern analytics demand, and the data lake, which provides flexibility at the cost of structure, trust, and regulatory traceability. The Lakehouse paradigm resolves this tension by layering transactional semantics, metadata management, and open storage formats directly onto cloud object storage. This paper proposes a six-layer Lakehouse reference architecture for financial systems, grounded in the Banking Industry Architecture Network (BIAN) Service Landscape 12.0 service-domain model. Each layer is mapped to the service domains that own its data products, which gives the platform a clear line of accountability. The architecture addresses ingestion and source integration, open table storage using the medallion pattern, governance and compliance, analytical and risk serving, real-time streaming integration, and data product delivery. A structured comparison of Delta Lake, Apache Iceberg, and Apache Hudi across financial workload profiles (batch regulatory reporting, real-time risk scoring, and ML model training) guides open table format selection decisions. Design tensions between real-time processing latency and regulatory auditability are analysed, together with a federated governance model that reconciles domain ownership of data with the enterprise-wide lineage that BCBS 239 requires, and a phased implementation roadmap is provided. The framework provides data architects and platform engineers with a structured foundation for building unified financial data platforms that satisfy BCBS 239, GDPR, SOX, and EU AI Act obligations while delivering the analytical throughput and ML serving capabilities that modern risk management demands.
No takes yet. Share an insight, caveat, or question.
Sarkar et al. (2026) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: