GitHub user BreakMeEveryday added a comment to the discussion: [Question] Why we use relational/SQL based backend storage in GraphDB?
> Simply put, in addition to the content mentioned by @dosu-bot, HugeGraph's > main storage design relies on the **binary KV** structure **in disk** & graph > structure **in memory**, but is compatible with relational databases such as > MySQL, making it easier for ordinary users to understand/migrate to the > graph. (It should be **noted** that HG does not rely on **relational > databases**, which are not equivalent to KV storage) > > From an abstract perspective, the essence of a storage system is to provide > the semantics of `KV/Map`, just like the data structure of a graph is > essentially composed of **array** or **linked-list**. Therefore, building a > graph system based on stable/reliable KV storage is a mainstream/common > approach, and it is also easier to expand to distributed environments Thank you! The "making it easier for ordinary users to understand/migrate to the graph. (It should be **noted** that HG does not rely on **relational databases**" which is part of you sentence answered my question. GitHub link: https://github.com/apache/incubator-hugegraph/discussions/2531#discussioncomment-9186376 ---- This is an automatically sent email for dev@hugegraph.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@hugegraph.apache.org
