DBMS > GeoMesa vs. GeoSpock vs. Oracle vs. Percona Server for MongoDB

System Properties Comparison GeoMesa vs. GeoSpock vs. Oracle vs. Percona Server for MongoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Spatial and temporal data processing engine for extreme data scale

Widely used RDBMS

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Spatial DBMS

Relational DBMS

Document store

Secondary database models

Time Series DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Website

www.geomesa.org

geospock.com

www.oracle.com/database

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

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

docs.oracle.com/en/database

docs.percona.com/percona-distribution-for-mongodb

Developer

CCRi and others

GeoSpock

Oracle

Percona

Initial release

2014

1980

2015

Current release

4.0.5, February 2024

2.0, September 2019

23c, September 2023

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

GPL Version 2

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

Java, Javascript

C and C++

C++

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux

Data scheme

yes

Schemaless in JSON and XML columns

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

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

with proprietary extensions

APIs and other access methods

JDBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

proprietary protocol using JSON

Supported programming languages

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Automatic sharding

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

via In-Memory Engine

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users can be defined per table

fine grained access rights according to SQL-standard

Access rights for users and roles

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.