DBMS > BigObject vs. RavenDB vs. Transbase vs. Yanza

System Properties Comparison BigObject vs. RavenDB vs. Transbase vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Analytic DBMS for real-time computations and queries

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store

Relational DBMS

Time Series 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.13
Rank	#342	Overall
	#150	Relational DBMS

Score	3.01
Rank	#101	Overall
	#17	Document stores

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

bigobject.io

ravendb.net

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

yanza.com

Technical documentation

docs.bigobject.io

ravendb.net/docs

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

Developer

BigObject, Inc.

Hibernating Rhinos

Transaction Software GmbH

Yanza

Initial release

2015

2010

1987

2015

Current release

5.4, July 2022

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

free community edition available

Open Source

AGPL version 3, commercial license available

commercial

free development license

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux
macOS
Raspberry Pi
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Windows

Data scheme

yes

schema-free

yes

schema-free

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

SQL-like DML and DDL statements

SQL-like query language (RQL)

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP 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

HTTP API

Supported programming languages

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

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

Lua

yes

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

automatically between fact table and dimension tables

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 lock on objects (tables, trees)

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

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

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

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

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

RavenDB Adds Graph Queries
15 May 2019, Datanami

provided by Google News

Share this page