DBMS > Apache Phoenix vs. Faircom DB vs. Manticore Search vs. MySQL

System Properties Comparison Apache Phoenix vs. Faircom DB vs. Manticore Search vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

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

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

Widely used open source RDBMS

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Search engine

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Spatial DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

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

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

phoenix.apache.org

www.faircom.com/products/faircom-db

manticoresearch.com

www.mysql.com

Technical documentation

phoenix.apache.org

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

manual.manticoresearch.com

dev.mysql.com/doc

Developer

Apache Software Foundation

FairCom Corporation

Manticore Software

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2014

1979

2017

1995

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

V12, November 2020

6.0, February 2023

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Restricted, free version available

Open Source

GPL version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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

Java

ANSI C, C++

C++

C and C++

Server operating systems

Linux
Unix
Windows

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

Data scheme

yes

late-bound, schema-on-read capabilities

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

Fixed schema

yes

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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

yes, ANSI SQL with proprietary extensions

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JDBC

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

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.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

Server-side scripts

Stored procedures

user defined functions

yes

.Net, JavaScript, C/C++

user defined functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

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

Synchronous replication based on Galera library

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

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

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

tunable from ACID to Eventually Consistent

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

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

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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

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.