DBMS > Amazon DynamoDB vs. Couchbase vs. Cubrid vs. Drizzle vs. Google Cloud Bigtable

System Properties Comparison Amazon DynamoDB vs. Couchbase vs. Cubrid vs. Drizzle vs. Google Cloud Bigtable

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.

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Primary database model

Document store
Key-value store

Document store

Relational 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	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

Score	18.46
Rank	#36	Overall
	#5	Document stores

Score	1.31
Rank	#169	Overall
	#78	Relational DBMS

Score	3.58
Rank	#92	Overall
	#14	Key-value stores
	#8	Wide column stores

Website

aws.amazon.com/dynamodb

www.couchbase.com

cubrid.com (korean)
cubrid.org (english)

cloud.google.com/bigtable

Technical documentation

docs.aws.amazon.com/dynamodb

docs.couchbase.com

cubrid.org/manuals

cloud.google.com/bigtable/docs

Developer

Amazon

Couchbase, Inc.

CUBRID Corporation, CUBRID Foundation

Drizzle project, originally started by Brian Aker

Google

Initial release

2012

2011

2008

2015

Current release

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

11.0, January 2021

7.2.4, September 2012

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

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

Open Source

Apache Version 2.0

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, C++, Java

C++

Server operating systems

hosted

Linux
OS X
Windows

Linux
Windows

FreeBSD
Linux
OS X

hosted

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

RESTful HTTP API

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

ADO.NET
JDBC
ODBC
OLE DB

JDBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C
C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C
C++
Java
PHP

C#
C++
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

Java Stored Procedures

Triggers

yes

by integration with AWS Lambda

yes

via the TAP protocol

yes

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

including cross data center replication
Source-replica replication

Source-replica replication

Multi-source replication
Source-replica replication

Internal replication in Colossus, and regional replication between two clusters in different zones

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

Atomic single-row operations

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

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

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

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.