DBMS > GeoMesa vs. Oracle Rdb

System Properties Comparison GeoMesa vs. Oracle Rdb

Please select another system to include it in the comparison.

Our visitors often compare GeoMesa and Oracle Rdb with Elasticsearch, MongoDB and PostgreSQL.

Editorial information provided by DB-Engines

Name

Description

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

Primary database model

Spatial DBMS

Relational DBMS

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	1.08
Rank	#187	Overall
	#85	Relational DBMS

Website

www.geomesa.org

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

Technical documentation

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

www.oracle.com/database/technologies/related/rdb-doc.html

Developer

CCRi and others

Oracle, originally developed by Digital Equipment Corporation (DEC)

Initial release

2014

1984

Current release

4.0.5, February 2024

7.4.1.1, 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

Server operating systems

HP Open VMS

Data scheme

yes

Flexible Schema (defined schema, partial schema, 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.

Secondary indexes

yes

SQL

Support of SQL

yes

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

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

User concepts

Access control

yes

depending on the DBMS used for storage

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

Oracle Adds New AI-Enabling Features To MySQL HeatWave
23 March 2023, Forbes

Oracle Business Model - How Oracle Makes Money?
12 June 2023, Business Model Analyst

Should we all consolidate databases for the storage benefits? Reg vultures deploy DevOps, zoos, haircuts
18 September 2020, The Register

2013 Data Science Salary Survey – O'Reilly
4 May 2013, O'Reilly Media

provided by Google News

Share this page