DBMS > Heroic vs. Lovefield vs. Oracle Berkeley DB vs. SiteWhere

System Properties Comparison Heroic vs. Lovefield vs. Oracle Berkeley DB vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used in-process key-value store

M2M integration platform for persisting/querying time series data

Primary database model

Time Series DBMS

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Time Series DBMS

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

github.com/spotify/heroic

google.github.io/lovefield

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

github.com/sitewhere/sitewhere

Technical documentation

spotify.github.io/heroic

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

docs.oracle.com/cd/E17076_05/html/index.html

sitewhere1.sitewhere.io/index.html

Developer

Spotify

Google

Oracle

originally developed by Sleepycat, which was acquired by Oracle

SiteWhere

Initial release

2014

1994

2010

Current release

2.1.12, February 2017

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

commercial license available

Open Source

Common Public Attribution License Version 1.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

Java

JavaScript

C, Java, C++ (depending on the Berkeley DB edition)

Java

Server operating systems

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

tested with Chrome, Firefox, IE, Safari

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

predefined scheme

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.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

yes

SQL interfaced based on SQLite is available

APIs and other access methods

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

HTTP REST

Supported programming languages

JavaScript

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

Triggers

Using read-only observers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

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

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

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

Users with fine-grained authorization concept

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

Recent citations in the news

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

provided by Google News

Margo Seltzer Named ACM Athena Lecturer for Technical and Mentoring Contributions
26 April 2023, HPCwire

EC will investigate the Oracle/Sun takeover due to concerns about MySQL
3 September 2009, The Guardian

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular -- ADTmag
5 March 2019, ADT Magazine

The importance of bitcoin nodes and how to start one
9 May 2014, The Merkle News

A Quick Look at Open Source Databases for Mobile App Development
29 April 2018, Open Source For You

provided by Google News

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page