DBMS > Axibase vs. Faircom DB vs. IBM Cloudant vs. SAP HANA

System Properties Comparison Axibase vs. Faircom DB vs. IBM Cloudant vs. SAP HANA

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

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Database as a Service offering based on Apache CouchDB

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Time Series DBMS

Key-value store
Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.35
Rank	#282	Overall
	#25	Time Series DBMS

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

axibase.com/docs/atsd/finance

www.faircom.com/products/faircom-db

www.ibm.com/products/cloudant

www.sap.com/products/hana.html

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

cloud.ibm.com/docs/Cloudant

help.sap.com/hana

Developer

Axibase Corporation

FairCom Corporation

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

SAP

Initial release

2013

1979

2010

Current release

15585

V12, November 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

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

commercial

Restricted, free version available

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

ANSI C, C++

Erlang

Server operating systems

Linux

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

hosted

Appliance or cloud-service

Data scheme

yes

schema free, schema optional, schema required, partial schema,

schema-free

yes

Typing

predefined data types such as float or date

yes

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

yes, ANSI SQL Types, JSON, typed binary structures

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

SQL

Support of SQL

SQL-like query language

yes, ANSI SQL with proprietary extensions

yes

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

Go
Java
PHP
Python
R
Ruby

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

View functions (Map-Reduce) in JavaScript

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Multi-source replication
Source-replica replication

yes

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
Tunable consistency per server, database, table, and transaction

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

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

Yes, tunable from durable to delayed durability to in-memory

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

Fine grained access rights according to SQL-standard with additional protections for files

Access rights for users can be defined per database

yes

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.