DBMS > GridGain vs. jBASE vs. SQLite vs. VelocityDB

System Properties Comparison GridGain vs. jBASE vs. SQLite vs. VelocityDB

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

A robust multi-value DBMS comprising development tools and middleware

Widely used embeddable, in-process RDBMS

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Multivalue DBMS

Relational DBMS

Graph DBMS
Object oriented DBMS

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

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	1.36
Rank	#157	Overall
	#3	Multivalue DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.00
Rank	#385	Overall
	#40	Graph DBMS
	#21	Object oriented DBMS

Website

www.gridgain.com

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

www.sqlite.org

velocitydb.com

Technical documentation

www.gridgain.com/docs/index.html

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

www.sqlite.org/docs.html

velocitydb.com/UserGuide

Developer

GridGain Systems, Inc.

Rocket Software (formerly Zumasys)

Dwayne Richard Hipp

VelocityDB Inc

Initial release

2007

1991

2000

2011

Current release

GridGain 8.5.1

5.7

3.46.1 (13 August 2024), August 2024

7.x

License

Commercial or Open Source

commercial, open source

commercial

Open Source

Public Domain

commercial

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, Python, REST, SQL

Server operating systems

Linux
OS X
Solaris
Windows
z/OS

AIX
Linux
Windows

server-less

Any that supports .NET

Data scheme

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

optional

yes

not rigid because of 'dynamic typing' concept.

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

Embedded SQL for jBASE in BASIC

yes

SQL-92 is not fully supported

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.Net

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
Basic
Jabbascript
Java

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

Server-side scripts

Stored procedures

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

yes

Triggers

yes (cache interceptors and events)

yes

Callbacks are triggered when data changes

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)

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

yes

Durability

Support for making data persistent

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

Role-based access control
Security Hooks for custom implementations

Access rights can be defined down to the item level

Based on Windows 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.