hugegraph-sync/hugegraph-server
benny066567 dce7995d9a
fix(server): tx leak when stopping the graph server (#2791)
2025-06-16 14:46:40 +08:00
..
hugegraph-api chore(server): remove some outdated configuration 2025-05-14 18:51:55 +08:00
hugegraph-cassandra BREAKING CHANGE(server): support "parent & child" EdgeLabel type (#2662) 2024-10-10 00:15:32 +08:00
hugegraph-core fix(server): tx leak when stopping the graph server (#2791) 2025-06-16 14:46:40 +08:00
hugegraph-dist BREAKING CHANGE(server): disable legacy backends include `MySQL/PG/c*`(.etc) (#2746) 2025-04-28 15:20:37 +08:00
hugegraph-example BREAKING CHANGE(server): disable legacy backends include `MySQL/PG/c*`(.etc) (#2746) 2025-04-28 15:20:37 +08:00
hugegraph-hbase feat(server): support new backend Hstore (#2560) 2024-07-10 16:35:44 +08:00
hugegraph-hstore BREAKING CHANGE(server): support "parent & child" EdgeLabel type (#2662) 2024-10-10 00:15:32 +08:00
hugegraph-mysql BREAKING CHANGE(server): support "parent & child" EdgeLabel type (#2662) 2024-10-10 00:15:32 +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 feat(server): support new backend Hstore (#2560) 2024-07-10 16:35:44 +08:00
hugegraph-scylladb fix(server): remove extra blank lines (#2459) 2024-02-25 11:45:00 +08:00
hugegraph-test feat(server): LoginAPI support token_expire field (#2754) 2025-05-05 11:49:12 +08:00
Dockerfile fix(docker): fix build pd-store arm image 2025-03-10 16:53:04 +08:00
Dockerfile-hstore chore(dist): intro additional Dockerfile to build the server image & skip init-hstore backend (#2642) 2024-08-22 14:04:06 +08:00
README.md BREAKING CHANGE(server): disable legacy backends include `MySQL/PG/c*`(.etc) (#2746) 2025-04-28 15:20:37 +08:00
pom.xml chore(dist): tar source and binary package for hugegraph with pd-store (#2594) 2024-08-06 21:21:14 +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/Memory/HStore/HBase/...) and allows users to extend custom backends without modifying the existing source code.