DBMS > BoltDB vs. EXASOL vs. Microsoft Azure Data Explorer vs. Snowflake

System Properties Comparison BoltDB vs. EXASOL vs. Microsoft Azure Data Explorer vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Fully managed big data interactive analytics platform

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

Primary database model

Key-value store

Relational DBMS

column oriented

Relational DBMS

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

github.com/boltdb/bolt

www.exasol.com

azure.microsoft.com/services/data-explorer

www.snowflake.com

Technical documentation

www.exasol.com/resources

docs.microsoft.com/en-us/azure/data-explorer

docs.snowflake.net/manuals/index.html

Developer

Exasol

Microsoft

Snowflake Computing Inc.

Initial release

2013

2000

2019

2014

Current release

cloud service with continuous releases

License

Commercial or Open Source

Open Source

MIT License

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Data scheme

schema-free

yes

Fixed schema with schema-less datatypes (dynamic)

yes

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

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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

all fields are automatically indexed

SQL

Support of SQL

yes

Kusto Query Language (KQL), SQL subset

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Yes, possible languages: KQL, Python, R

user defined functions

Triggers

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

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.

yes

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

Azure Active Directory Authentication

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.