DBMS > GeoMesa vs. GeoSpock vs. SQLite vs. Valentina Server

System Properties Comparison GeoMesa vs. GeoSpock vs. SQLite vs. Valentina Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Spatial and temporal data processing engine for extreme data scale

Widely used embeddable, in-process RDBMS

Object-relational database and reports server

Primary database model

Spatial DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.18
Rank	#313	Overall
	#140	Relational DBMS

Website

www.geomesa.org

geospock.com

www.sqlite.org

www.valentina-db.net

Technical documentation

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

www.sqlite.org/docs.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

CCRi and others

GeoSpock

Dwayne Richard Hipp

Paradigma Software

Initial release

2014

2000

1999

Current release

5.0.1, July 2024

2.0, September 2019

3.46.1 (13 August 2024), August 2024

5.7.5

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Public Domain

commercial

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

Java, Javascript

Server operating systems

hosted

server-less

Linux
OS X
Windows

Data scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ODBC

Supported programming languages

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

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

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 for users can be defined per table

fine grained access rights according to SQL-standard

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.