DBMS > EsgynDB vs. Geode vs. Microsoft Access vs. Realm vs. Snowflake

System Properties Comparison EsgynDB vs. Geode vs. Microsoft Access vs. Realm vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

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

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.esgyn.cn

geode.apache.org

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

realm.io

www.snowflake.com

Technical documentation

geode.apache.org/docs

developer.microsoft.com/en-us/access

realm.io/docs

docs.snowflake.net/manuals/index.html

Developer

Esgyn

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

Microsoft

Realm, acquired by MongoDB in May 2019

Snowflake Computing Inc.

Initial release

2015

2002

1992

2014

Current release

1.1, February 2017

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Bundled with Microsoft Office

Open Source

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

C++, Java

Java

C++

Server operating systems

Linux

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

Android
Backend: server-less
iOS
Windows

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

SQL

Support of SQL

yes

SQL-like query language (OQL)

yes

but not compliant to any SQL standard

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

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

.Net
Java

with Android only
Objective-C
React Native
Swift

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

yes

since Access 2010 using the ACE-engine

runs within the applications so server-side scripts are unnecessary

user defined functions

Triggers

yes

Cache Event Listeners

yes

since Access 2010 using the ACE-engine

yes

Change Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Multi-source replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

yes, on a single node

ACID

but no files for transaction logging

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

In-Memory realm

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights per client and object definable

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

yes

Users with fine-grained authorization concept, user roles and pluggable 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.