GitHub user dosubot[bot] added a comment to the discussion: [Question] Why we use relational/SQL based backend storage in GraphDB?
<!-- Answer --> I'm glad the explanation provided clarity on HugeGraph's approach to storage and its classification as a graph database. Understanding that HugeGraph's design is not strictly tied to relational databases but rather utilizes a binary KV structure for disk storage and a graph structure in memory helps highlight its flexibility and efficiency in handling graph data. This design choice facilitates easier migration for users familiar with relational databases while fully leveraging the advantages of graph databases for complex queries and relationship exploration. If you have any more questions or need further clarification on HugeGraph or graph databases in general, feel free to ask! <!-- Dosu Comment Footer --> <details> <summary> #### About Dosu </summary> This response is meant to be useful and save you time. It is **not meant to be a precise solution**, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. </details> GitHub link: https://github.com/apache/incubator-hugegraph/discussions/2531#discussioncomment-9186377 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
