DBMS > Geode vs. Microsoft Access vs. MySQL vs. Oracle NoSQL vs. Tarantool

System Properties Comparison Geode vs. Microsoft Access vs. MySQL vs. Oracle NoSQL vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

geode.apache.org

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

www.mysql.com

www.oracle.com/database/nosql/technologies/nosql

www.tarantool.io

Technical documentation

geode.apache.org/docs

developer.microsoft.com/en-us/access

dev.mysql.com/doc

docs.oracle.com/en/database/other-databases/nosql-database/index.html

www.tarantool.io/en/doc

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

Initial release

2002

1992

1995

2011

2008

Current release

1.1, February 2017

1902 (16.0.11328.20222), March 2019

8.4.0, April 2024

24.1, May 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Bundled with Microsoft Office

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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++

C and C++

Java

C and C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Solaris SPARC/x86

BSD
Linux
macOS

Data scheme

schema-free

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

optional

string, double, decimal, uuid, integer, blob, boolean, datetime

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

SQL-like query language (OQL)

yes

but not compliant to any SQL standard

yes

with proprietary extensions

SQL-like DML and DDL statements

Full-featured ANSI SQL support

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

Open binary protocol

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

C
C#
Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

user defined functions

yes

since Access 2010 using the ACE-engine

yes

proprietary syntax

Lua, C and SQL stored procedures

Triggers

yes

Cache Event Listeners

yes

since Access 2010 using the ACE-engine

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Multi-source replication
Source-replica replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

yes, on a single node

ACID

but no files for transaction logging

ACID

not for MyISAM storage engine

configurable

ACID within a storage node (=shard)

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

off heap cache

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access rights per client and object definable

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

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and 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.