DBMS > Amazon DocumentDB vs. BigObject vs. Couchbase vs. HugeGraph

System Properties Comparison Amazon DocumentDB vs. BigObject vs. Couchbase vs. HugeGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Analytic DBMS for real-time computations and queries

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

A fast-speed and highly-scalable Graph DBMS

Primary database model

Document store

Relational DBMS

a hierachical model (tree) can be imposed

Document store

Graph DBMS

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	1.91
Rank	#132	Overall
	#24	Document stores

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Website

aws.amazon.com/documentdb

bigobject.io

www.couchbase.com

github.com/hugegraph
hugegraph.apache.org

Technical documentation

aws.amazon.com/documentdb/resources

docs.bigobject.io

docs.couchbase.com

hugegraph.apache.org/docs

Developer

BigObject, Inc.

Couchbase, Inc.

Baidu

Initial release

2019

2015

2011

2018

Current release

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

0.9

License

Commercial or Open Source

commercial

free community edition available

Open Source

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

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

yes

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

Java

Server operating systems

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux
OS X
Windows

Linux
macOS
Unix

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

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-like DML and DDL statements

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

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

fluentd
ODBC
RESTful HTTP API

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

Java API
RESTful HTTP API
TinkerPop Gremlin

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Groovy
Java
Python

Server-side scripts

Stored procedures

Lua

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

asynchronous Gremlin script jobs

Triggers

yes

via the TAP protocol

Partitioning methods

Methods for storing different data on different nodes

none

Automatic Sharding

yes

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

none

Multi-source replication

including cross data center replication
Source-replica replication

yes

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

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Eventual Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

automatically between fact table and dimension tables

yes

edges in graph

Transaction concepts

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

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

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

Access rights for users and roles

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

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.