DBMS > BoltDB vs. Heroic vs. Microsoft Azure SQL Database vs. Snowflake vs. SWC-DB

System Properties Comparison BoltDB vs. Heroic vs. Microsoft Azure SQL Database vs. Snowflake vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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

Database as a Service offering with high compatibility to Microsoft SQL Server

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

A high performance, scalable Wide Column DBMS

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Time Series DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

github.com/boltdb/bolt

github.com/spotify/heroic

azure.microsoft.com/en-us/products/azure-sql/database

www.snowflake.com

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

spotify.github.io/heroic

docs.microsoft.com/en-us/azure/azure-sql

docs.snowflake.net/manuals/index.html

Developer

Spotify

Microsoft

Snowflake Computing Inc.

Alex Kashirin

Initial release

2013

2014

2010

2014

2020

Current release

V12

0.5, April 2021

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

commercial

Open Source

GPL 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

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

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

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

SQL-like query language

APIs and other access methods

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

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Proprietary protocol
Thrift

Supported programming languages

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

C++

Server-side scripts

Stored procedures

Transact SQL

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

yes, with always 3 replicas available

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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

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.