DBMS > Couchbase vs. Dgraph vs. EsgynDB vs. Rockset vs. YDB

System Properties Comparison Couchbase vs. Dgraph vs. EsgynDB vs. Rockset vs. YDB

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

A scalable, reliable search and analytics service in the cloud, built on RocksDB

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Document store
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

Relational DBMS
Search engine

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.82
Rank	#212	Overall
	#36	Document stores

Score	0.33
Rank	#287	Overall
	#43	Document stores
	#132	Relational DBMS

Website

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

Developer

Couchbase, Inc.

Dgraph Labs, Inc.

Esgyn

Rockset

Yandex

Initial release

2011

2016

2015

2019

Current release

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

License

Commercial or Open Source

Open Source

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

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0; commercial license available

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

C++, Java

C++

Server operating systems

Linux
OS X
Windows

Linux

hosted

Linux

Data scheme

schema-free

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

Typing

predefined data types such as float or date

yes

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

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

yes

Read-only SQL queries, including JOINs

SQL-like query language (YQL)

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

HTTP REST

RESTful HTTP API (DynamoDB compatible)

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

Go
Java
JavaScript (Node.js)
Python

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

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

Java Stored Procedures

Triggers

yes

via the TAP protocol

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

yes

Sharding

Automatic sharding

Sharding

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

Active-passive shard 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

Eventual Consistency

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

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 organizations can be defined via Rockset console

Access rights defined for Yandex Cloud users

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.