DBMS > Faircom DB vs. GeoMesa vs. Manticore Search vs. MySQL vs. OceanBase

System Properties Comparison Faircom DB vs. GeoMesa vs. Manticore Search vs. MySQL vs. OceanBase

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.

Multi-storage database for search, including full-text search.

Widely used open source RDBMS

A distributed, high available RDBMS compatible with Oracle and MySQL

Primary database model

Key-value store
Relational DBMS

Spatial DBMS

Search engine

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Spatial DBMS

Document store
Wide column store

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	0.22
Rank	#312	Overall
	#21	Search engines

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.66
Rank	#147	Overall
	#68	Relational DBMS

Website

www.faircom.com/products/faircom-db

Technical documentation

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

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

manual.manticoresearch.com

dev.mysql.com/doc

en.oceanbase.com/docs/oceanbase-database

Developer

FairCom Corporation

CCRi and others

Manticore Software

Oracle

since 2010, originally MySQL AB, then Sun

OceanBase

previously Alibaba and Ant Group

Initial release

1979

2014

2017

1995

2010

Current release

V12, November 2020

4.0.5, February 2024

6.0, February 2023

8.4.0, April 2024

4.3.0, April 2024

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache License 2.0

Open Source

GPL version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Commercial license available

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

Scala

C++

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

FreeBSD
Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

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

yes

Fixed schema

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

SQL-like query language

yes

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Proprietary native API
Table API

Supported programming languages

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

Elixir
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

Ada

in MySQL-compatible model
C

in Oracle- and MySQL- compatible models
C++

in Oracle- and MySQL- compatible models
D

in MySQL-compatible model
Delphi

in MySQL-compatible model
Eiffel

in MySQL-compatible model
Erlang

in MySQL-compatible model
Haskell

in MySQL-compatible model
Java

in Oracle- and MySQL- compatible models
JavaScript (Node.js)

in MySQL-compatible model
Objective-C

in MySQL-compatible model
OCaml

in MySQL-compatible model
Perl

in MySQL-compatible model
PHP

in MySQL-compatible model
Python

in MySQL-compatible model
Ruby

in MySQL-compatible model
Scheme

in MySQL-compatible model
Tcl

in MySQL-compatible model

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions

yes

proprietary syntax

PL/SQL in oracle-compatible mode, MySQL Stored Procedure in mysql-compatible mode

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

Partitioning is done manually, search queries against distributed index is supported

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning (by hash, key, range, range columns, list, and list columns)

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

Synchronous replication based on Galera library

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

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

yes

The original contents of fields are not stored in the Manticore index.

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

Users with fine-grained authorization concept

no user groups or roles

Access rights for users, groups and roles according to SQL-standard

More information provided by the system vendor

Specific characteristics

OceanBase Database is the world’s only native distributed database that has set new...
» more

Competitive advantages

High Availability : The five IDCs across three sites disaster recovery solution sets...
» more

Key customers

OceanBase Database has helped over 400 customers across industries upgrade their...
» more

Market metrics

TPC-C No.1 Performance , achieved a result of 707.35 million tpmC in the TPC-C benchmark...
» more

Licensing and pricing models

Mulan PubL v2 license for open source community edition. Commercial license for enterprise...
» more

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.