<p>Binary search trees (BST) are not totally equivalent to the proposed data structure. Their asymptotic complexity is better when it comes to both insert and remove sorted values dynamically (assuming they are balanced correctly). For example, when you when to build an index of the top-k values dynamically:</p>
<pre><code>while end_of_stream(stream):
    value &lt;- stream.pop_value()
    tree.insert(value)
    tree.remove_max()
</code></pre>
<p>Sorted arrays are not efficient in this case because of the linear-time insertion. The complexity of bucketed lists is not better than plain list asymptotically and also suffer from a linear-time search. One can note that a heap can be used in this case, and in fact it is probably better to use a heap here, although they are not always interchangeable.</p>
<p>That being said, your are right : BST are slow, cause a lot of cache miss and fragmentation, etc. Thus, they are often replaced by more compact variants like <a href="https://en.wikipedia.org/wiki/B-tree" rel="nofollow noreferrer"><strong>B-trees</strong></a>. B-tree uses a sorted array index to reduce the amount of node jumps and make the data-structure much more compact. They can be mixed with some 4-byte pointer optimizations to make them even more compact. B-trees are to BST what bucketed linked-lists are to plain linked-lists. B-trees are very good for building dynamic database index of huge datasets stored on a slow storage device (because of the size): they enable applications to fetch values associated to a key using very <em>few storage-device lookups</em> (which as very slow on HDD for example). Another example of real-world use-case is interval-trees.</p>
<p>Note that memory fragmentation can be reduced using compaction methods. For BSTs/B-trees, one can reorder the root nodes like in a heap. However, compaction is not always easy to apply, especially on native languages with pointers like in C/C++ although some <a href="https://arxiv.org/pdf/1902.04738.pdf" rel="nofollow noreferrer">very clever methods exists</a> to do so.</p>
<p>Keep in mind that B-trees shine only on big datasets (especially the ones that do not fit in cache). On relatively small ones, using just plain arrays or even sorted array is often a very good solution.</p>
Are there real-world reasons to employ a Binary Search Tree over a Binary Search of semi-contiguous list?
<p>I'm watching university lectures on algorithms and it seems so many of them rely almost entirely binary search trees of some particular sort for querying/database/search tasks.</p>
<p>I don't understand this obsession with <em>Binary Search <strong>Trees</strong></em>. It seems like in the <strong>vast</strong> majority of scenarios, a BSP could be replaced with a sorted array in the case of a static data, or a sorted bucketed list if insertions occur dynamically, and then a <em>Binary Search</em> could be employed over them.</p>
<p>With this approach, you get the same algorithmic complexity (for querying at least) as a BST, <strong>way</strong> better cache coherency, way less memory fragmentation (and less gc allocs depending on what language you're in), and are likely much simpler to write.</p>
<p>The fundamental issue is that BSP are completely memory naïve -- their focus is <strong>entirely</strong> on O(n) complexity and they ignore the very real performance considerations of memory fragmentation and cache coherency... Am I missing something?</p>