DBMS > Ignite vs. OpenQM vs. Snowflake

System Properties Comparison Ignite vs. OpenQM vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

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

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

Primary database model

Key-value store
Relational DBMS

Multivalue DBMS

Relational 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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

ignite.apache.org

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

www.snowflake.com

Technical documentation

apacheignite.readme.io/docs

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Rocket Software, originally Martin Phillips

Snowflake Computing Inc.

Initial release

2015

1993

2014

Current release

Apache Ignite 2.6

3.4-12

License

Commercial or Open Source

Open Source

Apache 2.0

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

Server operating systems

Linux
OS X
Solaris
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

hosted

Data scheme

yes

with some exceptions

yes

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

Typing

predefined data types such as float or date

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

yes

APIs and other access methods

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

CLI Client
JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
Basic
C
Java
Objective C
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

yes

user defined functions

Triggers

yes (cache interceptors and events)

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

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

Foreign keys

Referential integrity

yes

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

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

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.