DBMS > Amazon Redshift vs. Couchbase vs. Coveo vs. PouchDB vs. Prometheus

System Properties Comparison Amazon Redshift vs. Couchbase vs. Coveo vs. PouchDB vs. Prometheus

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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

JavaScript DBMS with an API inspired by CouchDB

Open-source Time Series DBMS and monitoring system

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	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

Developer

Amazon (based on PostgreSQL)

Couchbase, Inc.

Coveo

Apache Software Foundation

Initial release

2012

2011

2012

2015

Current release

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

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

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

commercial

Open Source

Apache 2.0

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

JavaScript

Server operating systems

hosted

Linux
OS X
Windows

hosted

server-less, requires a JavaScript environment (browser, Node.js)

Linux
Windows

Data scheme

yes

schema-free

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Import of XML data possible

Secondary indexes

restricted

yes

via views

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

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

RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C#
Java
JavaScript
Python

JavaScript

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

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

View functions in JavaScript

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic Sharding

yes

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

including cross data center replication
Source-replica replication

yes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

by Federation

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

none

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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.

granular access controls, API key management, content filters

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.