DBMS > Faircom DB vs. Geode vs. Kingbase vs. MySQL vs. RRDtool

System Properties Comparison Faircom DB vs. Geode vs. Kingbase vs. MySQL vs. RRDtool

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

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

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

Widely used open source RDBMS

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

Key-value store
Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

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

Score	0.50
Rank	#257	Overall
	#119	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Website

www.faircom.com/products/faircom-db

geode.apache.org

www.kingbase.com.cn

www.mysql.com

oss.oetiker.ch/rrdtool

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

geode.apache.org/docs

dev.mysql.com/doc

oss.oetiker.ch/rrdtool/doc

Developer

FairCom Corporation

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

BeiJing KINGBASE Information technologies inc.

Oracle

since 2010, originally MySQL AB, then Sun

Tobias Oetiker

Initial release

1979

2002

1999

1995

1999

Current release

V12, November 2020

1.1, February 2017

V8.0, August 2021

8.4.0, April 2024

1.8.0, 2022

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V2 and FLOSS

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 Java

C and C++

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

All OS with a Java VM

the JDK (8 or later) is also required

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

HP-UX
Linux

Data scheme

schema free, schema optional, schema required, partial schema,

schema-free

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes

Numeric data only

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

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

SQL-like query language (OQL)

Standard with numerous extensions

yes

with proprietary extensions

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

ADO.NET
JDBC
ODBC
Proprietary native API

in-process shared library
Pipes

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

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

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

horizontal partitioning (by range, list and hash) and vertical partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Multi-source replication

yes

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
Tunable consistency per server, database, table, and transaction

Eventual Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

tunable from ACID to Eventually Consistent

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

by using the rrdcached daemon

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

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 access rights according to SQL-standard with additional protections for files

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.