DBMS > Google Cloud Datastore vs. Oracle Berkeley DB vs. STSdb vs. TerarkDB

System Properties Comparison Google Cloud Datastore vs. Oracle Berkeley DB vs. STSdb vs. TerarkDB

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Document store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

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

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

cloud.google.com/datastore

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

github.com/STSSoft/STSdb4

github.com/bytedance/terarkdb

Technical documentation

cloud.google.com/datastore/docs

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

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Google

Oracle

originally developed by Sleepycat, which was acquired by Oracle

STS Soft SC

ByteDance, originally Terark

Initial release

2008

1994

2011

2016

Current release

18.1.40, May 2020

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

GPLv2, commercial license available

commercial

restricted open source 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

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes, details here

yes

primitive types and user defined types (classes)

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

APIs and other access methods

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

.NET Client API

C++ API
Java API

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

C#
Java

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

none

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

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

Google Cloud vs AWS: Which Cloud Computing Platform is Better?
11 September 2024, Cloudwards

Google Gets Rid of Fees To Transfer Data Out of Cloud Platform
12 January 2024, Spiceworks News and Insights

What Is Google Cloud? Platform, Benefits & More Explained
11 September 2024, Cloudwards

Google App Engine
26 April 2024, TechTarget

17 Top Cloud Storage Companies to Know
9 April 2024, Built In

provided by Google News

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

What is NoSQL (Not Only SQL database)?
28 February 2022, TechTarget

Margo I. Seltzer
18 August 2020, Berkman Klein Center

Oracle acquires Sleepycat for code
17 August 2016, East Bay Times

How to store financial market data for backtesting
26 January 2019, Towards Data Science

provided by Google News

Share this page