DBMS > GeoMesa vs. JaguarDB vs. MySQL vs. SAP Adaptive Server

System Properties Comparison GeoMesa vs. JaguarDB vs. MySQL vs. SAP Adaptive Server

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.

Performant, highly scalable DBMS for AI and IoT applications

Widely used open source RDBMS

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Primary database model

Spatial DBMS

Key-value store
Vector DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#15	Vector DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	35.09
Rank	#25	Overall
	#17	Relational DBMS

Website

www.geomesa.org

www.jaguardb.com

www.mysql.com

www.sap.com/products/technology-platform/sybase-ase.html

Technical documentation

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

www.jaguardb.com/support.html

dev.mysql.com/doc

help.sap.com/docs/SAP_ASE

Developer

CCRi and others

DataJaguar, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

SAP, Sybase

Initial release

2014

2015

1995

1987

Current release

5.0.0, May 2024

3.3 July 2023

8.4.0, April 2024

16.0

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL V3.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++

the server part. Clients available in other languages

C and C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Unix
Windows

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

C
C++
Cobol
Java
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

Java and Transact-SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication

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

Eventual Consistency

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

User concepts

Access control

yes

depending on the DBMS used for storage

rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

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.