DBMS > CouchDB vs. EJDB vs. GeoMesa vs. Newts vs. Sequoiadb

System Properties Comparison CouchDB vs. EJDB vs. GeoMesa vs. Newts vs. Sequoiadb

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.

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Time Series DBMS based on Cassandra

NewSQL database with distributed OLTP and SQL

Primary database model

Document store

Spatial DBMS

Time Series DBMS

Document 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	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Website

couchdb.apache.org

github.com/Softmotions/ejdb

www.geomesa.org

opennms.github.io/newts

www.sequoiadb.com

Technical documentation

docs.couchdb.org/en/stable

github.com/Softmotions/ejdb/blob/master/README.md

www.geomesa.org/documentation/stable/user/index.html

github.com/OpenNMS/newts/wiki

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Apache Software Foundation

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

Softmotions

CCRi and others

OpenNMS Group

Sequoiadb Ltd.

Initial release

2005

2012

2014

2013

Current release

3.3.3, December 2023

4.0.5, February 2024

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

GPLv2

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

Server: AGPL; Client: Apache V2

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

Scala

Java

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

server-less

Linux
OS X
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

oid, date, timestamp, binary, regex

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 query language

APIs and other access methods

RESTful HTTP/JSON API

in-process shared library

HTTP REST
Java API

proprietary protocol using JSON

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++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Java

.Net
C++
Java
PHP
Python

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

none

depending on storage layer

Sharding

based on Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

depending on storage layer

selectable replication factor

based on Cassandra

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

depending on storage layer

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

atomic operations within a single document possible

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Read/Write 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.

depending on storage layer

User concepts

Access control

Access rights for users can be defined per database

yes

depending on the DBMS used for storage

simple password-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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Couchbase climbs up the DB-Engines Ranking, increasing its popularity by 10% every month
2 June 2014, Matthias Gelbmann

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

How to Automate A Blog Post App Deployment With GitHub Actions, Node.js, CouchDB, and Aptible
4 December 2023, hackernoon.com

IBM Cloudant pulls plan to fund new foundational layer for CouchDB
15 March 2022, The Register

How to install the CouchDB NoSQL database on Debian Server 11
16 June 2022, TechRepublic

CouchDB 3.0 ends admin party era • DEVCLASS
27 February 2020, DevClass

CouchDB 3.0 puts safety first
27 February 2020, InfoWorld

provided by Google News

Share this page