DBMS > Heroic vs. IBM Db2 warehouse vs. Snowflake vs. TerminusDB vs. VelocityDB

System Properties Comparison Heroic vs. IBM Db2 warehouse vs. Snowflake vs. TerminusDB vs. VelocityDB

Editorial information provided by DB-Engines

Name

Description

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

Cloud-based data warehousing service

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Time Series DBMS

Relational DBMS

Graph DBMS

Graph DBMS
Object oriented DBMS

Secondary database models

Document store
RDF store

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	1.37
Rank	#160	Overall
	#74	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Website

github.com/spotify/heroic

www.ibm.com/products/db2/warehouse

www.snowflake.com

terminusdb.com

velocitydb.com

Technical documentation

spotify.github.io/heroic

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

velocitydb.com/UserGuide

Developer

Spotify

IBM

Snowflake Computing Inc.

DataChemist Ltd.

VelocityDB Inc

Initial release

2014

2018

2011

Current release

11.0.0, January 2023

7.x

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL V3

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

Java

Prolog, Rust

Server operating systems

hosted

Linux

Any that supports .NET

Data scheme

schema-free

yes

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

yes

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.

Import/export of XML data possible

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

SQL-like query language (WOQL)

APIs and other access methods

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

.NET Client API
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

.Net

Supported programming languages

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

JavaScript (Node.js)
Python

JavaScript
Python

.Net

Server-side scripts

Stored procedures

PL/SQL, SQL PL

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Journaling Streams

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

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

yes

in-memory journaling

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

fine grained access rights according to SQL-standard

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

Role-based access control

Based on Windows 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.