DBMS > IRONdb vs. Microsoft Azure Cosmos DB vs. PouchDB vs. SAP Adaptive Server

System Properties Comparison IRONdb vs. Microsoft Azure Cosmos DB vs. PouchDB vs. SAP Adaptive Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Globally distributed, horizontally scalable, multi-model database service

JavaScript DBMS with an API inspired by CouchDB

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Primary database model

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Relational DBMS

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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

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

Score	2.35
Rank	#116	Overall
	#22	Document stores

Score	37.12
Rank	#25	Overall
	#17	Relational DBMS

Website

www.circonus.com/solutions/time-series-database/

azure.microsoft.com/services/cosmos-db

pouchdb.com

www.sap.com/products/technology-platform/sybase-ase.html

Technical documentation

docs.circonus.com/irondb/category/getting-started

learn.microsoft.com/azure/cosmos-db

pouchdb.com/guides

help.sap.com/docs/SAP_ASE

Developer

Circonus LLC.

Microsoft

Apache Software Foundation

SAP, Sybase

Initial release

2017

2014

2012

1987

Current release

V0.10.20, January 2018

7.1.1, June 2019

16.0

License

Commercial or Open Source

commercial

Open Source

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

C and C++

JavaScript

C and C++

Server operating systems

Linux

hosted

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

AIX
HP-UX
Linux
Solaris
Unix
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

yes

SQL

Support of SQL

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like query language

yes

APIs and other access methods

HTTP API

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

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

JavaScript

C
C++
Cobol
Java
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

yes, in Lua

JavaScript

View functions in JavaScript

Java and Transact-SQL

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

Implicit feature of the cloud service

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes

Implicit feature of the cloud service

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Multi-source replication
Source-replica replication

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

Immediate consistency per node, eventual consistency across nodes

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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