DBMS > GeoMesa vs. OpenEdge vs. SAP Adaptive Server vs. SQLite vs. VelocityDB

System Properties Comparison GeoMesa vs. OpenEdge vs. SAP Adaptive Server vs. SQLite vs. VelocityDB

Editorial information provided by DB-Engines

Name

Description

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

Application development environment with integrated database management system

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

Widely used embeddable, in-process RDBMS

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

Primary database model

Spatial DBMS

Relational DBMS

Graph DBMS
Object oriented DBMS

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

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

Website

www.geomesa.org

www.progress.com/openedge

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

www.sqlite.org

velocitydb.com

Technical documentation

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

documentation.progress.com/output/ua/OpenEdge_latest

help.sap.com/docs/SAP_ASE

www.sqlite.org/docs.html

velocitydb.com/UserGuide

Developer

CCRi and others

Progress Software Corporation

SAP, Sybase

Dwayne Richard Hipp

VelocityDB Inc

Initial release

2014

1984

1987

2000

2011

Current release

4.0.5, February 2024

OpenEdge 12.2, March 2020

16.0

3.45.3 (15 April 2024), April 2024

7.x

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

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

C and C++

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Unix
Windows

server-less

Any that supports .NET

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.Net

Supported programming languages

Progress proprietary ABL (Advanced Business Language)

C
C++
Cobol
Java
Java
Perl
PHP
Python

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

Server-side scripts

Stored procedures

yes

Java and Transact-SQL

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning

since Version 11.4

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

Multi-source replication
Source-replica replication

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

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

Users and groups

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.