DBMS > AgensGraph vs. KairosDB vs. RavenDB vs. Transbase

System Properties Comparison AgensGraph vs. KairosDB vs. RavenDB vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Distributed Time Series DBMS based on Cassandra or H2

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Primary database model

Graph DBMS
Relational DBMS

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.16
Rank	#333	Overall
	#30	Graph DBMS
	#146	Relational DBMS

Score	0.71
Rank	#230	Overall
	#20	Time Series DBMS

Score	3.01
Rank	#101	Overall
	#17	Document stores

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

bitnine.net/agensgraph

github.com/kairosdb/kairosdb

ravendb.net

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

Technical documentation

bitnine.net/documentation

kairosdb.github.io

ravendb.net/docs

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

Developer

Bitnine Global Inc.

Hibernating Rhinos

Transaction Software GmbH

Initial release

2016

2013

2010

1987

Current release

2.1, December 2018

1.2.2, November 2018

5.4, July 2022

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

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
OS X
Windows

Linux
macOS
Raspberry Pi
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

depending on used data model

schema-free

yes

Typing

predefined data types such as float or date

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

yes

SQL-like query language (RQL)

yes

APIs and other access methods

Cypher Query Language
JDBC

Graphite protocol
HTTP REST
Telnet API

.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

C
Java
JavaScript
Python

Java
JavaScript

Node.js
PHP
Python

.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

no, but can be realized using table inheritance

Sharding

based on Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

based on Cassandra

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

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

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.

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based 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

Graph DBMS Performance Comparison AgensGraph vs. Neo4j
29 June 2017, Business Wire

Bitnine Releases AgensGraph 2.1, the Multi-model Graph Database Optimized for the Legacy Environment
29 January 2019, Business Wire

provided by Google News

The re-emergence of time-series – O'Reilly
6 April 2013, oreilly.com

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

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

RavenDB Adds Graph Queries
15 May 2019, Datanami

Review: NoSQL database RavenDB
20 March 2019, TechGenix

provided by Google News

Share this page