DBMS > IRONdb vs. Oracle NoSQL vs. SAP HANA vs. Splice Machine

System Properties Comparison IRONdb vs. Oracle NoSQL vs. SAP HANA vs. Splice Machine

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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Time Series DBMS

Document store
Key-value store
Relational DBMS

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	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Website

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

www.oracle.com/database/nosql/technologies/nosql

www.sap.com/products/hana.html

splicemachine.com

Technical documentation

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

docs.oracle.com/en/database/other-databases/nosql-database/index.html

help.sap.com/hana

splicemachine.com/how-it-works

Developer

Circonus LLC.

Oracle

SAP

Splice Machine

Initial release

2017

2011

2010

2014

Current release

V0.10.20, January 2018

24.1, May 2024

2.0 SPS07 (April 4, 2023), April 2023

3.1, March 2021

License

Commercial or Open Source

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

Open Source

AGPL 3.0, commercial license available

Cloud-based only

Only available as a cloud service

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

C and C++

Java

Server operating systems

Linux

Linux
Solaris SPARC/x86

Appliance or cloud-service

Linux
OS X
Solaris
Windows

Data scheme

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

optional

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 (Circonus Analytics Query Language: CAQL)

SQL-like DML and DDL statements

yes

APIs and other access methods

HTTP API

RESTful HTTP API

JDBC
ODBC

JDBC
Native Spark Datasource
ODBC

Supported programming languages

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

C
C#
Go
Java
JavaScript (Node.js)
Python

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

yes, in Lua

SQLScript, R

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

yes

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

configurable

ACID within a storage node (=shard)

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

off heap cache

yes

User concepts

Access control

Access rights for users and roles

yes

Access rights for users, groups and roles 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.