DBMS > Axibase vs. Brytlyt vs. FatDB vs. RocksDB

System Properties Comparison Axibase vs. Brytlyt vs. FatDB vs. RocksDB

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

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

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

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

Primary database model

Time Series DBMS

Relational DBMS

Document store
Key-value store

Key-value store

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

Score	0.35
Rank	#282	Overall
	#25	Time Series DBMS

Score	0.38
Rank	#276	Overall
	#127	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

axibase.com/docs/atsd/finance

brytlyt.io

rocksdb.org

Technical documentation

docs.brytlyt.io

github.com/facebook/rocksdb/wiki

Developer

Axibase Corporation

Brytlyt

FatCloud

Facebook, Inc.

Initial release

2013

2016

2012

2013

Current release

15585

5.0, August 2023

9.2.1, May 2024

License

Commercial or Open Source

commercial

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

commercial

Open Source

BSD

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

C, C++ and CUDA

C++

Server operating systems

Linux

Linux
OS X
Windows

Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

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

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

Via inetgration in SQL Server

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

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

C++ API
Java API

Supported programming languages

Go
Java
PHP
Python
R
Ruby

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

in PL/pgSQL

yes

via applications

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Can implement custom security layer via applications

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.