Data lake: how Red Hat maintains data quality across multiple Drupal sites
summary
Red Hat moves product and learning content into a managed data lake backed by MongoDB + Search API backend with a custom indexing event subscriber that applies a configurable JSON schema, forbids PII, and enforces governance. A proof‑of‑concept product index runs in Next.js, builds statically and refreshes every 30 minutes from GraphQL (live at access.redhat.com/products), and a PHP MongoDB service plus shared Drupal module delivers reusable content, rendered caching, and incremental migration toward a canonical source.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:07Requirements
- 6:30Data Repository Types
- 7:03Relational database
- 7:25Data warehouse
- 8:02Data Lake Challenges
- 11:49Data Lake Advantages
- 13:23Tech Stack
- 16:33Retrieval
- 20:20Strategy
- 27:29Content Syndicated Patterns
- 32:06Thank you
related talks
08mRed Hat's expansion into data
01h 00mData Mesh: Beyond the Data Lake
02h 05mBig Data and the Data Lake from the Analyst Perspective
17mOpen Data Lakes: Latest stop in the big data journey
15mWhat is a Data Lake, Anyway?
30mFrom Data Lakes to Data Mesh - The Evolution of Redmesh
59mModern data lakes with Lake Formation, Amazon Redshift & AWS Glue
40mUnbundling of the Cloud Data Warehouse: Open Source Databases and Data Lakes