DBMS > Apache Druid vs. IBM Cloudant vs. SAP SQL Anywhere vs. Snowflake

System Properties Comparison Apache Druid vs. IBM Cloudant vs. SAP SQL Anywhere vs. Snowflake

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

Database as a Service offering based on Apache CouchDB

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

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

Primary database model

Relational DBMS
Time Series DBMS

Document store

Relational 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	2.73
Rank	#108	Overall
	#20	Document stores

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

druid.apache.org

www.ibm.com/products/cloudant

www.sap.com/products/technology-platform/sql-anywhere.html

www.snowflake.com

Technical documentation

druid.apache.org/docs/latest/design

cloud.ibm.com/docs/Cloudant

help.sap.com/docs/SAP_SQL_Anywhere

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation and contributors

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

SAP

formerly Sybase

Snowflake Computing Inc.

Initial release

2012

2010

1992

2014

Current release

29.0.1, April 2024

17, July 2015

License

Commercial or Open Source

Open Source

Apache license v2

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

Erlang

Server operating systems

Linux
OS X
Unix

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

hosted

Data scheme

yes

schema-less columns are supported

schema-free

yes

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

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

APIs and other access methods

JDBC
RESTful HTTP/JSON API

RESTful HTTP/JSON API

ADO.NET
HTTP API
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes, in C/C++, Java, .Net or Perl

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication
Source-replica replication

Source-replica replication

Database mirroring

yes

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

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.