DBMS > Derby vs. Google BigQuery vs. Oracle Berkeley DB vs. YDB

System Properties Comparison Derby vs. Google BigQuery vs. Oracle Berkeley DB vs. YDB

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.

Large scale data warehouse service with append-only tables

Widely used in-process key-value store

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store
Relational DBMS

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

Score	4.60
Rank	#70	Overall
	#38	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

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

Score	0.33
Rank	#287	Overall
	#43	Document stores
	#132	Relational DBMS

Website

db.apache.org/derby

cloud.google.com/bigquery

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

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

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

cloud.google.com/bigquery/docs

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

ydb.tech/en/docs

Developer

Apache Software Foundation

Google

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Yandex

Initial release

1997

2010

1994

2019

Current release

10.17.1.0, November 2023

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

commercial license available

Open Source

Apache 2.0; commercial license available

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

Linux

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

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

yes

SQL interfaced based on SQLite is available

SQL-like query language (YQL)

APIs and other access methods

JDBC

RESTful HTTP/JSON API

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
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

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

in JavaScript

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Active-passive shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights defined for Yandex Cloud users

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.