DBMS > Blueflood vs. Geode vs. MySQL vs. Trafodion

System Properties Comparison Blueflood vs. Geode vs. MySQL vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Scalable TimeSeries DBMS based on Cassandra

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

Widely used open source RDBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Time Series DBMS

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	0.06
Rank	#353	Overall
	#34	Time Series DBMS

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

github.com/rax-maas/blueflood/wiki

geode.apache.org/docs

dev.mysql.com/doc

trafodion.apache.org/documentation.html

Developer

Rackspace

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

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation, originally developed by HP

Initial release

2013

2002

1995

2014

Current release

1.1, February 2017

8.4.0, April 2024

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

C++, Java

Server operating systems

Linux
OS X

All OS with a Java VM

the JDK (8 or later) is also required

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

predefined 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

with proprietary extensions

yes

APIs and other access methods

HTTP REST

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
ODBC

Supported programming languages

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

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Java Stored Procedures

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication

Multi-source replication
Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Immediate Consistency

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

not for MyISAM storage engine

ACID

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

Users with fine-grained authorization concept

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