DBMS > Apache Impala vs. GeoMesa vs. Memcached vs. MySQL vs. OpenTSDB

System Properties Comparison Apache Impala vs. GeoMesa vs. Memcached vs. MySQL vs. OpenTSDB

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

In-memory key-value store, originally intended for caching

Widely used open source RDBMS

Scalable Time Series DBMS based on HBase

Primary database model

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.68
Rank	#142	Overall
	#12	Time Series DBMS

Website

Technical documentation

impala.apache.org/impala-docs.html

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

github.com/memcached/memcached/wiki

dev.mysql.com/doc

opentsdb.net/docs/build/html/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

CCRi and others

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

since 2010, originally MySQL AB, then Sun

currently maintained by Yahoo and other contributors

Initial release

2013

2014

2003

1995

2011

Current release

4.1.0, June 2022

5.0.0, May 2024

1.6.27, May 2024

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache License 2.0

Open Source

BSD license

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

LGPL

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 MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

Scala

C and C++

Java

Server operating systems

Linux

FreeBSD
Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

Proprietary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Telnet API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Erlang
Go
Java
Python
R
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

depending on storage layer

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

depending on storage layer

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

yes

depending on the DBMS used for storage

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept

no user groups or roles

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.