DBMS > Faircom DB vs. GeoMesa vs. IBM Db2 vs. RocksDB

System Properties Comparison Faircom DB vs. GeoMesa vs. IBM Db2 vs. RocksDB

Please select another system to include it in the comparison.

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.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Common in IBM host environments, 2 different versions for host and Windows/Linux

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

Primary database model

Key-value store
Relational DBMS

Spatial DBMS

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Key-value store

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

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

Website

www.faircom.com/products/faircom-db

www.geomesa.org

www.ibm.com/products/db2

rocksdb.org

Technical documentation

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

www.geomesa.org/documentation/stable/user/index.html

www.ibm.com/docs/en/db2

github.com/facebook/rocksdb/wiki

Developer

FairCom Corporation

CCRi and others

IBM

Facebook, Inc.

Initial release

1979

2014

1983

host version

2013

Current release

V12, November 2020

5.0.0, May 2024

12.1, October 2016

9.2.1, May 2024

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache License 2.0

commercial

free version is available

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

Scala

C and C++

C++

Server operating systems

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

easily portable to other OSs

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux

Data scheme

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

yes

schema-free

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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.

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

APIs and other access methods

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

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

C++ API
Java API

Supported programming languages

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

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

depending on storage layer

Sharding

only with Windows/Unix/Linux Version

horizontal partitioning

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).

depending on storage layer

yes

with separate tools (MQ, InfoSphere)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

depending on storage layer

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

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

depending on storage layer

yes

User concepts

Access control

Fine grained access rights according to SQL-standard with additional protections for files

yes

depending on the DBMS used for storage

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.