DBMS > Apache Druid vs. Heroic vs. SAP Advantage Database Server vs. Snowflake vs. VictoriaMetrics

System Properties Comparison Apache Druid vs. Heroic vs. SAP Advantage Database Server vs. Snowflake vs. VictoriaMetrics

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

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Relational DBMS
Time Series DBMS

Time Series DBMS

Relational DBMS

Time Series DBMS

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

Score	2.85
Rank	#96	Overall
	#50	Relational DBMS
	#6	Time Series DBMS

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	1.23
Rank	#165	Overall
	#15	Time Series DBMS

Website

druid.apache.org

github.com/spotify/heroic

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

www.snowflake.com

victoriametrics.com

Technical documentation

druid.apache.org/docs/latest/design

spotify.github.io/heroic

docs.snowflake.net/manuals/index.html

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Apache Software Foundation and contributors

Spotify

Sybase, SAP

Snowflake Computing Inc.

VictoriaMetrics

Initial release

2012

2014

1993

2014

2018

Current release

30.0.0, June 2024

v1.91, May 2023

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache 2.0

commercial

Open Source

Apache Version 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

Server operating systems

Linux
OS X
Unix

Linux
Windows

hosted

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

schema-less columns are supported

schema-free

yes

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

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL for querying

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

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

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Delphi
Perl
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual 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 capabilities

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

caching of (temporary) tables can be configured

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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.