DBMS > Faircom DB vs. GreptimeDB vs. Machbase Neo vs. RocksDB vs. Tarantool

System Properties Comparison Faircom DB vs. GreptimeDB vs. Machbase Neo vs. RocksDB vs. Tarantool

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.

An open source Time Series DBMS built for increased scalability, high performance and efficiency

TimeSeries DBMS for AIoT and BigData

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Key-value store

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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.06
Rank	#352	Overall
	#33	Time Series DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

www.faircom.com/products/faircom-db

Technical documentation

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

docs.greptime.com

machbase.com/dbms

github.com/facebook/rocksdb/wiki

www.tarantool.io/en/doc

Developer

FairCom Corporation

Greptime Inc.

Machbase

Facebook, Inc.

Initial release

1979

2022

2013

2008

Current release

V12, November 2020

V8.0, August 2023

8.11.4, April 2024

2.10.0, May 2022

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache Version 2.0

commercial

free test version available

Open Source

BSD

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

ANSI C, C++

Rust

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

Android
Docker
FreeBSD
Linux
macOS
Windows

Linux
macOS
Windows

Linux

BSD
Linux
macOS

Data scheme

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

schema-free, schema definition possible

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

yes, ANSI SQL with proprietary extensions

yes

SQL-like query language

Full-featured ANSI SQL support

APIs and other access methods

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

gRPC
HTTP API
JDBC

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

C++ API
Java API

Open binary protocol

Supported programming languages

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

C++
Erlang
Go
Java
JavaScript

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Python

Lua, C and SQL stored procedures

Triggers

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

horizontal partitioning

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

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

selectable replication factor

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

yes

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

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

yes

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

volatile and lookup table

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

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

Simple rights management via user accounts

simple password-based access control

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

More information provided by the system vendor

Specific characteristics

GreptimeDB is a SQL & Python-enabled timeseries database system built from scratch...
» more

Competitive advantages

- Inherits advantages of Rust, such as excellent performance, memory safe, resource...
» more

Typical application scenarios

For IoT industries, GreptimeDB can seamless integrate with message queues and other...
» more

Key customers

Greptime's clients span multiple sectors including IoT, connected vehicles, and energy...
» more

Market metrics

GreptimeDB has garnered global recognition by topping GitHub trends following its...
» more

Licensing and pricing models

GreptimeDB: open source, distributed, cloud-native TSDB; supports Hybrid Time-series...
» 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.