DBMS > GridGain vs. RDF4J vs. Snowflake vs. TerminusDB

System Properties Comparison GridGain vs. RDF4J vs. Snowflake vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GridGain is an in-memory computing platform, built on Apache Ignite

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Key-value store
Relational DBMS

RDF store

Relational DBMS

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

Technical documentation

www.gridgain.com/docs/index.html

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

Developer

GridGain Systems, Inc.

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Snowflake Computing Inc.

DataChemist Ltd.

Initial release

2007

2004

2014

2018

Current release

GridGain 8.5.1

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Open Source

GPL V3

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

Java, C++, .Net

Java

Prolog, Rust

Server operating systems

Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

hosted

Linux

Data scheme

yes

RDF Schemas

yes

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

yes

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

SQL-like query language (WOQL)

APIs and other access methods

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

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Java
PHP
Python

JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

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

yes

user defined functions

yes

Triggers

yes (cache interceptors and events)

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

yes

Journaling Streams

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

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

in-memory journaling

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

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

Role-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.