DBMS > FatDB vs. Lovefield vs. Oracle Berkeley DB vs. SpatiaLite

System Properties Comparison FatDB vs. Lovefield vs. Oracle Berkeley DB vs. SpatiaLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Embeddable relational database for web apps written in pure JavaScript

Widely used in-process key-value store

Spatial extension of SQLite

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Website

google.github.io/lovefield

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

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

Technical documentation

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

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

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

Developer

FatCloud

Google

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Alessandro Furieri

Initial release

2012

2014

1994

2008

Current release

2.1.12, February 2017

18.1.40, May 2020

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

commercial license available

Open Source

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

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

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

C++

Server operating systems

Windows

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

server-less

Data scheme

schema-free

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.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language

via JavaScript builder pattern

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

yes

via applications

Triggers

yes

via applications

Using read-only observers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual 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

Can implement custom security layer via applications

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Kagiso interactive shares: all eyes on android at google I/O
11 May 2015, WhaTech

provided by Google News

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

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

Oracle buys Sleepycat Software
14 February 2006, MarketWatch

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

Margo I. Seltzer | Berkman Klein Center
18 August 2020, Berkman Klein Center

provided by Google News

Share this page