DBMS > Axibase vs. IBM Cloudant vs. Machbase Neo vs. Snowflake vs. TimesTen

System Properties Comparison Axibase vs. IBM Cloudant vs. Machbase Neo vs. Snowflake vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

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

Database as a Service offering based on Apache CouchDB

TimeSeries DBMS for AIoT and BigData

Cloud-based data warehousing service for structured and semi-structured data

In-Memory RDBMS compatible to Oracle

Primary database model

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

Score	0.35
Rank	#282	Overall
	#25	Time Series DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

axibase.com/docs/atsd/finance

www.ibm.com/products/cloudant

machbase.com

www.snowflake.com

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

Technical documentation

cloud.ibm.com/docs/Cloudant

machbase.com/dbms

docs.snowflake.net/manuals/index.html

docs.oracle.com/database/timesten-18.1

Developer

Axibase Corporation

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Machbase

Snowflake Computing Inc.

Oracle, TimesTen Performance Software, HP

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

Initial release

2013

2010

2013

2014

1998

Current release

15585

V8.0, August 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

free test version available

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

Erlang

Server operating systems

Linux

hosted

Linux
macOS
Windows

hosted

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

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

yes

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

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

RESTful HTTP/JSON API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

CLI Client
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Go
Java
PHP
Python
R
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

JavaScript (Node.js)
Python

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

View functions (Map-Reduce) in JavaScript

user defined functions

PL/SQL

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

selectable replication factor

yes

Multi-source replication
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

Immediate 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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

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

volatile and lookup table

yes

User concepts

Access control

Access rights for users can be defined per database

simple password-based access control

Users with fine-grained authorization concept, user roles and pluggable authentication

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.