When should you NOT use a skip list instead of a balanced tree?
Use a tree if you need strict O(log n) worst-case guarantees and can afford the complexity. Use a tree if you need parent pointers for range deletions or efficient reverse traversal. Skip lists win when you prioritize simplicity, concurrent inserts, or range scans (you just walk the base level). Most databases choose skip lists for in-memory work (transient, high churn); trees for persistent storage (predictable latency, stability).
Answered in
Skip Lists: The Shortcut Nobody RotatesBalanced trees rebalance with rotations. Skip lists layer express lanes with random promotion—same O(log n) search, simpler locking.
Read the full analysisOther questions this article answers
More system design questions
- Why doesn't Google just run Dijkstra faster?
- What is a shortcut edge and when is it precomputed?
- How much space do shortcut edges take compared to the original graph?
- Can Contraction Hierarchies handle dynamic graphs like traffic or road closure?
- Why contract low-degree nodes first instead of high-degree ones?
- What is a CRDT and why does it matter for real-time collaboration?
- How do CRDTs handle concurrent edits without a central server referee?
- Why did Figma move from operational transforms to CRDTs?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design beat.