DBMS > GridGain vs. SQLite vs. UniData,UniVerse vs. VoltDB

System Properties Comparison GridGain vs. SQLite vs. UniData,UniVerse vs. VoltDB

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

Widely used embeddable, in-process RDBMS

MultiValue database and application server with SQL mapping layer and meta database capabilities

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Multivalue DBMS

Relational DBMS

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	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	3.16
Rank	#97	Overall
	#2	Multivalue DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

www.gridgain.com

www.sqlite.org

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

www.voltdb.com

Technical documentation

www.gridgain.com/docs/index.html

www.sqlite.org/docs.html

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

docs.voltdb.com

Developer

GridGain Systems, Inc.

Dwayne Richard Hipp

Rocket Software

VoltDB Inc.

Initial release

2007

2000

1985

2010

Current release

GridGain 8.5.1

3.45.3 (15 April 2024), April 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Public Domain

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Cloud-based only

Only available as a cloud service

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

server-less

AIX
HP-UX
Linux
Solaris
Windows

Linux
OS X

for development

Data scheme

yes

dynamic column types

schema-free

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

optional

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-92 is not fully supported

yes

only a subset of SQL 99

APIs and other access methods

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

.Net
Basic

U2 Basic
C
Java

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

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

yes

Java

Triggers

yes (cache interceptors and events)

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

Source-replica replication

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

configurable

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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 according to SQL-standard and operating system based

Users and roles with access to stored procedures

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.