DBMS > Graph Engine vs. Heroic vs. IRONdb vs. SAP Advantage Database Server vs. Snowflake

System Properties Comparison Graph Engine vs. Heroic vs. IRONdb vs. SAP Advantage Database Server vs. Snowflake

Editorial information provided by DB-Engines

Name

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

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

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

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

Primary database model

Graph DBMS
Key-value store

Time Series DBMS

Relational DBMS

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

Score	0.56
Rank	#241	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

www.graphengine.io

github.com/spotify/heroic

www.circonus.com/solutions/time-series-database/

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

www.snowflake.com

Technical documentation

www.graphengine.io/docs/manual

spotify.github.io/heroic

docs.circonus.com/irondb/category/getting-started

docs.snowflake.net/manuals/index.html

Developer

Microsoft

Spotify

Circonus LLC.

Sybase, SAP

Snowflake Computing Inc.

Initial release

2010

2014

2017

1993

2014

Current release

V0.10.20, January 2018

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

commercial

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

.NET and C

Java

C and C++

Server operating systems

.NET

Linux

Linux
Windows

hosted

Data scheme

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

RESTful HTTP API

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

HTTP API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

C#
C++
F#
Visual Basic

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Delphi
Perl
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

yes, in Lua

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Automatic, metric affinity per node

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

configurable replication factor, datacenter aware

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

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 per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

In-memory capabilities

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

yes

caching of (temporary) tables can be configured

User concepts

Access control

fine grained access rights according to SQL-standard

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

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.