DBMS > Axibase vs. Faircom DB vs. FatDB vs. GeoMesa

System Properties Comparison Axibase vs. Faircom DB vs. FatDB vs. GeoMesa

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Primary database model

Time Series DBMS

Key-value store
Relational DBMS

Document store
Key-value store

Spatial DBMS

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

Score	0.35
Rank	#282	Overall
	#25	Time Series DBMS

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Website

axibase.com/docs/atsd/finance

www.faircom.com/products/faircom-db

www.geomesa.org

Technical documentation

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

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

Developer

Axibase Corporation

FairCom Corporation

FatCloud

CCRi and others

Initial release

2013

1979

2012

2014

Current release

15585

V12, November 2020

5.0.0, May 2024

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

commercial

Restricted, free version available

commercial

Open Source

Apache License 2.0

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.

Implementation language

Java

ANSI C, C++

Scala

Server operating systems

Linux

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

easily portable to other OSs

Windows

Data scheme

yes

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

schema-free

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes, ANSI SQL with proprietary extensions

Via inetgration in SQL Server

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Supported programming languages

Go
Java
PHP
Python
R
Ruby

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

via applications

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

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

selectable replication factor

depending on storage layer

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

Eventual Consistency
Immediate Consistency

depending on storage layer

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

User concepts

Access control

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

Can implement custom security layer via applications

yes

depending on the DBMS used for storage

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

The Ultimate ATV Test: Suzuki's King Quad 750 AXI Rugged Package vs. Alaska's Hunting Season
20 April 2021, Outdoor Life

Time Series Databases Software Market - A comprehensive study by Key Players | Warp 10, Amazon Timestream ...
6 February 2020, openPR

provided by Google News

FairCom kicks off new era of database technology USA - English
10 November 2020, PR Newswire

World's First Converged IIoT Hub to be Showcased at IoT Tech Expo
3 September 2021, Automation.com

provided by Google News

Share this page