DBMS > Apache Druid vs. Snowflake vs. SWC-DB vs. TimescaleDB

System Properties Comparison Apache Druid vs. Snowflake vs. SWC-DB vs. TimescaleDB

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

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

A high performance, scalable Wide Column DBMS

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Wide column store

Time Series DBMS

Secondary database models

Time Series DBMS

Relational DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

druid.apache.org

www.snowflake.com

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

www.timescale.com

Technical documentation

druid.apache.org/docs/latest/design

docs.snowflake.net/manuals/index.html

docs.timescale.com

Developer

Apache Software Foundation and contributors

Snowflake Computing Inc.

Alex Kashirin

Timescale

Initial release

2012

2014

2020

2017

Current release

29.0.1, April 2024

0.5, April 2021

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

GPL V3

Open Source

Apache 2.0

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

hosted

Linux

Linux
OS X
Windows

Data scheme

yes

schema-less columns are supported

yes

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

schema-free

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Proprietary protocol
Thrift

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

JavaScript (Node.js)
Python

C++

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

yes

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

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

Users with fine-grained authorization concept, user roles and pluggable authentication

fine grained access rights according to SQL-standard

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.