DBMS > Axibase vs. EJDB vs. FatDB vs. RocksDB

System Properties Comparison Axibase vs. EJDB 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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Document store

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.31
Rank	#296	Overall
	#44	Document stores

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

Website

axibase.com/docs/atsd/finance

github.com/Softmotions/ejdb

rocksdb.org

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

github.com/facebook/rocksdb/wiki

Developer

Axibase Corporation

Softmotions

FatCloud

Facebook, Inc.

Initial release

2013

2012

2013

Current release

15585

9.2.1, May 2024

License

Commercial or Open Source

commercial

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

Open Source

GPLv2

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

Server operating systems

Linux

server-less

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

string, integer, double, bool, date, object_id

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

Via inetgration in SQL Server

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

in-process shared library

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

C++ API
Java API

Supported programming languages

Go
Java
PHP
Python
R
Ruby

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

via applications

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

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.