DBMS > CouchDB vs. JaguarDB vs. Microsoft Azure Cosmos DB vs. Valentina Server

System Properties Comparison CouchDB vs. JaguarDB vs. Microsoft Azure Cosmos DB vs. Valentina Server

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.

Performant, highly scalable DBMS for AI and IoT applications

Globally distributed, horizontally scalable, multi-model database service

Object-relational database and reports server

Primary database model

Document store

Key-value store
Vector DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Spatial DBMS

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

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

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

couchdb.apache.org

www.jaguardb.com

azure.microsoft.com/services/cosmos-db

www.valentina-db.net

Technical documentation

docs.couchdb.org/en/stable

www.jaguardb.com/support.html

learn.microsoft.com/azure/cosmos-db

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Apache Software Foundation

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

DataJaguar, Inc.

Microsoft

Paradigma Software

Initial release

2005

2015

2014

1999

Current release

3.3.3, December 2023

3.3 July 2023

5.7.5

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

GPL V3.0

commercial

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

Erlang

C++

the server part. Clients available in other languages

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

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

via views

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

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

ODBC

Supported programming languages

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

View functions in JavaScript

JavaScript

yes

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

Multi-item ACID transactions with snapshot isolation within a partition

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

User concepts

Access control

Access rights for users can be defined per database

rights management via user accounts

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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.