DBMS > Heroic vs. Interbase vs. MySQL vs. SpatiaLite vs. Warp 10

System Properties Comparison Heroic vs. Interbase vs. MySQL vs. SpatiaLite vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

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

Light-weight proven RDBMS

originally from Borland

Widely used open source RDBMS

Spatial extension of SQLite

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

github.com/spotify/heroic

www.embarcadero.com/products/interbase

www.mysql.com

www.gaia-gis.it/fossil/libspatialite/index

www.warp10.io

Technical documentation

spotify.github.io/heroic

docs.embarcadero.com/products/interbase

dev.mysql.com/doc

www.gaia-gis.it/gaia-sins/spatialite_topics.html

www.warp10.io/content/02_Getting_started

Developer

Spotify

Embarcadero

Oracle

since 2010, originally MySQL AB, then Sun

Alessandro Furieri

SenX

Initial release

2014

1984

1995

2008

2015

Current release

InterBase 2020, December 2019

8.4.0, April 2024

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Open Source

Apache License 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

C++

Java

Server operating systems

Android
iOS
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

server-less

Linux
OS X
Windows

Data scheme

schema-free

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.

export as XML data possible

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Jupyter
WebSocket

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

yes

proprietary syntax

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Interbase Change Views

Multi-source replication
Source-replica replication

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.