DBMS > OrigoDB vs. SAP HANA vs. SiriDB vs. Tarantool vs. Yaacomo

System Properties Comparison OrigoDB vs. SAP HANA vs. SiriDB vs. Tarantool vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

A fully ACID in-memory object graph database

In-memory, column based data store. Available as appliance or cloud service

Open Source Time Series DBMS

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Object oriented DBMS

Relational DBMS

Time Series DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

origodb.com

www.sap.com/products/hana.html

siridb.com

www.tarantool.io

yaacomo.com

Technical documentation

origodb.com/docs

help.sap.com/hana

docs.siridb.com

www.tarantool.io/en/doc

Developer

Robert Friberg et al

SAP

Cesbit

Q2WEB GmbH

Initial release

2009

under the name LiveDB

2010

2017

2008

2009

Current release

2.0 SPS07 (April 4, 2023), April 2023

2.10.0, May 2022

License

Commercial or Open Source

Open Source

commercial

Open Source

MIT License

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

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
Windows

Appliance or cloud-service

Linux

BSD
Linux
macOS

Android
Linux
Windows

Data scheme

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

User defined using .NET types and collections

yes

Numeric data

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Full-featured ANSI SQL support

yes

APIs and other access methods

.NET Client API
HTTP API
LINQ

JDBC
ODBC

HTTP API

Open binary protocol

JDBC
ODBC

Supported programming languages

.Net

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

SQLScript, R

Lua, C and SQL stored procedures

Triggers

yes

Domain Events

yes

yes, before/after data modification events, on replication events, client session events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

yes

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

yes, write ahead logging

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

yes, full featured in-memory storage engine with persistence

yes

User concepts

Access control

Role based authorization

yes

simple rights management via user accounts

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.