DBMS > Graph Engine vs. GridGain vs. HyperSQL vs. IBM Db2 warehouse vs. SQLite

System Properties Comparison Graph Engine vs. GridGain vs. HyperSQL vs. IBM Db2 warehouse vs. SQLite

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Cloud-based data warehousing service

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
Key-value store

Key-value store
Relational DBMS

Relational DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

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

Score	3.49
Rank	#87	Overall
	#47	Relational DBMS

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.graphengine.io

www.gridgain.com

hsqldb.org

www.ibm.com/products/db2/warehouse

www.sqlite.org

Technical documentation

www.graphengine.io/docs/manual

www.gridgain.com/docs/index.html

hsqldb.org/web/hsqlDocsFrame.html

www.sqlite.org/docs.html

Developer

Microsoft

GridGain Systems, Inc.

IBM

Dwayne Richard Hipp

Initial release

2010

2007

2001

2014

2000

Current release

GridGain 8.5.1

2.7.2, June 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

based on BSD license

commercial

Open Source

Public Domain

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

.NET and C

Java, C++, .Net

Java

Server operating systems

.NET

Linux
OS X
Solaris
Windows

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

hosted

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Import/export of XML data possible

Secondary indexes

yes

SQL

Support of SQL

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

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

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

HTTP API

JDBC via HTTP
JDBC
ODBC

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
F#
Visual Basic

C#
C++
Java
PHP
Python
Ruby
Scala

All languages supporting JDBC/ODBC
Java

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

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

Java, SQL

PL/SQL, SQL PL

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

yes

none

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

via file-system locks

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.