DBMS > Apache Druid vs. Manticore Search vs. Riak KV vs. SQLite vs. YottaDB

System Properties Comparison Apache Druid vs. Manticore Search vs. Riak KV vs. SQLite vs. YottaDB

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, fault tolerant key-value store

Widely used embeddable, in-process RDBMS

A fast and solid embedded Key-value store

Primary database model

Relational DBMS
Time Series DBMS

Search engine

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Key-value store

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Relational DBMS

using the Octo plugin

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	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

Technical documentation

druid.apache.org/docs/latest/design

manual.manticoresearch.com

www.tiot.jp/riak-docs/riak/kv/latest

www.sqlite.org/docs.html

yottadb.com/resources/documentation

Developer

Apache Software Foundation and contributors

Manticore Software

OpenSource, formerly Basho Technologies

Dwayne Richard Hipp

YottaDB, LLC

Initial release

2012

2017

2009

2000

2001

Current release

29.0.1, April 2024

6.0, February 2023

3.2.0, December 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

GPL version 2

Open Source

Apache version 2, commercial enterprise edition

Open Source

Public Domain

Open Source

AGPL 3.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Erlang

Server operating systems

Linux
OS X
Unix

FreeBSD
Linux
macOS
Windows

Linux
OS X

server-less

Docker
Linux

Data scheme

yes

schema-less columns are supported

Fixed schema

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

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

yes

not rigid because of 'dynamic typing' concept.

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

Secondary indexes

yes

full-text index on all search fields

restricted

yes

SQL

Support of SQL

SQL for querying

SQL-like query language

yes

SQL-92 is not fully supported

by using the Octo plugin

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
Native Erlang Interface

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

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

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Synchronous replication based on Galera library

selectable replication factor

none

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

Foreign keys

Referential integrity

links between data sets can be stored

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

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.

yes

User concepts

Access control

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

yes, using Riak Security

Users and groups based on OS-security mechanisms

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.