B-tree / B+ tree
The shape of a database index.
Designed at Boeing Scientific Research Labs to keep an index page-resident on disk. The "B" stands for nothing definitive: Bayer, balanced, Boeing, broad. Bayer himself never said. Every relational database since uses a B+tree variant. SQLite's author Richard Hipp once said: "B-trees are the only data structure that matters."
Each node holds many keys (typically 100–500), all leaves at the same depth. The fan-out keeps the tree shallow — billions of records in just 4 levels. B+trees push all data to leaves and link them, so range scans are sequential disk reads.
PostgreSQL, MySQL InnoDB, SQLite, Oracle, SQL Server, every B-tree-based KV store. Filesystems: ext4 HTree, NTFS, HFS+, BTRFS, ReFS, ZFS.
When your index doesn't fit in RAM, only B-trees stay sane. A 100-million-row index is 20 levels deep in a binary tree; 4 levels in a B+tree with fanout 200. That's the difference between 20 disk seeks and 4.