DBMS > GeoMesa vs. Oracle Berkeley DB vs. PlanetScale vs. PostGIS

System Properties Comparison GeoMesa vs. Oracle Berkeley DB vs. PlanetScale vs. PostGIS

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.

Widely used in-process key-value store

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Spatial extension of PostgreSQL

Primary database model

Spatial DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Spatial DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Website

www.geomesa.org

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

planetscale.com

postgis.net

Technical documentation

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

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

planetscale.com/docs

postgis.net/documentation

Developer

CCRi and others

Oracle

originally developed by Sleepycat, which was acquired by Oracle

PlanetScale

Initial release

2014

1994

2020

2005

Current release

5.0.0, May 2024

18.1.40, May 2020

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

commercial license available

commercial

Open Source

GPL v2.0

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

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

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

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

yes

based on PostgreSQL

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

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

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

Margo I. Seltzer | Berkman Klein Center
18 August 2020, Berkman Klein Center

Oracle buys Sleepycat Software
14 February 2006, MarketWatch

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

provided by Google News

PlanetScale ends free tier bid, sheds staff in profitability bid
11 March 2024, The Register

PlanetScale forks MySQL to add vector support
3 October 2023, TechCrunch

PlanetScale Named to Fortune 2023 Best Small Workplaces
31 August 2023, Business Wire

How to Migrate to PlanetScale's Serverless Database
14 October 2021, The New Stack

PlanetScale review: Horizontally scalable MySQL in the cloud
1 September 2021, InfoWorld

provided by Google News

Share this page