**Introduction:**

A red-black tree is a kind of self-balancing binary search tree where each node has an extra bit, and that bit is often interpreted as the colour (red or black). These colours are used to ensure that the tree remains balanced during insertions and deletions. Although the balance of the tree is not perfect, it is good enough to reduce the searching time and maintain it around O(log n) time, where n is the total number of elements in the tree. This tree was invented in 1972 by Rudolf Bayer.

It must be noted that as each node requires only 1 bit of space to store the colour information, these types of trees show identical memory footprint to the classic (uncoloured) binary search tree.

**Rules That Every Red-Black Tree Follows:**

- Every node has a colour either red or black.
- The root of tree is always black.
- There are no two adjacent red nodes (A red node cannot have a red parent or red child).
- Every path from a node (including root) to any of its descendant NULL node has the same number of black nodes.

**Why Red-Black Trees?**

Most of the BST operations (e.g., search, max, min, insert, delete.. etc) take O(h) time where h is the height of the BST. The cost of these operations may become O(n) for a skewed Binary tree. If we make sure that the height of the tree remains O(log n) after every insertion and deletion, then we can guarantee an upper bound of O(log n) for all these operations. The height of a Red-Black tree is always O(log n) where n is the number of nodes in the tree.

Sr. No. | Algorithm | Time Complexity |
---|---|---|

1. | Search | O(log n) |

2. | Insert | O(log n) |

3. | Delete | O(log n) |

**“n” is the total number of elements in the red-black tree.**

**Comparison with**** AVL Tree**:

The AVL trees are more balanced compared to Red-Black Trees, but they may cause more rotations during insertion and deletion. So if your application involves frequent insertions and deletions, then Red-Black trees should be preferred. And if the insertions and deletions are less frequent and search is a more frequent operation, then AVL tree should be preferred over Red-Black Tree.

**How does a Red-Black Tree ensure balance?**

A simple example to understand balancing is, a chain of 3 nodes is not possible in the Red-Black tree. We can try any combination of colours and see all of them violate Red-Black tree property.

A chain of 3 nodes is nodes is not possible in Red-Black Trees. Following areNOTRed-Black Trees303030/ \ / \ / \20NIL20NIL20NIL / \ / \ / \10NIL10NIL10NIL Violates Violates Violates Property 4. Property 4 Property 3 Following are different possible Red-Black Trees with above 3 keys2020/ \ / \10 3010 30/ \ / \ / \ / \ NIL NIL NIL NIL NIL NIL NIL NIL

**Interesting points about Red-Black Tree:**

- Black height of the red-black tree is the number of black nodes on a path from the root node to a leaf node. Leaf nodes are also counted as black nodes. So, a red-black tree of height h has black height >= h/2.
- Height of a red-black tree with n nodes is h<= 2 log
_{2}(n + 1). - All leaves (NIL) are black.
- The black depth of a node is defined as the number of black nodes from the root to that node i.e the number of black ancestors.
- Every red-black tree is a special case of a binary tree.

**Black Height of a Red-Black Tree :**

Black height is the number of black nodes on a path from the root to a leaf. Leaf nodes are also counted black nodes. From the above properties 3 and 4, we can derive, **a Red-Black Tree of height h has black-height >= h/2**.

Number of nodes from a node to its farthest descendant leaf is no more than twice as the number of nodes to the nearest descendant leaf.

**Every Red Black Tree with n nodes has height <= **2Log_{2}(n+1)

This can be proved using the following facts:

- For a general Binary Tree, let
**k**be the minimum number of nodes on all root to NULL paths, then n >= 2^{k}– 1 (Ex. If k is 3, then n is at least 7). This expression can also be written as k <= Log_{2}(n+1). - From property 4 of Red-Black trees and above claim, we can say in a Red-Black Tree with n nodes, there is a root to leaf path with at-most Log
_{2}(n+1) black nodes. - From property 3 of Red-Black trees, we can claim that the number of black nodes in a Red-Black tree is at least ⌊ n/2 ⌋ where n is the total number of nodes.

From the above points, we can conclude the fact that Red Black Tree with **n** nodes has height <= 2Log_{2}(n+1)

**Search Operation in Red-black Tree:**

As every red-black tree is a special case of a binary tree so the searching algorithm of a red-black tree is similar to that of a binary tree.

**Algorithm:**

searchElement (tree, val)Step 1:If tree -> data = val OR tree = NULL Return tree Else If val data Return searchElement (tree -> left, val) Else Return searchElement (tree -> right, val) [ End of if ] [ End of if ]Step 2:END

For the program, you can refer it for **AVL tree**.

**Example: Searching 11 in the following red-black tree.**

**Solution:**

- Start from the root.
- Compare the inserting element with root, if less than root, then recurse for left, else recurse for right.
- If the element to search is found anywhere, return true, else return false.

In this post, we introduced Red-Black trees and discussed how balance is ensured. The hard part is to maintain balance when keys are added and removed. We have also seen how to search an element from the red-black tree. We will soon be discussing insertion and deletion operations in coming posts on the Red-Black tree.

**Exercise:**

**1)** Is it possible to have all black nodes in a Red-Black tree? **2) **Draw a Red-Black Tree that is not an AVL tree structure-wise?

**Insertion and Deletion**

Red-Black Tree Insertion

Red-Black Tree Deletion

**Applications: **

- Most of the self-balancing BST library functions like map and set in C++ (OR TreeSet and TreeMap in Java) use Red-Black Tree.
- It is used to implement CPU Scheduling Linux. Completely Fair Scheduler uses it.
- Besides they are used in the K-mean clustering algorithm for reducing time complexity.
- Moreover, MySQL also uses the Red-Black tree for indexes on tables.

**References:**

- Introduction to Algorithms 3rd Edition by Clifford Stein, Thomas H. Cormen, Charles E. Leiserson, Ronald L. Rivest
- http://en.wikipedia.org/wiki/Red%E2%80%93black_tree
- Video Lecture on Red-Black Tree by Tim Roughgarden
- MIT Video Lecture on Red-Black Tree
- MIT Lecture Notes on Red-Black Tree

## Recommended Posts:

- Gomory-Hu Tree | Set 1 (Introduction)
- Persistent Segment Tree | Set 1 (Introduction)
- ScapeGoat Tree | Set 1 (Introduction and Insertion)
- Palindromic Tree | Introduction & Implementation
- BK-Tree | Introduction & Implementation
- Introduction to R-tree
- Decision Tree Introduction with example
- Introduction of B-Tree
- Overview of Data Structures | Set 3 (Graph, Trie, Segment Tree and Suffix Tree)
- Skip List | Set 1 (Introduction)
- Self Organizing List | Set 1 (Introduction)
- Suffix Array | Set 1 (Introduction)
- Fibonacci Heap | Set 1 (Introduction)
- Heavy Light Decomposition | Set 1 (Introduction)
- proto van Emde Boas Trees | Set 1 (Background and Introduction)
- Unrolled Linked List | Set 1 (Introduction)
- AA Trees | Set 1 (Introduction)
- Persistent Trie | Set 1 (Introduction)
- Tournament Tree (Winner Tree) and Binary Heap
- Check if a given Binary Tree is height balanced like a Red-Black Tree