DBMS > GeoMesa vs. MySQL vs. SAP Advantage Database Server vs. VelocityDB

System Properties Comparison GeoMesa vs. MySQL vs. SAP Advantage Database Server vs. VelocityDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Widely used open source RDBMS

Low-cost RDBMS with access to ISAM and FoxPro data structures

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

Primary database model

Spatial DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Graph DBMS
Object oriented DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Website

www.geomesa.org

www.mysql.com

www.sap.com/products/advantage-database-server.html

velocitydb.com

Technical documentation

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

dev.mysql.com/doc

velocitydb.com/UserGuide

Developer

CCRi and others

Oracle

since 2010, originally MySQL AB, then Sun

Sybase, SAP

VelocityDB Inc

Initial release

2014

1995

1993

2011

Current release

4.0.5, February 2024

8.4.0, April 2024

7.x

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Scala

C and C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

.Net

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Delphi
Perl
PHP

.Net

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
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

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

caching of (temporary) tables can be configured

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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.