DBMS > Apache Drill vs. Apache Druid vs. Manticore Search vs. Snowflake

System Properties Comparison Apache Drill vs. Apache Druid vs. Manticore Search vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

Multi-storage database for search, including full-text search.

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

Primary database model

Document store
Relational DBMS

Relational DBMS
Time Series DBMS

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

Technical documentation

drill.apache.org/docs

druid.apache.org/docs/latest/design

manual.manticoresearch.com

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Apache Software Foundation and contributors

Manticore Software

Snowflake Computing Inc.

Initial release

2012

2017

2014

Current release

1.20.3, January 2023

29.0.1, April 2024

6.0, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache license v2

Open Source

GPL version 2

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

Server operating systems

Linux
OS X
Windows

Linux
OS X
Unix

FreeBSD
Linux
macOS
Windows

hosted

Data scheme

schema-free

yes

schema-less columns are supported

Fixed schema

yes

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

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL for querying

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
RESTful HTTP/JSON API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

CLI Client
JDBC
ODBC

Supported programming languages

C++

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

Partitioning is done manually, search queries against distributed index is supported

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Synchronous replication based on Galera library

yes

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

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

The original contents of fields are not stored in the Manticore index.

yes

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

User concepts

Access control

Depending on the underlying data source

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

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.