DBMS > GeoMesa vs. LevelDB vs. ObjectBox vs. TimescaleDB

System Properties Comparison GeoMesa vs. LevelDB vs. ObjectBox vs. TimescaleDB

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.

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Extremely fast embedded database for small devices, IoT and Mobile

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Secondary database models

Time Series DBMS

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	1.29
Rank	#166	Overall
	#5	Object oriented DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

www.geomesa.org

github.com/google/leveldb

objectbox.io

www.timescale.com

Technical documentation

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

github.com/google/leveldb/blob/main/doc/index.md

docs.objectbox.io

docs.timescale.com

Developer

CCRi and others

Google

ObjectBox Limited

Timescale

Initial release

2014

2011

2017

Current release

5.0.0, May 2024

1.23, February 2021

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

BSD

Open Source

Apache License 2.0

Open Source

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

C and C++

Server operating systems

Illumos
Linux
OS X
Windows

Android
iOS
Linux
macOS
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

yes

full PostgreSQL SQL syntax

APIs and other access methods

Proprietary native API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

online/offline synchronization between client and server

Source-replica replication with hot standby and reads on replicas

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

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

yes

fine grained access rights according to SQL-standard

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.

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

Pliops unveils XDP-Rocks for RocksDB – Blocks and Files
19 October 2022, Blocks and Files

Microsoft Teams stores auth tokens as cleartext in Windows, Linux, Macs
14 September 2022, BleepingComputer

XanMod, Liquorix Kernels Offer Some Advantages On AMD Ryzen 5 Notebook
26 July 2021, Phoronix

Threat Thursday: BlackGuard Infostealer Rises from Russian Underground Markets
21 April 2022, BlackBerry Blog

Rust-Based Info Stealers Abuse GitHub Codespaces
19 May 2023, Trend Micro

provided by Google News

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

Power IoT and time-series workloads with TimescaleDB for Azure Database for PostgreSQL
18 March 2019, azure.microsoft.com

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, Business Wire

TimescaleDB goes distributed; implements ‘Chunking’ over ‘Sharding’ for scaling-out
22 August 2019, Packt Hub

provided by Google News

Share this page