Building a data lake at a bank #bbuzz
summary
SolarisBank builds a cloud data lake that ingests via Kinesis → Avro → S3, runs batch analytics with Luigi, and centralizes access and audit trails using infrastructure-as-code and versioned deployments. The system enforces per-customer processing rules through an authorization table, applies pseudonymization and retention windows, and offers a pragmatic deletion option by revoking encryption keys. The pipeline is live and reduces ad hoc DB access, but GDPR edge cases and anonymization limits still require legal policy and occasional recomputation.
AI-written summary · about
chapters (5)
- 0:00Introduction to data lake
- 3:56Why build a data lake
- 10:40GDPR challenges in banking
- 20:11Data minimization and deletion
- 25:50Compliance and conclusion
related talks
41mRole of Private Data Lake for Sustainable Business Growth
49mBuilding a Data-Driven Bank
43mManaging a Data Lake on AWS
30mRaw Data to Business Insights: What You Need to Build a Modern Data Lake
28mBuilding A Governed Data Lake
27mInnovation through self-service data products
01h 03mReinvente su estrategia de datos con Lagos de Datos Transaccionales
34mData Lakehouse: Who, Why and How