DBMS > Google BigQuery vs. Immudb vs. Oracle Berkeley DB vs. Sadas Engine

System Properties Comparison Google BigQuery vs. Immudb vs. Oracle Berkeley DB vs. Sadas Engine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Widely used in-process key-value store

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Secondary database models

Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.24
Rank	#305	Overall
	#43	Key-value stores

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

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

cloud.google.com/bigquery

github.com/codenotary/immudb
immudb.io

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

www.sadasengine.com

Technical documentation

cloud.google.com/bigquery/docs

docs.immudb.io

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

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Google

Codenotary

Oracle

originally developed by Sleepycat, which was acquired by Oracle

SADAS s.r.l.

Initial release

2010

2020

1994

2006

Current release

1.2.3, April 2022

18.1.40, May 2020

8.0

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

commercial license available

commercial

free trial version 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

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

C++

Server operating systems

hosted

BSD
Linux
macOS
Solaris
Windows
z/OS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

AIX
Linux
Windows

Data scheme

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

yes

SQL-like syntax

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

RESTful HTTP/JSON API

gRPC protocol
PostgreSQL wire protocol

JDBC
ODBC
Proprietary protocol

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
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

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

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

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

managed by 'Learn by Usage'

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights for users, groups and roles according to SQL-standard

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.