DBMS > Geode vs. MonetDB vs. MySQL vs. Spark SQL

System Properties Comparison Geode vs. MonetDB vs. MySQL vs. Spark SQL

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

A relational database management system that stores data in columns

Widely used open source RDBMS

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	1.72
Rank	#148	Overall
	#68	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	19.15
Rank	#33	Overall
	#20	Relational DBMS

Website

Technical documentation

geode.apache.org/docs

www.monetdb.org/Documentation

dev.mysql.com/doc

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

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

MonetDB BV

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

Initial release

2002

2004

1995

2014

Current release

1.1, February 2017

Dec2023 (11.49), December 2023

8.3.0, January 2024

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Mozilla Public License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

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

Scala

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

schema-free

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

SQL 2003 with some extensions

yes

with proprietary extensions

SQL-like DML and DDL statements

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

Supported programming languages

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

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java
Python
R
Scala

Server-side scripts

Stored procedures

user defined functions

yes, in SQL, C, R

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding via remote tables

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Source-replica replication available in experimental status

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes, on a single node

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or 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.