DBMS > Geode vs. Microsoft Access vs. Snowflake vs. Splice Machine

System Properties Comparison Geode vs. Microsoft Access vs. Snowflake vs. Splice Machine

Please select another system to include it in the comparison.

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

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Key-value store

Relational DBMS

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Website

geode.apache.org

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

www.snowflake.com

splicemachine.com

Technical documentation

geode.apache.org/docs

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

splicemachine.com/how-it-works

Developer

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

Microsoft

Snowflake Computing Inc.

Splice Machine

Initial release

2002

1992

2014

Current release

1.1, February 2017

1902 (16.0.11328.20222), March 2019

3.1, March 2021

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Bundled with Microsoft Office

commercial

Open Source

AGPL 3.0, commercial license available

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

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
OS X
Solaris
Windows

Data scheme

schema-free

yes

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

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

SQL

Support of SQL

SQL-like query language (OQL)

yes

but not compliant to any SQL standard

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

JDBC
Native Spark Datasource
ODBC

Supported programming languages

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

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

JavaScript (Node.js)
Python

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

user defined functions

yes

since Access 2010 using the ACE-engine

user defined functions

yes

Java

Triggers

yes

Cache Event Listeners

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

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, user roles and pluggable authentication

Access rights for users, groups and roles 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.