DBMS > Apache Druid vs. Manticore Search vs. Quasardb vs. Snowflake vs. Tarantool

System Properties Comparison Apache Druid vs. Manticore Search vs. Quasardb vs. Snowflake vs. Tarantool

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

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

Distributed, high-performance timeseries database

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS
Time Series DBMS

Search engine

Time Series DBMS

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Spatial DBMS

with Tarantool/GIS extension

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.29
Rank	#302	Overall
	#21	Search engines

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

Technical documentation

druid.apache.org/docs/latest/design

manual.manticoresearch.com

doc.quasar.ai/master

docs.snowflake.net/manuals/index.html

www.tarantool.io/en/doc

Developer

Apache Software Foundation and contributors

Manticore Software

quasardb

Snowflake Computing Inc.

Initial release

2012

2017

2009

2014

2008

Current release

29.0.1, April 2024

6.0, February 2023

3.14.1, January 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

GPL version 2

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C and C++

Server operating systems

Linux
OS X
Unix

FreeBSD
Linux
macOS
Windows

BSD
Linux
OS X
Windows

hosted

BSD
Linux
macOS

Data scheme

yes

schema-less columns are supported

Fixed schema

schema-free

yes

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

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

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

yes

integer and binary

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

yes

with tags

yes

SQL

Support of SQL

SQL for querying

SQL-like query language

yes

Full-featured ANSI SQL support

APIs and other access methods

JDBC
RESTful HTTP/JSON API

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

HTTP API

CLI Client
JDBC
ODBC

Open binary protocol

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

JavaScript (Node.js)
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

user defined functions

Lua, C and SQL stored procedures

Triggers

similar concept for controling cloud resources

yes, before/after data modification events, on replication events, client session events

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

Sharding

consistent hashing

yes

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Synchronous replication based on Galera library

Source-replica replication with selectable replication factor

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

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

yes

by using LevelDB

yes

yes, write ahead logging

In-memory capabilities

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

yes

Transient mode

yes, full featured in-memory storage engine with persistence

User concepts

Access control

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

Cryptographically strong user authentication and audit trail

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

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.