DBMS > Apache Drill vs. Axibase vs. Snowflake vs. SwayDB vs. VoltDB

System Properties Comparison Apache Drill vs. Axibase vs. Snowflake vs. SwayDB vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store
Relational DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

drill.apache.org

axibase.com/docs/atsd/finance

www.snowflake.com

swaydb.simer.au

www.voltdb.com

Technical documentation

drill.apache.org/docs

docs.snowflake.net/manuals/index.html

docs.voltdb.com

Developer

Apache Software Foundation

Axibase Corporation

Snowflake Computing Inc.

Simer Plaha

VoltDB Inc.

Initial release

2012

2013

2014

2018

2010

Current release

1.20.3, January 2023

15585

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

commercial

Open Source

GNU Affero GPL V3.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Scala

Java, C++

Server operating systems

Linux
OS X
Windows

Linux

hosted

Linux
OS X

for development

Data scheme

schema-free

yes

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

schema-free

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

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 SELECT statement is SQL:2003 compliant

SQL-like query language

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

CLI Client
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C++

Go
Java
PHP
Python
R
Ruby

JavaScript (Node.js)
Python

Java
Kotlin
Scala

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Java

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Atomic execution of operations

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

Depending on the underlying data source

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

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

Users and roles with access to stored procedures

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.