DBMS > Apache Druid vs. Microsoft SQL Server vs. Snowflake vs. Splunk

System Properties Comparison Apache Druid vs. Microsoft SQL Server vs. Snowflake vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Microsofts flagship relational DBMS

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

Analytics Platform for Big Data

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Search engine

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	88.71
Rank	#14	Overall
	#2	Search engines

Website

druid.apache.org

www.microsoft.com/en-us/sql-server

www.snowflake.com

www.splunk.com

Technical documentation

druid.apache.org/docs/latest/design

learn.microsoft.com/en-US/sql/sql-server

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation and contributors

Microsoft

Snowflake Computing Inc.

Splunk Inc.

Initial release

2012

1989

2014

2003

Current release

29.0.1, April 2024

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache license v2

commercial

restricted free version is available

commercial

Limited free edition and free developer edition available

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

Linux
OS X
Unix

Linux
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-less columns are supported

yes

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

yes

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

SQL

Support of SQL

SQL for querying

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

tables can be distributed across several files (horizontal partitioning); sharding through federation

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes, but depending on the SQL-Server Edition

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

fine grained access rights according to SQL-standard

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.