DBMS > Google BigQuery vs. Memcached vs. Oracle Berkeley DB vs. Sequoiadb vs. Valentina Server

System Properties Comparison Google BigQuery vs. Memcached vs. Oracle Berkeley DB vs. Sequoiadb vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

In-memory key-value store, originally intended for caching

Widely used in-process key-value store

NewSQL database with distributed OLTP and SQL

Object-relational database and reports server

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

Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

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

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

cloud.google.com/bigquery

www.memcached.org

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

www.sequoiadb.com

www.valentina-db.net

Technical documentation

cloud.google.com/bigquery/docs

github.com/memcached/memcached/wiki

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

www.sequoiadb.com/en/index.php?m=Files&a=index

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Google

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Sequoiadb Ltd.

Paradigma Software

Initial release

2010

2003

1994

2013

1999

Current release

1.6.25, March 2024

18.1.40, May 2020

5.7.5

License

Commercial or Open Source

commercial

Open Source

BSD license

Open Source

commercial license available

Open Source

Server: AGPL; Client: Apache V2

commercial

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

FreeBSD
Linux
OS X
Unix
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

yes

APIs and other access methods

RESTful HTTP/JSON API

Proprietary protocol

proprietary protocol using JSON

ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
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

.Net
C++
Java
PHP
Python

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions

in JavaScript

JavaScript

yes

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

Document is locked during a transaction

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)

yes

using SASL (Simple Authentication and Security Layer) protocol

simple password-based access control

fine grained access rights 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.