DBMS > Heroic vs. Immudb vs. Snowflake vs. ToroDB

System Properties Comparison Heroic vs. Immudb vs. Snowflake vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB 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

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Relational DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.31
Rank	#295	Overall
	#42	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

github.com/spotify/heroic

github.com/codenotary/immudb
immudb.io

www.snowflake.com

github.com/torodb/server

Technical documentation

spotify.github.io/heroic

docs.immudb.io

docs.snowflake.net/manuals/index.html

Developer

Spotify

Codenotary

Snowflake Computing Inc.

8Kdata

Initial release

2014

2020

2014

2016

Current release

1.2.3, April 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2.0

commercial

Open Source

AGPL-V3

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

BSD
Linux
macOS
Solaris
Windows
z/OS

hosted

All OS with a Java 7 VM

Data scheme

schema-free

yes

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

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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 syntax

yes

APIs and other access methods

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

gRPC protocol
PostgreSQL wire protocol

CLI Client
JDBC
ODBC

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

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

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

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

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.