DBMS > Google Cloud Datastore vs. Oracle Berkeley DB vs. XTDB

System Properties Comparison Google Cloud Datastore vs. Oracle Berkeley DB vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Widely used in-process key-value store

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store

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	3.62
Rank	#71	Overall
	#12	Document stores

Score	1.72
Rank	#131	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	0.20
Rank	#314	Overall
	#46	Document stores

Website

cloud.google.com/datastore

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

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

cloud.google.com/datastore/docs

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

www.xtdb.com/docs

Developer

Google

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Juxt Ltd.

Initial release

2008

1994

2019

Current release

18.1.40, May 2020

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

MIT License

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)

Clojure

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes, details here

yes, extensible-data-notation format

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

SQL-like query language (GQL)

yes

SQL interfaced based on SQLite is available

limited SQL, making use of Apache Calcite

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
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

Clojure
Java

Server-side scripts

Stored procedures

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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 rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Best cloud storage of 2025: tested, reviewed and rated by experts
9 May 2025, TechRadar

Storage news ticker – April 11
11 April 2025, Blocks and Files

Best Cloud Storage Options for All Your Data in 2025
16 April 2025, CNET

Google Cloud vs AWS: Which Cloud Computing Platform is Better?
5 April 2025, Cloudwards.net

Enabling Security for Hadoop Data Lake on Google Cloud Storage
30 July 2024, Uber

provided by Google News

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular
5 March 2019, ADTmag

Which Are the Top Local Databases for React Native
15 October 2019, appinventiv.com

Fig. 2. XML Methods for Various XML DBMS Types
29 October 2024, ResearchGate

Margo I. Seltzer
12 December 2024, Berkman Klein Center

30 years of Cream of the Crop: a complete list
28 January 2012, The Mercury News

provided by Google News

Share this page