DBMS > BaseX vs. Couchbase vs. Tarantool vs. Warp 10 vs. Yaacomo

System Properties Comparison BaseX vs. Couchbase vs. Tarantool vs. Warp 10 vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

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

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Native XML DBMS

Document store

Document store
Key-value store
Relational DBMS

Time Series 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

with Tarantool/GIS extension

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

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

yaacomo.com

Technical documentation

docs.basex.org

docs.couchbase.com

www.tarantool.io/en/doc

www.warp10.io/content/02_Getting_started

Developer

BaseX GmbH

Couchbase, Inc.

SenX

Q2WEB GmbH

Initial release

2007

2011

2008

2015

2009

Current release

10.7, August 2023

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

2.10.0, May 2022

License

Commercial or Open Source

Open Source

BSD license

Open Source

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

Open Source

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

Open Source

Apache License 2.0

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

Java

C, C++, Go and Erlang

C and C++

Java

Server operating systems

Linux
OS X
Windows

BSD
Linux
macOS

Linux
OS X
Windows

Android
Linux
Windows

Data scheme

schema-free

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

schema-free

yes

Typing

predefined data types such as float or date

XQuery supports types

yes

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

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

SQL

Support of SQL

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

Full-featured ANSI SQL support

yes

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

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

Open binary protocol

HTTP API
Jupyter
WebSocket

JDBC
ODBC

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

yes

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

Lua, C and SQL stored procedures

yes

WarpScript

Triggers

yes

via events

yes

via the TAP protocol

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

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic Sharding

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

Sharding

based on HBase

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

including cross data center replication
Source-replica replication

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

selectable replication factor

based on HBase

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

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

Immediate Consistency

based on HBase

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

multiple readers, single writer

ACID

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes

Ephemeral buckets

yes, full featured in-memory storage engine with persistence

yes

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

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

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

fine grained access rights according to SQL-standard

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.