DBMS > GeoMesa vs. Microsoft Azure Table Storage vs. ObjectBox vs. Oracle Rdb vs. SQLite

System Properties Comparison GeoMesa vs. Microsoft Azure Table Storage vs. ObjectBox vs. Oracle Rdb vs. SQLite

Editorial information provided by DB-Engines

Name

Description

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

A Wide Column Store for rapid development using massive semi-structured datasets

Lightweight, fast on-device database for IoT, Mobile and Embedded devices, persisting and synchronising objects and vectors

Widely used embeddable, in-process RDBMS

Primary database model

Spatial DBMS

Wide column store

Object oriented DBMS
Vector DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	1.29
Rank	#166	Overall
	#5	Object oriented DBMS
	#7	Vector DBMS

Score	1.14
Rank	#178	Overall
	#80	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.geomesa.org

azure.microsoft.com/en-us/services/storage/tables

github.com/objectbox
objectbox.io

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

www.sqlite.org

Technical documentation

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

docs.objectbox.io

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

www.sqlite.org/docs.html

Developer

CCRi and others

Microsoft

ObjectBox Limited

Oracle, originally developed by Digital Equipment Corporation (DEC)

Dwayne Richard Hipp

Initial release

2014

2012

2017

1984

2000

Current release

5.0.0, May 2024

4.0 (May 2024)

7.4.1.1, 2021

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Bindings are released under Apache 2.0

Apache License 2.0

commercial

Open Source

Public Domain

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

Server operating systems

hosted

Android
Any POSIX system
Docker
iOS
Linux
macOS
QNX
Windows

HP Open VMS

server-less

Data scheme

yes

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

yes

dynamic column types

Typing

predefined data types such as float or date

yes

yes, plus "flex" map-like types

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

Proprietary native API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

C
C++
Dart (Flutter)
Go
Java
Kotlin
Python
Swift

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Data sync between devices allowing occasional connected databases to work completely offline

none

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

optimistic locking

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Access rights based on private key authentication or shared access signatures

yes

More information provided by the system vendor

News

The on-device Vector Database for Android and Java
29 May 2024

Vector search: making sense of search queries
29 May 2024

Python on-device Vector and Object Database for Local AI
28 May 2024

Evolution of search: traditional vs vector search
23 May 2024

On-device Vector Database for Dart/Flutter
21 May 2024

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.