DBMS > Snowflake vs. Stardog vs. TerarkDB vs. VictoriaMetrics

System Properties Comparison Snowflake vs. Stardog vs. TerarkDB vs. VictoriaMetrics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

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

Primary database model

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

www.snowflake.com

www.stardog.com

github.com/bytedance/terarkdb

victoriametrics.com

Technical documentation

docs.snowflake.net/manuals/index.html

docs.stardog.com

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

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

Developer

Snowflake Computing Inc.

Stardog-Union

ByteDance, originally Terark

VictoriaMetrics

Initial release

2014

2010

2016

2018

Current release

7.3.0, May 2020

v1.91, May 2023

License

Commercial or Open Source

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

commercial

restricted open source version available

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

C++

Server operating systems

hosted

Linux
macOS
Windows

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

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

schema-free and OWL/RDFS-schema support

schema-free

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

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

yes

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

CLI Client
JDBC
ODBC

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

C++ API
Java API

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

Supported programming languages

JavaScript (Node.js)
Python

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

C++
Java

Server-side scripts

Stored procedures

user defined functions

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

similar concept for controling cloud resources

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication in HA-Cluster

none

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in HA-Cluster

Eventual Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

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.

yes

User concepts

Access control

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

Access rights for 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.