DBMS > Derby vs. Google Cloud Bigtable vs. Oracle Berkeley DB vs. SQLite

System Properties Comparison Derby vs. Google Cloud Bigtable vs. Oracle Berkeley DB vs. SQLite

Please select another system to include it in the comparison.

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.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Widely used in-process key-value store

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Key-value store
Wide column store

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	4.60
Rank	#70	Overall
	#38	Relational DBMS

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

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

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

db.apache.org/derby

cloud.google.com/bigtable

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

www.sqlite.org

Technical documentation

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

cloud.google.com/bigtable/docs

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

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Google

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Dwayne Richard Hipp

Initial release

1997

2015

1994

2000

Current release

10.17.1.0, November 2023

18.1.40, May 2020

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

commercial license available

Open Source

Public Domain

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

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

Server operating systems

All OS with a Java VM

hosted

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

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

yes

SQL interfaced based on SQLite is available

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java

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

.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

Java Stored Procedures

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Internal replication in Colossus, and regional replication between two clusters in different zones

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

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.