GitHub user dosubot[bot] added a comment to the discussion: [Question] Why we 
use relational/SQL based backend storage in GraphDB?

<!-- Answer -->
HugeGraph qualifies as a Graph DB through its design and architecture, which 
provide graph database functionalities regardless of the storage backend it 
uses, such as MySQL, RocksDB, Cassandra, or HBase. It's built on the Apache 
TinkerPop3 framework and supports the Gremlin query language, enabling it to 
perform complex graph operations and analyses characteristic of graph databases.

The system's architecture includes a Core Module for the graph engine, a 
Backend Module for physical data storage optimized for graph operations, and an 
API Module for user interaction through RESTful APIs and Gremlin queries. This 
modular design allows HugeGraph to offer graph-oriented computation, data 
abstraction, and a rich set of graph operations, making it suitable for 
applications requiring deep relationship analysis and knowledge graph 
construction.

HugeGraph's designation as a graph database stems from its graph-specific 
operations, optimizations, and support for graph query languages, rather than 
the nature of its storage backend. This approach enables it to leverage the 
robustness, scalability, and persistence capabilities of traditional databases 
while providing the unique advantages of graph databases, such as improved 
search speeds and efficient data relationship exploration.

For more details on HugeGraph's architecture and capabilities, you can refer to 
the architectural guide and introduction in the HugeGraph documentation, as 
well as the source code for insights on how it interacts with backend storage 
systems.


<!-- Dosu Comment Footer -->
<details>
<summary>

#### Details
</summary>

**Sources**
- [[Question] Why we use relational/SQL based backend storage in 
GraphDB?](https://github.com/apache/incubator-hugegraph/issues/2524)
- 
[hugegraph-server/hugegraph-rocksdb/src/main/java/org/apache/hugegraph/backend/store/rocksdb/RocksDBStore.java](https://github.com/apache/incubator-hugegraph/blob/master/hugegraph-server/hugegraph-rocksdb/src/main/java/org/apache/hugegraph/backend/store/rocksdb/RocksDBStore.java)
- 
[content/en/docs/guides/architectural.md](https://github.com/apache/incubator-hugegraph-doc/blob/master/content/en/docs/guides/architectural.md)
- 
[content/en/docs/introduction/README.md](https://github.com/apache/incubator-hugegraph-doc/blob/master/content/en/docs/introduction/README.md)
- 
[content/en/docs/language/hugegraph-gremlin.md](https://github.com/apache/incubator-hugegraph-doc/blob/master/content/en/docs/language/hugegraph-gremlin.md)
- 
[content/cn/docs/language/hugegraph-gremlin.md](https://github.com/apache/incubator-hugegraph-doc/blob/master/content/cn/docs/language/hugegraph-gremlin.md)
- 
[hugegraph-server/hugegraph-core/src/main/java/org/apache/hugegraph/job/algorithm/SubgraphStatAlgorithm.java](https://github.com/apache/incubator-hugegraph/blob/master/hugegraph-server/hugegraph-core/src/main/java/org/apache/hugegraph/job/algorithm/SubgraphStatAlgorithm.java)

<br/>

**About Dosu**
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.
</details>

*To continue the conversation, mention @dosu.*


GitHub link: 
https://github.com/apache/incubator-hugegraph/discussions/2531#discussioncomment-9187112

----
This is an automatically sent email for dev@hugegraph.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@hugegraph.apache.org

Reply via email to