DBMS > Faircom DB vs. Google Cloud Bigtable vs. mSQL vs. MySQL

System Properties Comparison Faircom DB vs. Google Cloud Bigtable vs. mSQL vs. MySQL

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.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used open source RDBMS

Primary database model

Key-value store
Relational DBMS

Key-value store
Wide column store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

www.faircom.com/products/faircom-db

cloud.google.com/bigtable

hughestech.com.au/products/msql

www.mysql.com

Technical documentation

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

cloud.google.com/bigtable/docs

dev.mysql.com/doc

Developer

FairCom Corporation

Google

Hughes Technologies

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

1979

2015

1994

1995

Current release

V12, November 2020

4.4, October 2021

8.4.0, April 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

free licenses can be provided

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

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

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

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

schema-free

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

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

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

C#
C++
Go
Java
JavaScript (Node.js)
Python

C
C++
Delphi
Java
Perl
PHP
Tcl

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

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

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

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

Internal replication in Colossus, and regional replication between two clusters in different zones

none

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

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

none

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

tunable from ACID to Eventually Consistent

Atomic single-row operations

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

User concepts

Access control

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.