DBMS > Apache Druid vs. Graph Engine vs. Manticore Search vs. Microsoft Azure Cosmos DB

System Properties Comparison Apache Druid vs. Graph Engine vs. Manticore Search vs. Microsoft Azure Cosmos DB

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS
Time Series DBMS

Graph DBMS
Key-value store

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Spatial DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

druid.apache.org

www.graphengine.io

manticoresearch.com

azure.microsoft.com/services/cosmos-db

Technical documentation

druid.apache.org/docs/latest/design

www.graphengine.io/docs/manual

manual.manticoresearch.com

learn.microsoft.com/azure/cosmos-db

Developer

Apache Software Foundation and contributors

Microsoft

Manticore Software

Microsoft

Initial release

2012

2010

2017

2014

Current release

29.0.1, April 2024

6.0, February 2023

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

MIT License

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

.NET and C

C++

Server operating systems

Linux
OS X
Unix

.NET

FreeBSD
Linux
macOS
Windows

hosted

Data scheme

yes

schema-less columns are supported

yes

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

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

yes

JSON types

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

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL for querying

SQL-like query language

APIs and other access methods

JDBC
RESTful HTTP/JSON API

RESTful HTTP API

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

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
C++
F#
Visual Basic

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

user defined functions

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

horizontal partitioning

Sharding

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

Sharding

Implicit feature of the cloud service

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

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

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

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Access rights can be defined down to the item level

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.