Theme
One governed data layer for streaming and analytics — Iceberg-native real-time with engines that span streams and tables.
Why this track matters
The Streaming-Augmented Lakehouse (SAL) is becoming the default blueprint: append-only streams landing in open tables, compaction for curated layers, and query engines that serve both interactive analytics and ML/AI. This track shows how OpenAI, Dremio, Onehouse/Hudi, Doris, and StreamNative/Ursa make it real — including governance with Unity Catalog.
What you’ll learn
- Designing SAL architectures: bronze append-only vs. compacted silver/gold and when to choose each.
- Ingestion & concurrency at scale: non-blocking writers, CDC, and streaming compaction.
- Governance & catalogs: Iceberg with Unity Catalog and cross-engine access patterns.
- Engine choices: where Ursa, Flink, Dremio, Doris, and Hudi fit in end-to-end pipelines.
Highlights
- Dremio — Streaming with Apache Iceberg
- Motorq - Real-Time Lakehouse Ingestion with StreamNative’s Classic Engine and Ursa
- Apache Doris (VeloDB) — Unlocking Real-Time Insights: Apache Doris in Stream and Lakehouse Integration
- OpenAI — StreamLink: Real-Time Data Ingestion at OpenAI Scale
- Onehouse/Hudi — High-Throughput Streaming in the Lakehouse with Non-Blocking Concurrency Control in Apache Flink & Hudi
- Uber + Onehouse —Flink Streaming Ingestion to Cloud-Lake at Scale
- Kentra — Schema Management and Streaming Data Products
Who should attend
Data platform teams standardizing on Iceberg or Delta Lake, analytics leaders, and architects bridging batch + stream under one governance model.
Join us
Register for DSS SF 2025 (Sept 30) and bring your lakehouse questions. We look forward to seeing you there!
