DBMS > Faircom EDGE vs. Geode vs. MySQL vs. Riak KV vs. Trafodion

System Properties Comparison Faircom EDGE vs. Geode vs. MySQL vs. Riak KV vs. Trafodion

Editorial information provided by DB-Engines

Name

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

Description

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

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

Widely used open source RDBMS

Distributed, fault tolerant key-value store

Transactional SQL-on-Hadoop DBMS

Primary database model

Key-value store
Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

www.faircom.com/products/faircom-edge

geode.apache.org

www.mysql.com

trafodion.apache.org

Technical documentation

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

geode.apache.org/docs

dev.mysql.com/doc

www.tiot.jp/riak-docs/riak/kv/latest

trafodion.apache.org/documentation.html

Developer

FairCom Corporation

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

OpenSource, formerly Basho Technologies

Apache Software Foundation, originally developed by HP

Initial release

1979

2002

1995

2009

2014

Current release

V3, October 2020

1.1, February 2017

8.4.0, April 2024

3.2.0, December 2022

2.3.0, February 2019

License

Commercial or Open Source

commercial

Restricted, free version available

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 version 2, commercial enterprise edition

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

ANSI C, C++

Java

C and C++

Erlang

C++, Java

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

All OS with a Java VM

the JDK (8 or later) is also required

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X

Linux

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

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

restricted

yes

SQL

Support of SQL

yes

ANSI SQL queries

SQL-like query language (OQL)

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Native Erlang Interface

ADO.NET
JDBC
ODBC

Supported programming languages

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

.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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions

yes

proprietary syntax

Erlang

Java Stored Procedures

Triggers

yes

Cache Event Listeners

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

Multi-source replication

Multi-source replication
Source-replica replication

selectable replication factor

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

Immediate Consistency
Tunable Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

not for MyISAM storage engine

links between data sets can be stored

yes

Transaction concepts

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

ACID

yes, on a single node

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

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

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Access rights per client and object definable

Users with fine-grained authorization concept

no user groups or roles

yes, using Riak Security

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.