DBMS > GeoMesa vs. jBASE vs. Oracle vs. Tigris

System Properties Comparison GeoMesa vs. jBASE vs. Oracle vs. Tigris

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 robust multi-value DBMS comprising development tools and middleware

Widely used RDBMS

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Spatial DBMS

Multivalue DBMS

Relational DBMS

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

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	#214	Overall
	#4	Spatial DBMS

Score	1.36
Rank	#157	Overall
	#3	Multivalue DBMS

Score	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Score	0.05
Rank	#359	Overall
	#50	Document stores
	#52	Key-value stores
	#23	Search engines
	#37	Time Series DBMS

Website

www.geomesa.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.oracle.com/database

www.tigrisdata.com

Technical documentation

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

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

docs.oracle.com/en/database

www.tigrisdata.com/docs

Developer

CCRi and others

Rocket Software (formerly Zumasys)

Oracle

Tigris Data, Inc.

Initial release

2014

1991

1980

2022

Current release

5.0.1, July 2024

5.7

23c, September 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

Apache Version 2.0

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

C and C++

Server operating systems

AIX
Linux
Windows

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

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

yes

optional

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

SQL

Support of SQL

Embedded SQL for jBASE in BASIC

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

.Net
Basic
Jabbascript
Java

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

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

yes

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

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

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

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'

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights can be defined down to the item level

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.