DBMS > Couchbase vs. Dgraph vs. EsgynDB vs. HarperDB vs. HugeGraph

System Properties Comparison Couchbase vs. Dgraph vs. EsgynDB vs. HarperDB vs. HugeGraph

Editorial information provided by DB-Engines

Name

Description

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

Distributed and scalable native Graph DBMS

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

A fast-speed and highly-scalable Graph DBMS

Primary database model

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	0.17
Rank	#335	Overall
	#31	Graph DBMS

Website

github.com/hugegraph
hugegraph.apache.org

Technical documentation

docs.couchbase.com

dgraph.io/docs

docs.harperdb.io/docs

hugegraph.apache.org/docs

Developer

Couchbase, Inc.

Dgraph Labs, Inc.

Esgyn

HarperDB

Baidu

Initial release

2011

2016

2015

2017

2018

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

3.1, August 2021

0.9

License

Commercial or Open Source

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

Open Source

Apache 2.0

commercial

free community edition available

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C, C++, Go and Erlang

C++, Java

Node.js

Java

Server operating systems

Linux
OS X
Windows

Linux

Linux
OS X

Linux
macOS
Unix

Data scheme

schema-free

yes

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data types

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

also supports composite index and range index

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes

SQL-like data manipulation statements

APIs and other access methods

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

ADO.NET
JDBC
ODBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Java API
RESTful HTTP API
TinkerPop Gremlin

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

Groovy
Java
Python

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

Java Stored Procedures

Custom Functions

since release 3.1

asynchronous Gremlin script jobs

Triggers

yes

via the TAP protocol

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

yes

Sharding

A table resides as a whole on one (or more) nodes in a cluster

yes

depending on used storage backend, e.g. Cassandra and HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Synchronous replication via Raft

Multi-source replication between multi datacenters

yes

the nodes on which a table resides can be defined

yes

depending on used storage backend, e.g. Cassandra and HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

edges in graph

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Ephemeral buckets

yes

User concepts

Access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

Planned for future releases

fine grained access rights according to SQL-standard

Access rights for users and roles

Users, roles and permissions

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.