DBMS > Drizzle vs. GeoMesa vs. H2 vs. Splunk vs. VictoriaMetrics

System Properties Comparison Drizzle vs. GeoMesa vs. H2 vs. Splunk vs. VictoriaMetrics

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.

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Analytics Platform for Big Data

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Secondary database models

Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

Technical documentation

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

www.h2database.com/html/main.html

docs.splunk.com/Documentation/Splunk

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Drizzle project, originally started by Brian Aker

CCRi and others

Thomas Mueller

Splunk Inc.

VictoriaMetrics

Initial release

2008

2014

2005

2003

2018

Current release

7.2.4, September 2012

4.0.5, February 2024

2.2.220, July 2023

v1.91, May 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache License 2.0

Open Source

dual-licence (Mozilla public license, Eclipse public license)

commercial

Limited free edition and free developer edition available

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.

Implementation language

C++

Scala

Java

Server operating systems

FreeBSD
Linux
OS X

All OS with a Java VM

Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

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

SQL

Support of SQL

yes

with proprietary extensions

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC

JDBC
ODBC

HTTP REST

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

C
C++
Java
PHP

Java

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

yes

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

depending on storage layer

With clustering: 2 database servers on different computers operate on identical copies of a database

Multi-source replication

Synchronous 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

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

fine grained access rights according to SQL-standard

Access rights for users and 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.

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

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Recent citations in the news

OpenTelemetry Is Too Complicated, VictoriaMetrics Says
1 April 2024, Datanami

KubeCon24: VictoriaMetrics' Simpler Alternative to Prometheus
20 March 2024, The New Stack

How VictoriaMetrics' open source approach led to mass industry adoption
3 May 2024, Tech.eu

VictoriaMetrics Machine Learning takes monitoring to the next level
19 March 2024, Business Wire

VictoriaMetrics takes organic growth over investor pressure
11 December 2023, The Register

provided by Google News

Share this page