DBMS > Drizzle vs. GeoMesa vs. Heroic vs. Percona Server for MySQL vs. Warp 10

System Properties Comparison Drizzle vs. GeoMesa vs. Heroic vs. Percona Server for MySQL vs. Warp 10

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.

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

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	2.03
Rank	#122	Overall
	#57	Relational DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

www.geomesa.org

github.com/spotify/heroic

www.percona.com/software/mysql-database/percona-server

www.warp10.io

Technical documentation

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

spotify.github.io/heroic

www.percona.com/downloads/Percona-Server-LATEST

www.warp10.io/content/02_Getting_started

Developer

Drizzle project, originally started by Brian Aker

CCRi and others

Spotify

Percona

SenX

Initial release

2008

2014

2008

2015

Current release

7.2.4, September 2012

4.0.5, February 2024

8.0.36-28, 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

GPL version 2

Open Source

Apache License 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.

Implementation language

C++

Scala

Java

C and C++

Java

Server operating systems

FreeBSD
Linux
OS X

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

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

ADO.NET
JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

C
C++
Java
PHP

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

WarpScript

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

depending on storage layer

yes

Multi-source replication
Source-replica replication
XtraDB Cluster

selectable replication factor

based on HBase

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
Immediate Consistency

Immediate Consistency

based on HBase

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

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

Users with fine-grained authorization concept

no user groups or roles

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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

Recent citations in the news

A Momentous 2023, Headlined by a 19% increase of ARR, Positions Percona for Even Greater Success in the Year ...
27 March 2024, Business Wire

Update or migrate? Planning for MySQL 5.7 EOL
22 June 2023, InfoWorld

Sizing Up Servers: Intel's Skylake-SP Xeon versus AMD's EPYC 7000 - The Server CPU Battle of the Decade?
11 July 2017, AnandTech

ScaleFlux computational storage makes Percona MySQL faster – Blocks and Files
5 August 2020, Blocks & Files

How to deploy the Percona database performance monitor with Docker
24 February 2023, TechRepublic

provided by Google News

Time Series Intelligence Software Market Business Insights, Key Trend Analysis | Google, SAP, Azure Time Series ...
24 April 2024, Amoré

Time Series Intelligence Software Market Analysis and Revenue Prediction | Azure Time Series Insights, Trendalyze ...
20 May 2024, Weekly Post Gazette

provided by Google News

Share this page