DBMS > Ignite vs. JanusGraph vs. Oracle Coherence vs. Snowflake

System Properties Comparison Ignite vs. JanusGraph vs. Oracle Coherence 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.

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Oracles in-memory data grid solution

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

Primary database model

Key-value store
Relational DBMS

Graph DBMS

Key-value store

Relational DBMS

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

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

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	1.97
Rank	#129	Overall
	#22	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

ignite.apache.org

janusgraph.org

www.oracle.com/java/coherence

www.snowflake.com

Technical documentation

apacheignite.readme.io/docs

docs.janusgraph.org

docs.oracle.com/en/middleware/standalone/coherence

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Linux Foundation; originally developed as Titan by Aurelius

Oracle

Snowflake Computing Inc.

Initial release

2015

2017

2007

2014

Current release

Apache Ignite 2.6

0.6.3, February 2023

14.1, August 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

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

Java

Server operating systems

Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

All OS with a Java VM

hosted

Data scheme

yes

schema-free

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

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JCache
JPA
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Clojure
Java
Python

.Net
C++
Java

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

Live Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

yes, with selectable consistency level

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

configurable

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

optionally

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

User authentification and security via Rexster Graph Server

authentification to access the cache via certificates or http basic authentication

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.