DBMS > Couchbase vs. MySQL vs. SiteWhere vs. Tarantool

System Properties Comparison Couchbase vs. MySQL vs. SiteWhere vs. Tarantool

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

Widely used open source RDBMS

M2M integration platform for persisting/querying time series data

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

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

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	18.46
Rank	#36	Overall
	#5	Document stores

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	0.06
Rank	#367	Overall
	#36	Time Series DBMS

Score	1.67
Rank	#150	Overall
	#25	Document stores
	#25	Key-value stores
	#69	Relational DBMS

Website

www.couchbase.com

www.mysql.com

github.com/sitewhere/sitewhere

www.tarantool.io

Technical documentation

docs.couchbase.com

dev.mysql.com/doc

sitewhere1.sitewhere.io/index.html

www.tarantool.io/en/doc

Developer

Couchbase, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

SiteWhere

Initial release

2011

1995

2010

2008

Current release

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

8.3.0, January 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

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

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Common Public Attribution License Version 1.0

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C, C++, Go and Erlang

C and C++

Java

C and C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

BSD
Linux
macOS

Data scheme

schema-free

yes

predefined scheme

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

with proprietary extensions

Full-featured ANSI SQL support

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

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

Open binary protocol

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

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

yes

proprietary syntax

Lua, C and SQL stored procedures

Triggers

yes

via the TAP protocol

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on HBase

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

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

selectable replication factor

based on HBase

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

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

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

Ephemeral buckets

yes

yes, full featured in-memory storage engine with persistence

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

Users with fine-grained authorization concept

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users 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.