hugegraph-sync/hugegraph-server
Bond 7b33574fd0
feat: added the OpenTelemetry trace support (#2477)
TODO: we need enhance our shell experience
---------

Co-authored-by: imbajin <jin@apache.org>
Co-authored-by: VGalaxies <vgalaxies@apache.org>
2024-03-15 17:30:16 +08:00
..
hugegraph-api fix(auth): enhance the URL check (#2422) 2024-03-09 21:04:30 +08:00
hugegraph-cassandra fix(server): clean up the code (#2456) 2024-02-22 17:26:15 +08:00
hugegraph-core feat(api): optimize adjacent-edges query (#2408) 2024-02-26 12:29:13 +08:00
hugegraph-dist feat: added the OpenTelemetry trace support (#2477) 2024-03-15 17:30:16 +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-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(server): clean up the code (#2456) 2024-02-22 17:26:15 +08:00
hugegraph-scylladb fix(server): remove extra blank lines (#2459) 2024-02-25 11:45:00 +08:00
hugegraph-test fix(server): clean up the code (#2456) 2024-02-22 17:26:15 +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 fix(server): unify the license headers (#2438) 2024-02-07 12:53:57 +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.