DBMS > Cachelot.io vs. Google BigQuery vs. Oracle Berkeley DB vs. ToroDB

System Properties Comparison Cachelot.io vs. Google BigQuery vs. Oracle Berkeley DB vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

In-memory caching system

Large scale data warehouse service with append-only tables

Widely used in-process key-value store

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Key-value store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store

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

Score	0.04
Rank	#388	Overall
	#62	Key-value stores

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

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

Website

cachelot.io

cloud.google.com/bigquery

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

github.com/torodb/server

Technical documentation

cloud.google.com/bigquery/docs

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

Developer

Google

Oracle

originally developed by Sleepycat, which was acquired by Oracle

8Kdata

Initial release

2015

2010

1994

2016

Current release

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Simplified BSD License

commercial

Open Source

commercial license available

Open Source

AGPL-V3

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++

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

Java

Server operating systems

FreeBSD
Linux
OS X

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

All OS with a Java 7 VM

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

APIs and other access methods

Memcached protocol

RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

.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

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

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

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 and roles

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.