DBMS > Axibase vs. Microsoft Azure Cosmos DB vs. TerminusDB vs. TimesTen

System Properties Comparison Axibase vs. Microsoft Azure Cosmos DB vs. TerminusDB vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

Globally distributed, horizontally scalable, multi-model database service

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

In-Memory RDBMS compatible to Oracle

Primary database model

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store
RDF store

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

Score	0.29
Rank	#292	Overall
	#25	Time Series 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	#325	Overall
	#29	Graph DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

axibase.com/docs/atsd/finance

azure.microsoft.com/services/cosmos-db

terminusdb.com

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

learn.microsoft.com/azure/cosmos-db

terminusdb.github.io/terminusdb/#

docs.oracle.com/database/timesten-18.1

Developer

Axibase Corporation

Microsoft

DataChemist Ltd.

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2013

2014

2018

1998

Current release

15585

11.0.0, January 2023

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

commercial

Open Source

GPL V3

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

Java

Prolog, Rust

Server operating systems

Linux

hosted

Linux

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

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

SQL

Support of SQL

SQL-like query language

SQL-like query language (WOQL)

yes

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Go
Java
PHP
Python
R
Ruby

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

JavaScript
Python

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

JavaScript

yes

PL/SQL

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Graph Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Implicit feature of the cloud service

Journaling Streams

Multi-source replication
Source-replica replication

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

in-memory journaling

yes

by means of logfiles and checkpoints

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

Role-based access control

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.