DBMS > Apache Drill vs. Ignite vs. InfinityDB vs. Ingres vs. RocksDB

System Properties Comparison Apache Drill vs. Ignite vs. InfinityDB vs. Ingres vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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 Java embedded Key-Value Store which extends the Java Map interface

Well established RDBMS

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store
Relational DBMS

Key-value store
Relational DBMS

Key-value store

Relational DBMS

Key-value store

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

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

Score	0.00
Rank	#378	Overall
	#57	Key-value stores

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

drill.apache.org

ignite.apache.org

boilerbay.com

www.actian.com/databases/ingres

rocksdb.org

Technical documentation

drill.apache.org/docs

apacheignite.readme.io/docs

boilerbay.com/infinitydb/manual

docs.actian.com/ingres

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Boiler Bay Inc.

Actian Corporation

Facebook, Inc.

Initial release

2012

2015

2002

1974

originally developed at University Berkely in early 1970s

2013

Current release

1.20.3, January 2023

Apache Ignite 2.6

4.0

11.2, May 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

commercial

Open Source

BSD

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++, Java, .Net

Java

C++

Server operating systems

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

All OS with a Java VM

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

schema-free

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

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

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

C++ API
Java API

Supported programming languages

C++

C#
C++
Java
PHP
Python
Ruby
Scala

Java

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

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

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

Ingres Replicator

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

yes

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Security Hooks for custom implementations

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.