forked from hugegraph/hugegraph-sync
**TODO:** After this PR merged, change the README in commons & pin a [issue](https://github.com/hugegraph/hugegraph-hubble/issues/371) to notify all users/devs to know the context (also update the repo description...) Finally, we may need start a discussion for marking commons repo in achieved status |
||
|---|---|---|
| .. | ||
| hugegraph-api | ||
| hugegraph-cassandra | ||
| hugegraph-core | ||
| hugegraph-dist | ||
| hugegraph-example | ||
| hugegraph-hbase | ||
| hugegraph-hstore | ||
| hugegraph-mysql | ||
| hugegraph-palo | ||
| hugegraph-postgresql | ||
| hugegraph-rocksdb | ||
| hugegraph-scylladb | ||
| hugegraph-test | ||
| Dockerfile | ||
| Dockerfile-hstore | ||
| README.md | ||
| pom.xml | ||
README.md
HugeGraph Server
HugeGraph Server consists of two layers of functionality: the graph engine layer, and the storage layer.
-
Graph Engine Layer:
- REST Server: Provides a RESTful API for querying graph/schema information, supports the Gremlin and Cypher query languages, and offers APIs for service monitoring and operations.
- Graph Engine: Supports both OLTP and OLAP graph computation types, with OLTP implementing the Apache TinkerPop3 framework.
- Backend Interface: Implements the storage of graph data to the backend.
-
Storage Layer:
- Storage Backend: Supports multiple built-in storage backends (RocksDB/MySQL/HBase/...) and allows users to extend custom backends without modifying the existing source code.