DBMS > EventStoreDB vs. Microsoft Azure Cosmos DB vs. Newts vs. PouchDB

System Properties Comparison EventStoreDB vs. Microsoft Azure Cosmos DB vs. Newts vs. PouchDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Industrial-strength, open-source database solution built from the ground up for event sourcing.

Globally distributed, horizontally scalable, multi-model database service

Time Series DBMS based on Cassandra

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Event Store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Document store

Secondary database models

Spatial DBMS

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

Score	1.10
Rank	#179	Overall
	#1	Event Stores

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

www.eventstore.com

azure.microsoft.com/services/cosmos-db

opennms.github.io/newts

pouchdb.com

Technical documentation

developers.eventstore.com

learn.microsoft.com/azure/cosmos-db

github.com/OpenNMS/newts/wiki

pouchdb.com/guides

Developer

Event Store Limited

Microsoft

OpenNMS Group

Apache Software Foundation

Initial release

2012

2014

2012

Current release

21.2, February 2021

7.1.1, June 2019

License

Commercial or Open Source

Open Source

commercial

Open Source

Apache 2.0

Open Source

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

JavaScript

Server operating systems

Linux
Windows

hosted

Linux
OS X
Windows

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

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

via views

SQL

Support of SQL

SQL-like query language

APIs and other access methods

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

HTTP REST
Java API

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Java

JavaScript

Server-side scripts

Stored procedures

JavaScript

View functions in JavaScript

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

based on Cassandra

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

selectable replication factor

based on Cassandra

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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 can be defined down to the item level

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.