DBMS > GridGain vs. Interbase vs. Microsoft Access vs. PouchDB vs. RocksDB

System Properties Comparison GridGain vs. Interbase vs. Microsoft Access vs. PouchDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

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

Light-weight proven RDBMS

originally from Borland

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

JavaScript DBMS with an API inspired by CouchDB

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Document store

Key-value store

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	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.gridgain.com

www.embarcadero.com/products/interbase

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

pouchdb.com

rocksdb.org

Technical documentation

www.gridgain.com/docs/index.html

docs.embarcadero.com/products/interbase

developer.microsoft.com/en-us/access

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

Developer

GridGain Systems, Inc.

Embarcadero

Microsoft

Apache Software Foundation

Facebook, Inc.

Initial release

2007

1984

1992

2012

2013

Current release

GridGain 8.5.1

InterBase 2020, December 2019

1902 (16.0.11328.20222), March 2019

7.1.1, June 2019

8.11.4, April 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

BSD

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

C++

JavaScript

C++

Server operating systems

Linux
OS X
Solaris
Windows

Android
iOS
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

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

Linux

Data scheme

yes

schema-free

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

export as XML data possible

Secondary indexes

yes

via views

SQL

Support of SQL

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

yes

but not compliant to any SQL standard

APIs and other access methods

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

ADO.NET
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

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

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

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

yes

Interbase procedure and trigger language

yes

since Access 2010 using the ACE-engine

View functions in JavaScript

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

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Interbase Change Views

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

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

Eventual 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

yes

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

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

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.