DBMS > GeoMesa vs. Google Cloud Spanner vs. Oracle Berkeley DB

System Properties Comparison GeoMesa vs. Google Cloud Spanner vs. Oracle Berkeley DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

Widely used in-process key-value store

Primary database model

Spatial DBMS

Relational DBMS

Key-value store

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	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	2.89
Rank	#103	Overall
	#52	Relational DBMS

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

Website

www.geomesa.org

cloud.google.com/spanner

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

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

cloud.google.com/spanner/docs

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

Developer

CCRi and others

Google

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2014

2017

1994

Current release

4.0.5, February 2024

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

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

Scala

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

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

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

Query statements complying to ANSI 2011

yes

SQL interfaced based on SQLite is available

APIs and other access methods

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

Supported programming languages

Go
Java
JavaScript (Node.js)
Python

.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

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication with 3 replicas for regional instances.

Source-replica replication

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

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

Transaction concepts

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

ACID

Strict serializable isolation

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.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

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

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Google Improves Cloud Spanner: More Compute and Storage without Price Increase
14 October 2023, InfoQ.com

Google turns up the heat on AWS, claims Cloud Spanner is half the cost of DynamoDB
11 October 2023, TechCrunch

Google makes its Cloud Spanner database service faster and more cost-efficient
11 October 2023, SiliconANGLE News

Google Spanner: When Do You Need to Move to It?
11 September 2023, hackernoon.com

Google Cloud Spanner competes directly with Amazon DynamoDB
12 October 2023, Techzine Europe

provided by Google News

Margo Seltzer Named ACM Athena Lecturer for Technical and Mentoring Contributions
26 April 2023, HPCwire

EC will investigate the Oracle/Sun takeover due to concerns about MySQL
3 September 2009, The Guardian

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

The importance of bitcoin nodes and how to start one
9 May 2014, The Merkle News

A Quick Look at Open Source Databases for Mobile App Development
29 April 2018, Open Source For You

provided by Google News

Share this page