DBMS > GeoMesa vs. VelocityDB

System Properties Comparison GeoMesa vs. VelocityDB

Please select another system to include it in the comparison.

Our visitors often compare GeoMesa and VelocityDB with DuckDB, PostgreSQL and CockroachDB.

Editorial information provided by DB-Engines

Name

Description

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

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Spatial DBMS

Graph DBMS
Object oriented DBMS

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

Score	0.73
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.00
Rank	#381	Overall
	#40	Graph DBMS
	#20	Object oriented DBMS

Website

www.geomesa.org

velocitydb.com

Technical documentation

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

velocitydb.com/UserGuide

Developer

CCRi and others

VelocityDB Inc

Initial release

2014

2011

Current release

5.0.1, July 2024

7.x

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

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

Server operating systems

Any that supports .NET

Data scheme

yes

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.

Secondary indexes

yes

SQL

Support of SQL

APIs and other access methods

.Net

Supported programming languages

.Net

Server-side scripts

Stored procedures

Triggers

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

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

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

Based on Windows Authentication

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.