DBMS > Apache Druid vs. Sadas Engine vs. Snowflake vs. SwayDB vs. Teradata

System Properties Comparison Apache Druid vs. Sadas Engine vs. Snowflake vs. SwayDB vs. Teradata

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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Key-value store

Relational DBMS

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	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

Technical documentation

druid.apache.org/docs/latest/design

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

docs.snowflake.net/manuals/index.html

docs.teradata.com

Developer

Apache Software Foundation and contributors

SADAS s.r.l.

Snowflake Computing Inc.

Simer Plaha

Teradata

Initial release

2012

2006

2014

2018

1984

Current release

29.0.1, April 2024

8.0

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

Apache license v2

commercial

free trial version available

commercial

Open Source

GNU Affero GPL V3.0

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++

Scala

Server operating systems

Linux
OS X
Unix

AIX
Linux
Windows

hosted

hosted
Linux

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

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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

SQL for querying

yes

SQL 2016 + extensions

APIs and other access methods

JDBC
RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol

CLI Client
JDBC
ODBC

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C
C#
C++
Groovy
Java
PHP
Python

JavaScript (Node.js)
Python

Java
Kotlin
Scala

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

UDFs, stored procedures, table functions in parallel

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

horizontal partitioning

yes

none

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

none

yes

none

Multi-source replication
Source-replica replication

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

Atomic execution of operations

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

managed by 'Learn by Usage'

yes

User concepts

Access control

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

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

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.