forked from hugegraph/hugegraph-sync
* remove zgc * Apply suggestions from code review * add comment for hugegraph-server.sh * fix enable-auth.sh * init store in entrypoint * use flag file to skip re-init * delete tar.gz * simply dockerfile * mvn optimize * simply dockerfile * add init log in docker --------- Co-authored-by: imbajin <jin@apache.org> |
||
|---|---|---|
| .. | ||
| hugegraph-api | ||
| hugegraph-cassandra | ||
| hugegraph-core | ||
| hugegraph-dist | ||
| hugegraph-example | ||
| hugegraph-hbase | ||
| hugegraph-mysql | ||
| hugegraph-palo | ||
| hugegraph-postgresql | ||
| hugegraph-rocksdb | ||
| hugegraph-scylladb | ||
| hugegraph-test | ||
| Dockerfile | ||
| 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.