DBMS > Ignite vs. IRONdb vs. OpenQM vs. TempoIQ

System Properties Comparison Ignite vs. IRONdb vs. OpenQM vs. TempoIQ

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.

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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

QpenQM is a high-performance, self-tuning, multi-value DBMS

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Multivalue DBMS

Time Series DBMS

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

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Website

ignite.apache.org

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

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

tempoiq.com (offline)

Technical documentation

apacheignite.readme.io/docs

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

Developer

Apache Software Foundation

Circonus LLC.

Rocket Software, originally Martin Phillips

TempoIQ

Initial release

2015

2017

1993

2012

Current release

Apache Ignite 2.6

V0.10.20, January 2018

3.4-12

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPLv2, extended commercial license 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

C++, Java, .Net

C and C++

Server operating systems

Linux
OS X
Solaris
Windows

Linux

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

yes

schema-free

yes

with some exceptions

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

ANSI-99 for query and DML statements, subset of DDL

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

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

HTTP API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

.Net
Basic
C
Java
Objective C
PHP
Python

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

yes, in Lua

yes

Triggers

yes (cache interceptors and events)

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

configurable replication factor, datacenter aware

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

User concepts

Access control

Security Hooks for custom implementations

Access rights can be defined down to the item level

simple authentication-based access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

Apache Ignite: An Overview
6 September 2023, Open Source For You

GridGain Releases Conference Schedule for Virtual Apache Ignite Summit 2023
1 June 2023, Datanami

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

Real-time in-memory OLTP and Analytics with Apache Ignite on AWS | Amazon Web Services
14 May 2016, AWS Blog

provided by Google News

Application observability firm Apica buys telemetry data startup Circonus and adds more funding
21 February 2024, SiliconANGLE News

Apica Acquires Telemetry Data Management Pioneer Circonus And Lands New Funding
22 February 2024, Datanami

Apica gets $6 million in funding and buys Circonus -
21 February 2024, Enterprise Times

provided by Google News

Share this page