DBMS > Drizzle vs. GigaSpaces vs. RocksDB vs. VictoriaMetrics

System Properties Comparison Drizzle vs. GigaSpaces vs. RocksDB vs. VictoriaMetrics

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.

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Key-value store

Time Series DBMS

Secondary database models

Graph DBMS
Search engine

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

Score	1.03
Rank	#188	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	1.23
Rank	#172	Overall
	#15	Time Series DBMS

Website

www.gigaspaces.com

rocksdb.org

victoriametrics.com

Technical documentation

docs.gigaspaces.com/latest/landing.html

github.com/facebook/rocksdb/wiki

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

Developer

Drizzle project, originally started by Brian Aker

Gigaspaces Technologies

Facebook, Inc.

VictoriaMetrics

Initial release

2008

2000

2013

2018

Current release

7.2.4, September 2012

15.5, September 2020

9.2.1, May 2024

v1.91, May 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache Version 2; Commercial licenses available

Open Source

BSD

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++

Java, C++, .Net

C++

Server operating systems

FreeBSD
Linux
OS X

Linux
macOS
Solaris
Windows

Linux

FreeBSD
Linux
macOS
OpenBSD

Data scheme

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.

XML can be used for describing objects metadata

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-99 for query and DML statements

APIs and other access methods

JDBC

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

C++ API
Java API

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

Supported programming languages

C
C++
Java
PHP

.Net
C++
Java
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

hooks for callbacks inside the server can be used.

yes, event driven architecture

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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.

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Role-based access control

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.