Suffix tree and Tries. What is the difference?

AlgorithmData StructuresTrieSuffix Tree

Algorithm Problem Overview


I am reading about Tries commonly known as Prefix trees and Suffix Trees.
Although I have found code for a Trie I can not find an example for a Suffix Tree. Also I get the feeling that the code that builds a Trie is the same as the one for a Suffix Tree with the only difference that in the former case we store prefixes but in the latter suffixes.
Is this true? Can anyone help me clear this out in my head? An example code would be great help!

Algorithm Solutions


Solution 1 - Algorithm

A suffix tree can be viewed as a data structure built on top of a trie where, instead of just adding the string itself into the trie, you would also add every possible suffix of that string. As an example, if you wanted to index the string banana in a suffix tree, you would build a trie with the following strings:

banana
anana
nana
ana
na
a

Once that's done you can search for any n-gram and see if it is present in your indexed string. In other words, the n-gram search is a prefix search of all possible suffixes of your string.

This is the simplest and slowest way to build a suffix tree. It turns out that there are many fancier variants on this data structure that improve on either or both space and build time. I'm not well versed enough in this domain to give an overview but you can start by looking into suffix arrays or this class advanced data structures (lecture 16 and 18).

This answer also does a wonderfull job explaining a variant of this data-structure.

Solution 2 - Algorithm

If you imagine a Trie in which you put some word's suffixes, you would be able to query it for the string's substrings very easily. This is the main idea behind suffix tree, it's basically a "suffix trie".

But using this naive approach, constructing this tree for a string of size n would be O(n^2) and take a lot of memory.

Since all the entries of this tree are suffixes of the same string, they share a lot of information, so there are optimized algorithms that allows you to create them more efficiently. Ukkonen's algorithm, for example, allows you to create a suffix tree online in O(n) time complexity.

Solution 3 - Algorithm

The difference is very simple. A suffix tree has less "dummy" nodes than the suffix trie. These dummy nodes are single characters that increase the lookup operation at the tree

Solution 4 - Algorithm

Trie's nodes have links to shorter context, 'Tree' does not have it. If Tree's nodes get link to shorter context then it turns to Trie ;o)

Solution 5 - Algorithm

A Suffix Tree for a given text is a compressed trie for all suffixes of the given text.

Ref: https://www.geeksforgeeks.org/pattern-searching-using-suffix-tree/

Solution 6 - Algorithm

I'll give you snippets to make your understanding clearer. Disclaimer: I'm not an expert and know these DS from coding interview preparations.

At first, as was said above: suffix trie is a structure made up of hash tables (simplest variant) where we store all possible variants. So, we can search substrings if needed. Ex: 'abc'.

{'a': True, 
  'a': {'b': True},
  'a': {'b': {'c': True}}, 
  'b': True,
  'b': {'c': True},
  'c': True}

And Trie is when we store full strings to check if they're present. Ex: {'t': {'h': {'i': {'s': {'*': 'this'}}}}, 'y': {'o': {'*': 'yo'}}

You can check for further explanation question on Leetcode: Implement Trie (Prefix Tree). Link: https://leetcode.com/problems/implement-trie-prefix-tree/

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionCratylusView Question on Stackoverflow
Solution 1 - AlgorithmZe BlobView Answer on Stackoverflow
Solution 2 - AlgorithmJuan LopesView Answer on Stackoverflow
Solution 3 - AlgorithmcuriousView Answer on Stackoverflow
Solution 4 - AlgorithmStephan BanevView Answer on Stackoverflow
Solution 5 - AlgorithmLiquidpieView Answer on Stackoverflow
Solution 6 - AlgorithmSleeplessChallengerView Answer on Stackoverflow