DBMS > Couchbase vs. Dgraph vs. HEAVY.AI vs. Tibero

System Properties Comparison Couchbase vs. Dgraph vs. HEAVY.AI vs. Tibero

Please select another system to include it in the comparison.

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Document store

Graph DBMS

Relational 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

Spatial 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	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Website

www.couchbase.com

dgraph.io

github.com/heavyai/heavydb
www.heavy.ai

us.tmaxsoft.com/products/tibero

Technical documentation

docs.couchbase.com

dgraph.io/docs

docs.heavy.ai

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Couchbase, Inc.

Dgraph Labs, Inc.

HEAVY.AI, Inc.

TmaxSoft

Initial release

2011

2016

2003

Current release

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

5.10, January 2022

6, April 2015

License

Commercial or Open Source

Open Source

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

Open Source

Apache 2.0

Open Source

Apache Version 2; enterprise edition available

commercial

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++ and CUDA

C and Assembler

Server operating systems

Linux
OS X
Windows

Linux

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

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.

yes

Secondary indexes

yes

SQL

Support of SQL

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

yes

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

JDBC
ODBC
Thrift
Vega

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

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/Thrift
Python

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

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

Persistent Stored Procedure (PSM)

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

yes

Sharding

Round robin

horizontal partitioning

by range, hash, list or composite

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

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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

planned for next version

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

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.