DBMS > GeoMesa vs. ObjectBox vs. Oracle Berkeley DB vs. Warp 10

System Properties Comparison GeoMesa vs. ObjectBox vs. Oracle Berkeley DB vs. Warp 10

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.

Extremely fast embedded database for small devices, IoT and Mobile

Widely used in-process key-value store

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Spatial DBMS

Object oriented DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Time Series DBMS

Secondary database models

Time Series DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.20
Rank	#170	Overall
	#5	Object oriented DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

www.geomesa.org

objectbox.io

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

www.warp10.io

Technical documentation

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

docs.objectbox.io

docs.oracle.com/cd/E17076_05/html/index.html

www.warp10.io/content/02_Getting_started

Developer

CCRi and others

ObjectBox Limited

Oracle

originally developed by Sleepycat, which was acquired by Oracle

SenX

Initial release

2014

2017

1994

2015

Current release

4.0.5, February 2024

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache License 2.0

Open Source

commercial license available

Open Source

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

C, Java, C++ (depending on the Berkeley DB edition)

Java

Server operating systems

Android
iOS
Linux
macOS
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X
Windows

Data scheme

yes

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

APIs and other access methods

Proprietary native API

HTTP API
Jupyter
WebSocket

Supported programming languages

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

yes

WarpScript

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

online/offline synchronization between client and server

Source-replica replication

selectable replication factor

based on HBase

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

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

User concepts

Access control

yes

depending on the DBMS used for storage

yes

Mandatory use of cryptographic tokens, containing fine-grained authorizations

More information provided by the system vendor

News

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

The first On-Device Vector Database: ObjectBox 4.0
16 May 2024

Edge AI: The era of on-device AI
23 April 2024

In-Memory Database Use Cases
15 February 2024

Data Viewer for Objects – announcing ObjectBox Admin
14 November 2023

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

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

Margo I. Seltzer | Berkman Klein Center
18 August 2020, Berkman Klein Center

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular -- ADTmag
5 March 2019, ADT Magazine

How to store financial market data for backtesting
26 January 2019, Towards Data Science

The importance of bitcoin nodes and how to start one
9 May 2014, The Merkle News

provided by Google News

Time Series Intelligence Software Market Business Insights, Key Trend Analysis | Google, SAP, Azure Time Series ...
24 April 2024, Amoré

Time Series Intelligence Software Market Analysis and Revenue Prediction | Azure Time Series Insights, Trendalyze ...
20 May 2024, Weekly Post Gazette

provided by Google News

Share this page