DBMS > Amazon Redshift vs. CouchDB vs. Machbase Neo vs. Microsoft Azure Table Storage

System Properties Comparison Amazon Redshift vs. CouchDB vs. Machbase Neo vs. Microsoft Azure Table Storage

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 native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

TimeSeries DBMS for AIoT and BigData

A Wide Column Store for rapid development using massive semi-structured datasets

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Website

aws.amazon.com/redshift

couchdb.apache.org

machbase.com

azure.microsoft.com/en-us/services/storage/tables

Technical documentation

docs.aws.amazon.com/redshift

docs.couchdb.org/en/stable

machbase.com/dbms

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Machbase

Microsoft

Initial release

2012

2005

2013

2012

Current release

3.3.3, December 2023

V8.0, August 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

free test version available

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

Erlang

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

hosted

Data scheme

yes

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

restricted

yes

via views

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

Server-side scripts

Stored procedures

user defined functions

in Python

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

selectable replication factor

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

atomic operations within a single document possible

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

strategy: 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

volatile and lookup table

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

simple password-based access control

Access rights based on private key authentication or shared access signatures

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.