DBMS > Heroic vs. MySQL vs. Percona Server for MongoDB vs. Snowflake

System Properties Comparison Heroic vs. MySQL vs. Percona Server for MongoDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used open source RDBMS

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.50
Rank	#250	Overall
	#39	Document stores

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

github.com/spotify/heroic

www.mysql.com

www.percona.com/mongodb/software/percona-server-for-mongodb

www.snowflake.com

Technical documentation

spotify.github.io/heroic

dev.mysql.com/doc

docs.percona.com/percona-distribution-for-mongodb

docs.snowflake.net/manuals/index.html

Developer

Spotify

Oracle

since 2010, originally MySQL AB, then Sun

Percona

Snowflake Computing Inc.

Initial release

2014

1995

2015

2014

Current release

9.0.0, July 2024

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL Version 2

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

C and C++

C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux

hosted

Data scheme

schema-free

yes

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

yes

with proprietary extensions

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC
Proprietary native API

proprietary protocol using JSON

CLI Client
JDBC
ODBC

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

via In-Memory Engine

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and roles

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.