DBMS > Drizzle vs. GeoMesa vs. Hawkular Metrics vs. HBase

System Properties Comparison Drizzle vs. GeoMesa vs. Hawkular Metrics vs. HBase

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

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

Wide-column store based on Apache Hadoop and on concepts of BigTable

Primary database model

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.04
Rank	#374	Overall
	#38	Time Series DBMS

Score	31.25
Rank	#26	Overall
	#2	Wide column stores

Website

www.geomesa.org

www.hawkular.org

hbase.apache.org

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

www.hawkular.org/hawkular-metrics/docs/user-guide

hbase.apache.org/book.html

Developer

Drizzle project, originally started by Brian Aker

CCRi and others

Community supported by Red Hat

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Initial release

2008

2014

2008

Current release

7.2.4, September 2012

4.0.5, February 2024

2.3.4, January 2021

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

Apache version 2

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

C++

Scala

Java

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X
Windows

Linux
Unix
Windows

using Cygwin

Data scheme

yes

schema-free

schema-free, schema definition possible

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

JDBC

HTTP REST

Java API
RESTful HTTP API
Thrift

Supported programming languages

C
C++
Java
PHP

Go
Java
Python
Ruby

C
C#
C++
Groovy
Java
PHP
Python
Scala

Server-side scripts

Stored procedures

yes

Coprocessors in Java

Triggers

hooks for callbacks inside the server can be used.

yes

via Hawkular Alerting

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

based on Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

depending on storage layer

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency or Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Single row ACID (across millions of columns)

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

depending on the DBMS used for storage

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Cloudera's HBase PaaS offering now supports Complex Transactions
11 August 2021, Krishna Maheshwari (sponsor)

Why is Hadoop not listed in the DB-Engines Ranking?
13 May 2013, Paul Andlinger

show all

Recent citations in the news

Waiting for Red Hat OpenShift 4.0? Too late, 4.1 has already arrived… • DEVCLASS
5 June 2019, DevClass

provided by Google News

Best Practices from Rackspace for Modernizing a Legacy HBase/Solr Architecture Using AWS Services | Amazon Web ...
9 October 2023, AWS Blog

Less Components, Higher Performance: Apache Doris instead of ClickHouse, MySQL, Presto, and HBase
20 October 2023, hackernoon.com

Cloudera Search Adds Search Engine Ease to Data on HDFS and Apache HBase
10 December 2023, Channel Futures

HBase: The database big data left behind
6 May 2016, InfoWorld

What Is HBase? (Definition, Uses, Benefits, Features)
22 December 2022, Built In

provided by Google News

Share this page