DBMS > Faircom DB vs. GeoMesa vs. IBM Db2 warehouse vs. MySQL vs. PlanetScale

System Properties Comparison Faircom DB vs. GeoMesa vs. IBM Db2 warehouse vs. MySQL vs. PlanetScale

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.

Cloud-based data warehousing service

Widely used open source RDBMS

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Primary database model

Key-value store
Relational DBMS

Spatial DBMS

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.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1.37
Rank	#160	Overall
	#74	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Website

www.faircom.com/products/faircom-db

www.geomesa.org

www.ibm.com/products/db2/warehouse

www.mysql.com

planetscale.com

Technical documentation

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

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

dev.mysql.com/doc

planetscale.com/docs

Developer

FairCom Corporation

CCRi and others

IBM

Oracle

since 2010, originally MySQL AB, then Sun

PlanetScale

Initial release

1979

2014

1995

2020

Current release

V12, November 2020

5.0.0, May 2024

8.4.0, April 2024

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache License 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Cloud-based only

Only available as a cloud service

yes

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

Scala

C and C++

Server operating systems

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

easily portable to other OSs

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS

Data scheme

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

yes

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.

Import/export of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

with proprietary 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

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

PL/SQL, SQL PL

yes

proprietary syntax

yes

proprietary syntax

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

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

Multi-source replication
Source-replica replication

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

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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

ACID

not for MyISAM storage engine

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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.