DBMS > GridGain vs. RDF4J vs. Rockset vs. Snowflake

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

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.

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

Primary database model

Key-value store
Relational DBMS

RDF store

Document store

Relational DBMS

Secondary database models

Relational DBMS
Search engine

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

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

www.gridgain.com/docs/index.html

rdf4j.org/documentation

docs.rockset.com

docs.snowflake.net/manuals/index.html

Developer

GridGain Systems, Inc.

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

Rockset

Snowflake Computing Inc.

Initial release

2007

2004

2019

2014

Current release

GridGain 8.5.1

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.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

Java, C++, .Net

Java

C++

Server operating systems

Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

hosted

Data scheme

yes

RDF Schemas

schema-free

yes

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

Typing

predefined data types such as float or date

yes

dynamic typing

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

ingestion from XML files supported

yes

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

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

Read-only SQL queries, including JOINs

yes

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

HTTP REST

CLI Client
JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Java
PHP
Python

Go
Java
JavaScript (Node.js)
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

none

Automatic sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

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

Eventual Consistency

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 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 for users and organizations can be defined via Rockset console

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.