DBMS > CouchDB vs. JanusGraph vs. Manticore Search vs. MySQL vs. StarRocks

System Properties Comparison CouchDB vs. JanusGraph vs. Manticore Search vs. MySQL vs. StarRocks

Editorial information provided by DB-Engines

Name

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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

Widely used open source RDBMS

An open source, high-performance columnar analytical database that enables real-time, multi-dimensional, and highly concurrent data analytics

Forked from Apache Doris

Primary database model

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Time Series DBMS

using the Manticore Columnar Library

Document store
Spatial DBMS

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.93
Rank	#198	Overall
	#93	Relational DBMS

Website

Technical documentation

docs.couchdb.org/en/stable

docs.janusgraph.org

manual.manticoresearch.com

dev.mysql.com/doc

docs.starrocks.io/en-us/latest/introduction/StarRocks_intro

Developer

Apache Software Foundation

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

Linux Foundation; originally developed as Titan by Aurelius

Manticore Software

Oracle

since 2010, originally MySQL AB, then Sun

The Linux Foundation

since Feb 2023

Initial release

2005

2017

1995

2020

Current release

3.3.3, December 2023

0.6.3, February 2023

6.0, February 2023

8.4.0, April 2024

2.5.3, March 2023

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache 2.0

Open Source

GPL version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Erlang

Java

C++

C and C++

C++, Java

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

FreeBSD
Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

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

yes

Secondary indexes

yes

via views

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

yes

APIs and other access methods

RESTful HTTP/JSON API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

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

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
MySQL protocol

Supported programming languages

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

Clojure
Java
Python

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

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

Java

Server-side scripts

Stored procedures

View functions in JavaScript

yes

user defined functions

yes

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning (by range and hash)

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Synchronous replication based on Galera library

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

atomic operations within a single document possible

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

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

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights for users can be defined per database

User authentification and security via Rexster Graph Server

Users with fine-grained authorization concept

no user groups or roles

Role based access control and fine grained access rights

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.