DBMS > 4D vs. Ehcache vs. Google BigQuery vs. Memcached vs. Oracle Berkeley DB

System Properties Comparison 4D vs. Ehcache vs. Google BigQuery vs. Memcached vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

A widely adopted Java cache with tiered storage options

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

Primary database model

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

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

Website

www.4d.com

www.ehcache.org

cloud.google.com/bigquery

www.memcached.org

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

Technical documentation

developer.4d.com

www.ehcache.org/documentation

cloud.google.com/bigquery/docs

github.com/memcached/memcached/wiki

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

Developer

4D, Inc

Terracotta Inc, owned by Software AG

Google

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

1984

2009

2010

2003

1994

Current release

v20, April 2023

3.10.0, March 2022

1.6.25, March 2024

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

BSD license

Open Source

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

OS X
Windows

All OS with a Java VM

hosted

FreeBSD
Linux
OS X
Unix
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

yes

schema-free

yes

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

close to SQL 92

yes

SQL interfaced based on SQLite is available

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JCache

RESTful HTTP/JSON API

Proprietary protocol

Supported programming languages

4D proprietary IDE
PHP

Java

.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

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Triggers

yes

Cache Event Listeners

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

by using Terracotta Server

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

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

Users and groups

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

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.