DBMS > Heroic vs. SAP Advantage Database Server vs. Snowflake vs. Tarantool vs. TinkerGraph

System Properties Comparison Heroic vs. SAP Advantage Database Server vs. Snowflake vs. Tarantool vs. TinkerGraph

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Low-cost RDBMS with access to ISAM and FoxPro data structures

Cloud-based data warehousing service for structured and semi-structured data

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

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Time Series DBMS

Relational DBMS

Document store
Key-value store
Relational DBMS

Graph DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

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

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

github.com/spotify/heroic

www.sap.com/products/advantage-database-server.html

www.snowflake.com

www.tarantool.io

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

spotify.github.io/heroic

docs.snowflake.net/manuals/index.html

www.tarantool.io/en/doc

Developer

Spotify

Sybase, SAP

Snowflake Computing Inc.

Initial release

2014

1993

2014

2008

2009

Current release

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

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

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C and C++

Java

Server operating systems

Linux
Windows

hosted

BSD
Linux
macOS

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

schema-free

Typing

predefined data types such as float or date

yes

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

Full-featured ANSI SQL support

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Open binary protocol

TinkerPop 3

Supported programming languages

Delphi
Perl
PHP

JavaScript (Node.js)
Python

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

Groovy
Java

Server-side scripts

Stored procedures

yes

user defined functions

Lua, C and SQL stored procedures

Triggers

yes

similar concept for controling cloud resources

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

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

none

Foreign keys

Referential integrity

yes

Relationships in graphs

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

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

optional

In-memory capabilities

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

caching of (temporary) tables can be configured

yes, full featured in-memory storage engine with persistence

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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

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.