DBMS > Faircom EDGE vs. GBase vs. Ignite vs. Riak KV vs. RocksDB

System Properties Comparison Faircom EDGE vs. GBase vs. Ignite vs. Riak KV vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

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

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Distributed, fault tolerant key-value store

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Key-value store
Relational DBMS

Key-value store

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

Key-value store

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.07
Rank	#185	Overall
	#86	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

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

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.faircom.com/products/faircom-edge

www.gbase.cn

ignite.apache.org

rocksdb.org

Technical documentation

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

apacheignite.readme.io/docs

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

github.com/facebook/rocksdb/wiki

Developer

FairCom Corporation

General Data Technology Co., Ltd.

Apache Software Foundation

OpenSource, formerly Basho Technologies

Facebook, Inc.

Initial release

1979

2004

2015

2009

2013

Current release

V3, October 2020

GBase 8a, GBase 8s, GBase 8c

Apache Ignite 2.6

3.2.0, December 2022

8.11.4, April 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

Apache 2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

BSD

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.

Implementation language

ANSI C, C++

C, Java, Python

C++, Java, .Net

Erlang

C++

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

Linux

Linux
OS X
Solaris
Windows

Linux
OS X

Linux

Data scheme

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

yes

schema-free

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

SQL

Support of SQL

yes

ANSI SQL queries

Standard with numerous extensions

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

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

ADO.NET
C API
JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

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

C#
C++
Java
PHP
Python
Ruby
Scala

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions

yes (compute grid and cache interceptors can be used instead)

Erlang

Triggers

yes

yes (cache interceptors and events)

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

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

Sharding

no "single point of failure"

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

yes

yes (replicated cache)

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

links between data sets can be stored

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

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.

yes

Security Hooks for custom implementations

yes, using Riak Security

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.