DBMS > Apache Drill vs. Drizzle vs. Heroic vs. OpenSearch

System Properties Comparison Apache Drill vs. Drizzle vs. Heroic vs. OpenSearch

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Primary database model

Document store
Relational DBMS

Relational DBMS

Time Series DBMS

Search engine

Secondary database models

Vector DBMS

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

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	15.65
Rank	#38	Overall
	#4	Search engines

Website

drill.apache.org

github.com/spotify/heroic

github.com/opensearch-project
opensearch.org

Technical documentation

drill.apache.org/docs

spotify.github.io/heroic

opensearch.org/docs/latest

Developer

Apache Software Foundation

Drizzle project, originally started by Brian Aker

Spotify

Amazon Web Services

Initial release

2012

2008

2014

2021

Current release

1.20.3, January 2023

7.2.4, September 2012

2.5.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GNU GPL

Open Source

Apache 2.0

Open Source

Apache Version 2.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.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

C++

Java

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X

All OS with a Java VM

Data scheme

schema-free

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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.

Secondary indexes

yes

via Elasticsearch

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Java API
RESTful HTTP/JSON API

Supported programming languages

C++

C
C++
Java
PHP

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

hooks for callbacks inside the server can be used.

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.