DBMS > Couchbase vs. Drizzle vs. IBM Cloudant vs. Sqrrl

System Properties Comparison Couchbase vs. Drizzle vs. IBM Cloudant vs. Sqrrl

Please select another system to include it in the comparison.

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.

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed 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.

Database as a Service offering based on Apache CouchDB

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Document store

Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

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	2.75
Rank	#104	Overall
	#19	Document stores

Website

www.couchbase.com

www.ibm.com/products/cloudant

sqrrl.com

Technical documentation

docs.couchbase.com

cloud.ibm.com/docs/Cloudant

Developer

Couchbase, Inc.

Drizzle project, originally started by Brian Aker

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Amazon

originally Sqrrl Data, Inc.

Initial release

2011

2008

2010

2012

Current release

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

7.2.4, September 2012

License

Commercial or Open Source

Open Source

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

Open Source

GNU GPL

commercial

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

Erlang

Java

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X

hosted

Linux

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.

Secondary indexes

yes

SQL

Support of SQL

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

yes

with proprietary extensions

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

RESTful HTTP/JSON API

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C
C++
Java
PHP

C#
Java
JavaScript
Objective-C
PHP
Ruby

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

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

View functions (Map-Reduce) in JavaScript

Triggers

yes

via the TAP protocol

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

making use of Hadoop

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

making use of Hadoop

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

Eventual Consistency

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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.

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users can be defined per database

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.