DBMS > Drizzle vs. jBASE vs. RavenDB vs. SQLite vs. VictoriaMetrics

System Properties Comparison Drizzle vs. jBASE vs. RavenDB vs. SQLite 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.

A robust multi-value DBMS comprising development tools and middleware

Open Source Operational and Transactional Enterprise NoSQL Document Database

Widely used embeddable, in-process RDBMS

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

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.23
Rank	#172	Overall
	#15	Time Series DBMS

Website

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

ravendb.net

www.sqlite.org

victoriametrics.com

Technical documentation

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

ravendb.net/docs

www.sqlite.org/docs.html

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

Developer

Drizzle project, originally started by Brian Aker

Rocket Software (formerly Zumasys)

Hibernating Rhinos

Dwayne Richard Hipp

VictoriaMetrics

Initial release

2008

1991

2010

2000

2018

Current release

7.2.4, September 2012

5.7

5.4, July 2022

3.46.0 (23 May 2024), May 2024

v1.91, May 2023

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

AGPL version 3, commercial license available

Open Source

Public Domain

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

Server operating systems

FreeBSD
Linux
OS X

AIX
Linux
Windows

Linux
macOS
Raspberry Pi
Windows

server-less

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

optional

yes

not rigid because of 'dynamic typing' concept.

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

Embedded SQL for jBASE in BASIC

SQL-like query language (RQL)

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

Supported programming languages

C
C++
Java
PHP

.Net
Basic
Jabbascript
Java

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Multi-source replication

none

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Access rights can be defined down to the item level

Authorization levels configured per client per database

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.