DBMS > GeoMesa vs. LMDB vs. Oracle vs. Quasardb

System Properties Comparison GeoMesa vs. LMDB vs. Oracle vs. Quasardb

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 high performant, light-weight, embedded key-value database library

Widely used RDBMS

Distributed, high-performance timeseries database

Primary database model

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.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.09
Rank	#121	Overall
	#20	Key-value stores

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Website

www.geomesa.org

www.symas.com/symas-embedded-database-lmdb

www.oracle.com/database

quasar.ai

Technical documentation

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

www.lmdb.tech/doc

docs.oracle.com/en/database

doc.quasar.ai/master

Developer

CCRi and others

Symas

Oracle

quasardb

Initial release

2014

2011

1980

2009

Current release

5.0.0, May 2024

0.9.32, January 2024

23c, September 2023

3.14.1, January 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

commercial

restricted free version is available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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++

C++

Server operating systems

Linux
Unix
Windows

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

BSD
Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP API

Supported programming languages

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding, horizontal partitioning

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Multi-source replication
Source-replica replication

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

with Hadoop integration

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

by using LevelDB

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

Transient mode

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

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.