DBMS > GridGain vs. LokiJS vs. Microsoft Access vs. MySQL

System Properties Comparison GridGain vs. LokiJS vs. Microsoft Access vs. MySQL

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

In-memory JavaScript DBMS

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.)

Widely used open source RDBMS

Primary database model

Key-value store
Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	1.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

Score	0.48
Rank	#262	Overall
	#42	Document stores

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Website

www.gridgain.com

github.com/techfort/LokiJS

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

www.mysql.com

Technical documentation

www.gridgain.com/docs/index.html

techfort.github.io/LokiJS

developer.microsoft.com/en-us/access

dev.mysql.com/doc

Developer

GridGain Systems, Inc.

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2007

2014

1992

1995

Current release

GridGain 8.5.1

1902 (16.0.11328.20222), March 2019

8.3.0, January 2024

License

Commercial or Open Source

commercial

Open Source

commercial

Bundled with Microsoft Office

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java, C++, .Net

JavaScript

C++

C and C++

Server operating systems

Linux
OS X
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

via views

yes

SQL

Support of SQL

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

yes

but not compliant to any SQL standard

yes

with proprietary extensions

APIs and other access methods

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

JavaScript API

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

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

View functions in JavaScript

yes

since Access 2010 using the ACE-engine

yes

proprietary syntax

Triggers

yes (cache interceptors and events)

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

atomic operations within a single collection possible

ACID

but no files for transaction logging

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

yes

but no files for transaction logging

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

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

Users with fine-grained authorization concept

no user groups or roles

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.