DBMS > Lovefield vs. OpenTSDB vs. Oracle Berkeley DB vs. SQLite

System Properties Comparison Lovefield vs. OpenTSDB vs. Oracle Berkeley DB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable relational database for web apps written in pure JavaScript

Scalable Time Series DBMS based on HBase

Widely used in-process key-value store

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

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

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

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

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

google.github.io/lovefield

opentsdb.net

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

www.sqlite.org

Technical documentation

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

opentsdb.net/docs/build/html/index.html

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

www.sqlite.org/docs.html

Developer

Google

currently maintained by Yahoo and other contributors

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Dwayne Richard Hipp

Initial release

2014

2011

1994

2000

Current release

2.1.12, February 2017

18.1.40, May 2020

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

LGPL

Open Source

commercial license available

Open Source

Public Domain

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

JavaScript

Java

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

Server operating systems

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

tested with Chrome, Firefox, IE, Safari

Linux
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

yes

SQL interfaced based on SQLite is available

yes

SQL-92 is not fully supported

APIs and other access methods

HTTP API
Telnet API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

JavaScript

Erlang
Go
Java
Python
R
Ruby

.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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Triggers

Using read-only observers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on HBase

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

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

via file-system locks

Durability

Support for making data persistent

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

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.