B+-trees (a variant of B-trees) are useful to know since relational DB indexes are often implemented using them.
A B-tree is a self-balancing tree that maintains sorted data and allows searches, insertions, and deletions in logarithmic time.
B-trees are designed to work well when stored on secondary storage, like HDD. The size of a node is normally the same size as the system block/page size.
Typical b-tree operations are:
|operation||description||time complexity (worst case)|
| ||Inserts key to tree.|
| ||Deletes key from the tree (assuming no duplicates).|
| ||Return value for key if it exists in tree.|
Note: to simplify the discussion, these notes assume that satellite data associated with the key resides in the same node as the key.
- Each node has the following attributes:
- keys stored in node .
- keys stored in non-decreasing order.
- Each internal node contains pointers to its children.
- The keys separate the ranges of keys stored in each subtree. If is any key stored in the subtree with root then: .
- All leaves have the same depth.
- The minimum degree () of a tree is used to define the minimum number of keys that can exist in a non-root node:
- t >= 2
- Non-root nodes must contain at least keys (meaning that an internal node has at least children.
- Non-root nodes can contain at most keys (meaning that an internal node has at most 2t children). A node is full if it contains keys.
Find requires traversing each level of the tree until the key is found. It’s similar to binary search algorithm except there is a range search used to identify the correct child to visit.
Insertion involves searching for the new leaf position and inserting the new key in sorted order. In the case that the leaf node is full, the node must be split.
Splitting involves creating two nodes from the full node ’s keys, split around the ’s median key to have keys each. The median node is moved to ’s parent to identify the dividing point between the two new trees [1, P. 493].
To avoid recursively splitting nodes up to thee root, you can preemptively split full nodes while traversing the tree [1, P. 493] .
There are two popular B-tree deletion strategies:
- Locate and delete the item (à la
find()), then restructure the tree to retain its invariants.
- Do a single pass down the tree, but before visiting a node restructure the tree so that once the key to be deleted is encountered, it can be deleted without triggering the need for any further restructuring.
Maintaining the B-tree invariants when deleting involves moving keys from sibling nodes that have , or in the case that no immediate siblings have , merging two nodes.
B+-trees are a variant of B-trees commonly used in DBs to implement indexes (where they are often referred to as btrees).
B+-trees store all satellite information in the leaves and only stores keys and child pointers in the internal nodes [1, P. 488].
-  T. H. Cormen, C. E. Leiserson, R. L. Rivest, and C. Stein, Introduction to Algorithms, 3rd ed. The MIT Press, 2009.