DBMS > GridGain vs. Microsoft Access vs. Oracle Coherence vs. SQLite

System Properties Comparison GridGain vs. Microsoft Access vs. Oracle Coherence vs. SQLite

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Oracles in-memory data grid solution

Widely used embeddable, in-process RDBMS

Primary database model

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Key-value store

Relational 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	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	1.90
Rank	#127	Overall
	#21	Key-value stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

www.gridgain.com

www.microsoft.com/en-us/microsoft-365/access

www.oracle.com/java/coherence

www.sqlite.org

Technical documentation

www.gridgain.com/docs/index.html

developer.microsoft.com/en-us/access

docs.oracle.com/en/middleware/standalone/coherence

www.sqlite.org/docs.html

Developer

GridGain Systems, Inc.

Microsoft

Oracle

Dwayne Richard Hipp

Initial release

2007

1992

2007

2000

Current release

GridGain 8.5.1

1902 (16.0.11328.20222), March 2019

14.1, August 2023

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial, open source

commercial

Bundled with Microsoft Office

commercial

Open Source

Public Domain

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

C++

Java

Server operating systems

Linux
OS X
Solaris
Windows
z/OS

Windows

Not a real database server, but making use of DLLs

All OS with a Java VM

server-less

Data scheme

yes

schema-free

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

Secondary indexes

yes

SQL

Support of SQL

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

yes

but not compliant to any SQL standard

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

ADO.NET
DAO
ODBC
OLE DB

JCache
JPA
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

.Net
C++
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

Server-side scripts

Stored procedures

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

yes

since Access 2010 using the ACE-engine

Triggers

yes (cache interceptors and events)

yes

since Access 2010 using the ACE-engine

yes

Live Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

yes, with selectable consistency level

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

configurable

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

optionally

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

a simple user-level security was built in till version Access 2003

authentification to access the cache via certificates or http basic 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.