DBMS > Amazon DocumentDB vs. Apache Druid vs. Couchbase vs. Manticore Search vs. TerminusDB

System Properties Comparison Amazon DocumentDB vs. Apache Druid vs. Couchbase vs. Manticore Search vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

Multi-storage database for search, including full-text search.

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store

Relational DBMS
Time Series DBMS

Document store

Search engine

Graph DBMS

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

Time Series DBMS

using the Manticore Columnar Library

Document store
RDF store

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

aws.amazon.com/documentdb

Technical documentation

aws.amazon.com/documentdb/resources

druid.apache.org/docs/latest/design

docs.couchbase.com

manual.manticoresearch.com

terminusdb.github.io/terminusdb/#

Developer

Apache Software Foundation and contributors

Couchbase, Inc.

Manticore Software

DataChemist Ltd.

Initial release

2019

2012

2011

2017

2018

Current release

29.0.1, April 2024

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

6.0, February 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache license v2

Open Source

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

Open Source

GPL version 2

Open Source

GPL V3

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

Java

C, C++, Go and Erlang

C++

Prolog, Rust

Server operating systems

hosted

Linux
OS X
Unix

Linux
OS X
Windows

FreeBSD
Linux
macOS
Windows

Linux

Data scheme

schema-free

yes

schema-less columns are supported

schema-free

Fixed schema

yes

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

SQL for querying

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

SQL-like query language

SQL-like query language (WOQL)

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
RESTful HTTP/JSON API

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

JavaScript
Python

Server-side scripts

Stored procedures

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

user defined functions

yes

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

manual/auto, time-based

Automatic Sharding

Sharding

Partitioning is done manually, search queries against distributed index is supported

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes, via HDFS, S3 or other storage engines

Multi-source replication

including cross data center replication
Source-replica replication

Synchronous replication based on Galera library

Journaling Streams

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

yes

in-memory journaling

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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

Role-based access control

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.