DBMS > Couchbase vs. Immudb vs. MySQL vs. SingleStore vs. TinkerGraph

System Properties Comparison Couchbase vs. Immudb vs. MySQL vs. SingleStore vs. TinkerGraph

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

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Widely used open source RDBMS

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Document store

Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

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

Relational DBMS

Document store
Spatial DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	15.82
Rank	#36	Overall
	#5	Document stores

Score	0.31
Rank	#278	Overall
	#39	Key-value stores

Score	1017.80
Rank	#2	Overall
	#2	Relational DBMS

Score	4.22
Rank	#69	Overall
	#37	Relational DBMS

Score	0.07
Rank	#346	Overall
	#35	Graph DBMS

Website

www.couchbase.com

github.com/codenotary/immudb
immudb.io

www.mysql.com

www.singlestore.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

Developer

Couchbase, Inc.

Codenotary

Oracle

since 2010, originally MySQL AB, then Sun

SingleStore Inc.

Initial release

2011

2020

1995

2013

2009

Current release

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

1.2.3, April 2022

9.0.0, July 2024

8.5, January 2024

License

Commercial or Open Source

Open Source

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

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

free developer edition available

Open Source

Apache 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 and C++

C++, Go

Java

Server operating systems

Linux
OS X
Windows

BSD
Linux
macOS
Solaris
Windows
z/OS

FreeBSD
Linux
OS X
Solaris
Windows

Linux

64 bit version required

Data scheme

schema-free

yes

schema-free

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

SQL-like syntax

yes

with proprietary extensions

yes

but no triggers and foreign keys

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

gRPC protocol
PostgreSQL wire protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

TinkerPop 3

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.Net
Go
Java
JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Bash
C
C#
Java
JavaScript (Node.js)
Python

Groovy
Java

Server-side scripts

Stored procedures

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

yes

proprietary syntax

yes

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

hash partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication
Source-replica replication

Source-replica replication

stores two copies of each physical data partition on two separate nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

optional

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.

Users with fine-grained authorization concept

no user groups or roles

Fine grained access control via users, groups and roles

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.