DBMS > Drizzle vs. GeoMesa vs. Heroic vs. Interbase vs. TimesTen

System Properties Comparison Drizzle vs. GeoMesa vs. Heroic vs. Interbase vs. TimesTen

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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Light-weight proven RDBMS

originally from Borland

In-Memory RDBMS compatible to Oracle

Primary database model

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

www.geomesa.org

github.com/spotify/heroic

www.embarcadero.com/products/interbase

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

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

spotify.github.io/heroic

docs.embarcadero.com/products/interbase

docs.oracle.com/database/timesten-18.1

Developer

Drizzle project, originally started by Brian Aker

CCRi and others

Spotify

Embarcadero

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2008

2014

1984

1998

Current release

7.2.4, September 2012

4.0.5, February 2024

InterBase 2020, December 2019

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

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

Android
iOS
Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

schema-free

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.

export as XML data possible

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

C
C++
Java
PHP

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

PL/SQL

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

depending on storage layer

yes

Interbase Change Views

Multi-source replication
Source-replica 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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

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

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

Recent citations in the news

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Borland InterBase backdoor detected | ZDNET
11 January 2001, ZDNet

An independent soccer league transforming lives in a slum in Kenya
15 November 2022, FanSided

Johnson Sakaja Donates KSh 200k to Support Cash Strapped Football Teams From Kibera - Tuko.co.ke
21 February 2024, Tuko.co.ke

Malaysian e-commerce firm Lelong.my acquires local digital marketing agency Mataris Agency
29 January 2018, Yahoo Singapore News

AHQ (Unit) Islamabad wins interbase shooting c’ship
11 February 2020, Pakistan Observer

provided by Google News

In-memory databases with Emulex Gen 7
25 October 2023, Broadcom Inc.

The Intel Xeon E7-8800 v3 Review: The POWER8 Killer?
8 May 2015, AnandTech

provided by Google News

Share this page