DBMS > Amazon Redshift vs. Couchbase vs. Dgraph vs. Drizzle

System Properties Comparison Amazon Redshift vs. Couchbase vs. Dgraph vs. Drizzle

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.

Description

Large scale data warehouse service for use with business intelligence tools

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

Distributed and scalable native Graph DBMS

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

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	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	18.46
Rank	#36	Overall
	#5	Document stores

Score	1.48
Rank	#158	Overall
	#15	Graph DBMS

Website

aws.amazon.com/redshift

www.couchbase.com

dgraph.io

Technical documentation

docs.aws.amazon.com/redshift

docs.couchbase.com

dgraph.io/docs

Developer

Amazon (based on PostgreSQL)

Couchbase, Inc.

Dgraph Labs, Inc.

Drizzle project, originally started by Brian Aker

Initial release

2012

2011

2016

2008

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

commercial

Open Source

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

Open Source

Apache 2.0

Open Source

GNU GPL

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

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
OS X

Data scheme

yes

schema-free

yes

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

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

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

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

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JDBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

C
C++
Java
PHP

Server-side scripts

Stored procedures

user defined functions

in Python

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

Triggers

yes

via the TAP protocol

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

including cross data center replication
Source-replica replication

Synchronous replication via Raft

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

User concepts

Access control

fine grained access rights according to SQL-standard

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

Planned for future releases

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.