DBMS > OrigoDB vs. SpatiaLite vs. Transbase vs. VoltDB vs. Yanza

System Properties Comparison OrigoDB vs. SpatiaLite vs. Transbase vs. VoltDB vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

A fully ACID in-memory object graph database

Spatial extension of SQLite

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Time Series DBMS for IoT Applications

Primary database model

Document store
Object oriented DBMS

Spatial DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

origodb.com

www.gaia-gis.it/fossil/libspatialite/index

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

www.voltdb.com

yanza.com

Technical documentation

origodb.com/docs

www.gaia-gis.it/gaia-sins/spatialite_topics.html

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

docs.voltdb.com

Developer

Robert Friberg et al

Alessandro Furieri

Transaction Software GmbH

VoltDB Inc.

Yanza

Initial release

2009

under the name LiveDB

2008

1987

2010

2015

Current release

5.0.0, August 2020

Transbase 8.3, 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

commercial

free development license

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C and C++

Java, C++

Server operating systems

Linux
Windows

server-less

FreeBSD
Linux
macOS
Solaris
Windows

Linux
OS X

for development

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

.NET Client API
HTTP API
LINQ

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
JDBC
RESTful HTTP/JSON API

HTTP API

Supported programming languages

.Net

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Domain Events

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Source-replica replication

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

Snapshots and command logging

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

Role based authorization

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page