DBMS > Faircom DB vs. Machbase Neo vs. RocksDB vs. Teradata Aster vs. Vitess

System Properties Comparison Faircom DB vs. Machbase Neo vs. RocksDB vs. Teradata Aster vs. Vitess

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

TimeSeries DBMS for AIoT and BigData

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

Platform for big data analytics on multistructured data sources and types

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Key-value store

Relational DBMS

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	0.12
Rank	#339	Overall
	#30	Time Series DBMS

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

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

www.faircom.com/products/faircom-db

machbase.com

rocksdb.org

vitess.io

Technical documentation

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

machbase.com/dbms

github.com/facebook/rocksdb/wiki

vitess.io/docs

Developer

FairCom Corporation

Machbase

Facebook, Inc.

Teradata

The Linux Foundation, PlanetScale

Initial release

1979

2013

2005

2013

Current release

V12, November 2020

V8.0, August 2023

8.11.4, April 2024

15.0.2, December 2022

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

free test version available

Open Source

BSD

commercial

Open Source

Apache Version 2.0, commercial licenses 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.

Implementation language

ANSI C, C++

C++

Server operating systems

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

easily portable to other OSs

Linux
macOS
Windows

Linux

Docker
Linux
macOS

Data scheme

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

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

SQL-like query language

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
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

C++ API
Java API

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Java
Python
R

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

R packages

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

horizontal partitioning

Sharding

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

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

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

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency across shards
Immediate Consistency within a shard

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

yes

ACID

ACID at shard level

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

volatile and lookup table

yes

User concepts

Access control

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

simple password-based access control

fine grained access rights according to SQL-standard

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.