DBMS > Derby vs. Heroic vs. Lovefield vs. Quasardb vs. Snowflake

System Properties Comparison Derby vs. Heroic vs. Lovefield vs. Quasardb vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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

Embeddable relational database for web apps written in pure JavaScript

Distributed, high-performance timeseries database

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

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

Score	4.60
Rank	#70	Overall
	#38	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

db.apache.org/derby

github.com/spotify/heroic

google.github.io/lovefield

quasar.ai

www.snowflake.com

Technical documentation

db.apache.org/derby/manuals/index.html

spotify.github.io/heroic

github.com/google/lovefield/blob/master/docs/spec_index.md

doc.quasar.ai/master

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Spotify

Google

quasardb

Snowflake Computing Inc.

Initial release

1997

2014

2009

2014

Current release

10.17.1.0, November 2023

2.1.12, February 2017

3.14.1, January 2024

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

JavaScript

C++

Server operating systems

All OS with a Java VM

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

BSD
Linux
OS X
Windows

hosted

Data scheme

yes

schema-free

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

integer and binary

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

with tags

SQL

Support of SQL

yes

SQL-like query language

via JavaScript builder pattern

SQL-like query language

yes

APIs and other access methods

JDBC

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

HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

Java

JavaScript

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

Triggers

yes

Using read-only observers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

consistent hashing

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

Source-replica replication with selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

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

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

yes

Transient mode

User concepts

Access control

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

Users with fine-grained authorization concept, user roles and pluggable authentication

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.