DBMS > Geode vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. Oracle NoSQL vs. SAP Adaptive Server

System Properties Comparison Geode vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. Oracle NoSQL vs. SAP Adaptive Server

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

Globally distributed, horizontally scalable, multi-model database service

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

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Primary database model

Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

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

Score	35.09
Rank	#25	Overall
	#17	Relational DBMS

Website

geode.apache.org

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

azure.microsoft.com/services/cosmos-db

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

www.sap.com/products/technology-platform/sybase-ase.html

Technical documentation

geode.apache.org/docs

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

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

help.sap.com/docs/SAP_ASE

Developer

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

Microsoft

Oracle

SAP, Sybase

Initial release

2002

1992

2014

2011

1987

Current release

1.1, February 2017

1902 (16.0.11328.20222), March 2019

24.1, May 2024

16.0

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Bundled with Microsoft Office

commercial

Open Source

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

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

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

hosted

Linux
Solaris SPARC/x86

AIX
HP-UX
Linux
Solaris
Unix
Windows

Data scheme

schema-free

yes

schema-free

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

yes

Typing

predefined data types such as float or date

yes

JSON types

optional

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

but not compliant to any SQL standard

SQL-like query language

SQL-like DML and DDL statements

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

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

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

C
C++
Cobol
Java
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

since Access 2010 using the ACE-engine

JavaScript

Java and Transact-SQL

Triggers

yes

Cache Event Listeners

yes

since Access 2010 using the ACE-engine

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

Implicit feature of the cloud service

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

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

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

Multi-item ACID transactions with snapshot isolation within a partition

configurable

ACID within a storage node (=shard)

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

off heap cache

User concepts

Access control

Access rights per client and object definable

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

Access rights can be defined down to the item level

Access rights for users and roles

fine grained access rights according to SQL-standard

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.