DBMS > Axibase vs. EJDB vs. RavenDB vs. Transbase

System Properties Comparison Axibase vs. EJDB vs. RavenDB vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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)

Open Source Operational and Transactional Enterprise NoSQL Document Database

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Time Series DBMS

Document store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

axibase.com/docs/atsd/finance

github.com/Softmotions/ejdb

ravendb.net

www.transaction.de/en/products/transbase.html

Technical documentation

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

ravendb.net/docs

www.transaction.de/en/products/transbase/features.html

Developer

Axibase Corporation

Softmotions

Hibernating Rhinos

Transaction Software GmbH

Initial release

2013

2012

2010

1987

Current release

15585

5.4, July 2022

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

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

Open Source

GPLv2

Open Source

AGPL version 3, commercial license available

commercial

free development license

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

Server operating systems

Linux

server-less

Linux
macOS
Raspberry Pi
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

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

SQL-like query language (RQL)

yes

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

in-process shared library

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native 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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID, Cluster-wide transaction available

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.

User concepts

Access control

Authorization levels configured per client per database

fine grained access rights according to SQL-standard

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

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

RavenDB Launches Version 6.0 Lightning Fast Queries, Data Integrations, Corax Indexing Engine, and Sharding
3 October 2023, PR Newswire

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

Oren Eini on RavenDB, Including Consistency Guarantees and C# as the Implementation Language
23 May 2022, InfoQ.com

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

How I Created a RavenDB Python Client
23 September 2016, Visual Studio Magazine

provided by Google News

Share this page