DBMS > Amazon Redshift vs. Couchbase vs. H2GIS vs. Vitess

System Properties Comparison Amazon Redshift vs. Couchbase vs. H2GIS vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Spatial extension of H2

Scalable, distributed, cloud-native DBMS, extending MySQL

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

Relational DBMS

Document store
Spatial DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	16.74
Rank	#33	Overall
	#5	Document stores

Score	0.00
Rank	#385	Overall
	#7	Spatial DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

aws.amazon.com/redshift

www.couchbase.com

www.h2gis.org

vitess.io

Technical documentation

docs.aws.amazon.com/redshift

docs.couchbase.com

www.h2gis.org/docs/home

vitess.io/docs

Developer

Amazon (based on PostgreSQL)

Couchbase, Inc.

CNRS

The Linux Foundation, PlanetScale

Initial release

2012

2011

2013

Current release

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

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

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

Open Source

LGPL 3.0

Open Source

Apache Version 2.0, commercial licenses available

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

Java

Server operating systems

hosted

Linux
OS X
Windows

Docker
Linux
macOS

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

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

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

yes

based on H2

yes

proprietary syntax

Triggers

yes

via the TAP protocol

yes

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

yes

based on H2

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

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

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.

yes

based on H2

Users with fine-grained authorization concept

no user groups or roles

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.