DBMS > Drizzle vs. Firebird vs. GridDB vs. Ingres vs. RocksDB

System Properties Comparison Drizzle vs. Firebird vs. GridDB vs. Ingres vs. RocksDB

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.

Firebird is an open source RDBMS forked from Borland's InterBase

Scalable in-memory time series database optimized for IoT and Big Data

Well established RDBMS

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

Primary database model

Secondary database models

Key-value store
Relational DBMS

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

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.firebirdsql.org

griddb.net

www.actian.com/databases/ingres

rocksdb.org

Technical documentation

www.firebirdsql.org/en/reference-manuals

docs.griddb.net

docs.actian.com/ingres

github.com/facebook/rocksdb/wiki

Developer

Drizzle project, originally started by Brian Aker

Firebird Foundation

Toshiba Corporation

Actian Corporation

Facebook, Inc.

Initial release

2008

2000

As fork of Borland's InterBase

2013

1974

originally developed at University Berkely in early 1970s

2013

Current release

7.2.4, September 2012

5.0.0, January 2024

5.1, August 2022

11.2, May 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Initial Developer's Public License

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

Open Source

BSD

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

C and C++

C++

Server operating systems

FreeBSD
Linux
OS X

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL92, SQL-like TQL (Toshiba Query Language)

yes

APIs and other access methods

JDBC

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

C++ API
Java API

Supported programming languages

C
C++
Java
PHP

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

PSQL

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

Ingres Replicator

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID at container level

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

yes

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.

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users with fine-grained authorization concept

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.