DBMS > GeoMesa vs. OpenMLDB vs. OrigoDB vs. SpatiaLite vs. VoltDB

System Properties Comparison GeoMesa vs. OpenMLDB vs. OrigoDB vs. SpatiaLite vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

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

An open-source machine learning database that provides a feature platform for training and inference

A fully ACID in-memory object graph database

Spatial extension of SQLite

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Spatial DBMS

Time Series DBMS

Document store
Object oriented DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.10
Rank	#359	Overall
	#36	Time Series DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.geomesa.org

openmldb.ai

origodb.com

www.gaia-gis.it/fossil/libspatialite/index

www.voltdb.com

Technical documentation

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

openmldb.ai/docs/zh/main

origodb.com/docs

www.gaia-gis.it/gaia-sins/spatialite_topics.html

docs.voltdb.com

Developer

CCRi and others

4 Paradigm Inc.

Robert Friberg et al

Alessandro Furieri

VoltDB Inc.

Initial release

2014

2020

2009

under the name LiveDB

2008

2010

Current release

5.0.0, May 2024

2024-2 February 2024

5.0.0, August 2020

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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++, Java, Scala

C++

Java, C++

Server operating systems

Linux

Linux
Windows

server-less

Linux
OS X

for development

Data scheme

yes

Fixed schema

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

JDBC
SQLAlchemy

.NET Client API
HTTP API
LINQ

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C++
Go
Java
Python
Scala

.Net

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning

client side managed; servers are not synchronized

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

none

Multi-source replication
Source-replica replication

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

depending on model

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Write ahead log

yes

Snapshots and command logging

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

fine grained access rights according to SQL-standard

Role based authorization

Users and roles with access to stored procedures

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.

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

MLOp practice: using OpenMLDB in the real-time anti-fraud model for the bank's online transaction
23 August 2021, Towards Data Science

Predictive maintenance — 5minutes demo of an end to end machine learning project
13 August 2021, Towards Data Science

Compared to Native Spark 3.0, We Have Achieved Significant Optimization Effects in the AI
3 August 2021, Towards Data Science

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page