About This Event
Alex Monahan goes inside DuckLake's architecture: how the catalog, storage, and compute layers are designed, why separating them is deliberate, and what it means for reads, writes, and query planning. Based on Chapter 3 of DuckLake: The Definitive Guide.
What You'll Learn
- How DuckLake's catalog, storage, and compute layers are designed
- Why DuckLake separates these layers by design rather than as an implementation detail
- How that architecture shapes DuckLake's handling of reads, writes, and query planning
Who Should Attend
This event is ideal for:
Data EngineersData ArchitectsTechnical Leaders
