Topic
query-engine
10 posts tagged “query-engine”.
-
Concurrency, Isolation, and MVCC: How Engines Handle Contention
This is Part 10 of a 10-part series on query engine design. Part 9 covered distributed joins. This final article covers how engines handle the…
-
Hash, Sort-Merge, Broadcast: How Distributed Joins Work
This is Part 9 of a 10-part series on query engine design. Part 8 covered partitioning. This article covers the most expensive operation in…
-
Partitioning, Sharding, and Data Distribution Strategies
This is Part 8 of a 10-part series on query engine design. Part 7 covered memory management. This article covers how engines divide data across…
-
Buffer Pools, Caches, and the Memory Hierarchy
This is Part 7 of a 10-part series on query engine design. Part 6 covered execution models. This article covers how engines manage their most…
-
Volcano, Vectorized, Compiled: How Engines Execute Your Query
This is Part 6 of a 10-part series on query engine design. Part 5 covered how optimizers pick a plan. This article covers what happens next: how the…
-
Inside the Query Optimizer: How Engines Pick a Plan
This is Part 5 of a 10-part series on query engine design. Part 4 covered indexing strategies. This article covers what happens after the engine…
-
B-Trees, LSM Trees, and the Indexing Tradeoff Spectrum
This is Part 4 of a 10-part series on query engine design. Part 3 covered how data is structured within files. This article covers the auxiliary data…
-
How Databases Organize Data on Disk: Pages, Blocks, and File Formats
This is Part 3 of a 10-part series on query engine design. Part 2 covered row vs. column storage layouts. This article goes one level deeper: how…
-
Row vs. Column: How Storage Layout Shapes Everything
This is Part 2 of a 10-part series on query engine design. Part 1 (Overview) introduced the nine decisions every engine must make. This article…
-
How Query Engines Think: The Tradeoffs Behind Every Data System
Every database you have ever used is a collection of deliberate engineering tradeoffs. PostgreSQL is fast at looking up a single customer record but…