DBMS > Faircom DB vs. Google Cloud Bigtable vs. Hazelcast vs. Microsoft SQL Server

System Properties Comparison Faircom DB vs. Google Cloud Bigtable vs. Hazelcast vs. Microsoft SQL Server

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.

A widely adopted in-memory data grid

Microsofts flagship relational DBMS

Primary database model

Key-value store
Relational DBMS

Key-value store
Wide column store

Key-value store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS
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	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

www.faircom.com/products/faircom-db

cloud.google.com/bigtable

hazelcast.com

www.microsoft.com/en-us/sql-server

Technical documentation

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

cloud.google.com/bigtable/docs

hazelcast.org/imdg/docs

learn.microsoft.com/en-US/sql/sql-server

Developer

FairCom Corporation

Google

Hazelcast

Microsoft

Initial release

1979

2015

2008

1989

Current release

V12, November 2020

5.3.6, November 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

restricted free version is 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.

Implementation language

ANSI C, C++

Java

C++

Server operating systems

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

easily portable to other OSs

hosted

All OS with a Java VM

Linux
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

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

SQL-like query language

yes

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)

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

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

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

Event Listeners, Executor Services

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

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

yes

Replicated Map

yes, but depending on the SQL-Server Edition

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)

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

Atomic single-row operations

one or two-phase-commit; repeatable reads; read commited

ACID

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

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)

Role-based access control

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.