anph
/
hugegraph-sync
forked from hugegraph/hugegraph-sync
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
hugegraph-sync/hugegraph-server
History
V_Galaxy 1e9752109e
chore: intro `install-dist` module in root (#2552) 
* init dist in root

* adapt path & regenerate deps

* add comment

* add comment

* fix pd dir

* fix server dir

* improve hugegraph-pd/.gitignore

* improve

* rename dist -> install-dist

* fix path

* regenerate known dependencies
 		2024-06-13 17:06:37 +08:00
..
hugegraph-api fix: update resource references (#2522) 2024-04-16 15:10:49 +08:00
hugegraph-cassandra fix(server): clean up the code (#2456) 2024-02-22 17:26:15 +08:00
hugegraph-core feat(store): integrate `store-core` submodule (#2548) 2024-06-07 17:25:42 +08:00
hugegraph-dist chore: intro `install-dist` module in root (#2552) 2024-06-13 17:06:37 +08:00
hugegraph-example fix: format and clean code in dist and example modules (#2441) 2024-02-20 17:22:07 +08:00
hugegraph-hbase fix(server): clean up the code (#2456) 2024-02-22 17:26:15 +08:00
hugegraph-hstore feat(server): integrate `server-hstore` into hugegraph (#2534) 2024-05-06 20:09:12 +08:00
hugegraph-mysql fix(server): clean up the code (#2456) 2024-02-22 17:26:15 +08:00
hugegraph-palo fix(server): clean up the code (#2456) 2024-02-22 17:26:15 +08:00
hugegraph-postgresql fix(server): clean up the code (#2456) 2024-02-22 17:26:15 +08:00
hugegraph-rocksdb fix: multi graph error in rocksdb with same path/fd 2024-03-22 10:51:57 +08:00
hugegraph-scylladb fix(server): remove extra blank lines (#2459) 2024-02-25 11:45:00 +08:00
hugegraph-test chore: reset license header for file declared in LICENSE (#2550) 2024-06-11 10:08:23 +08:00
Dockerfile fix(chore): remove zgc in dockerfile for ARM env (#2421) 2024-01-26 16:48:41 +08:00
README.md chore: reset hugegraph version to 1.2.0 (#2382) 2023-12-09 22:02:49 +08:00
pom.xml chore: intro `install-dist` module in root (#2552) 2024-06-13 17:06:37 +08:00

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.