DBMS > CouchDB vs. Percona Server for MongoDB vs. RocksDB vs. Spark SQL

System Properties Comparison CouchDB vs. Percona Server for MongoDB vs. RocksDB vs. Spark SQL

Please select another system to include it in the comparison.

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 drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Document store

Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	10.26
Rank	#45	Overall
	#7	Document stores

Score	0.55
Rank	#253	Overall
	#39	Document stores

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	19.15
Rank	#33	Overall
	#20	Relational DBMS

Website

couchdb.apache.org

www.percona.com/mongodb/software/percona-server-for-mongodb

rocksdb.org

spark.apache.org/sql

Technical documentation

docs.couchdb.org/en/stable

docs.percona.com/percona-distribution-for-mongodb

github.com/facebook/rocksdb/wiki

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Apache Software Foundation

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

Percona

Facebook, Inc.

Apache Software Foundation

Initial release

2005

2015

2013

2014

Current release

3.3.3, December 2023

3.4.10-2.10, November 2017

8.11.4, April 2024

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

GPL Version 2

Open Source

BSD

Open Source

Apache 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.

Implementation language

Erlang

C++

Scala

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux

Linux
OS X
Windows

Data scheme

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

yes

via views

yes

SQL

Support of SQL

SQL-like DML and DDL statements

APIs and other access methods

RESTful HTTP/JSON API

proprietary protocol using JSON

C++ API
Java API

JDBC
ODBC

Supported programming languages

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C
C++
Go
Java
Perl
Python
Ruby

Java
Python
R
Scala

Server-side scripts

Stored procedures

View functions in JavaScript

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

horizontal partitioning

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a single document possible

yes

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

via In-Memory Engine

yes

User concepts

Access control

Access rights for users can be defined per database

Access rights for users and 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.