DBMS > Couchbase vs. Drizzle vs. IRONdb vs. Realm vs. Trafodion

System Properties Comparison Couchbase vs. Drizzle vs. IRONdb vs. Realm vs. Trafodion

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Transactional SQL-on-Hadoop DBMS

Primary database model

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

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

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	7.41
Rank	#52	Overall
	#8	Document stores

Website

www.couchbase.com

www.circonus.com/solutions/time-series-database/

realm.io

trafodion.apache.org

Technical documentation

docs.couchbase.com

docs.circonus.com/irondb/category/getting-started

realm.io/docs

trafodion.apache.org/documentation.html

Developer

Couchbase, Inc.

Drizzle project, originally started by Brian Aker

Circonus LLC.

Realm, acquired by MongoDB in May 2019

Apache Software Foundation, originally developed by HP

Initial release

2011

2008

2017

2014

Current release

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

7.2.4, September 2012

V0.10.20, January 2018

2.3.0, February 2019

License

Commercial or Open Source

Open Source

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

Open Source

GNU GPL

commercial

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

C and C++

C++, Java

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X

Linux

Android
Backend: server-less
iOS
Windows

Linux

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

yes

with proprietary extensions

SQL-like query language (Circonus Analytics Query Language: CAQL)

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

JDBC

HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C
C++
Java
PHP

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

.Net
Java

with Android only
Objective-C
React Native
Swift

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

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

yes, in Lua

runs within the applications so server-side scripts are unnecessary

Java Stored Procedures

Triggers

yes

via the TAP protocol

hooks for callbacks inside the server can be used.

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

Automatic, metric affinity per node

none

Sharding

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

configurable replication factor, datacenter aware

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate consistency per node, eventual consistency across nodes

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

In-Memory realm

User concepts

Access control

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

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.