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

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

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

A high-performance vector database with neural network or semantic-based matching

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

Widely used embeddable, in-process RDBMS

Primary database model

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	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.geomesa.org

www.progress.com/openedge

github.com/qdrant/qdrant
qdrant.tech

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

www.sqlite.org

Technical documentation

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

documentation.progress.com/output/ua/OpenEdge_latest

qdrant.tech/documentation

help.sap.com/docs/SAP_ASE

www.sqlite.org/docs.html

Developer

CCRi and others

Progress Software Corporation

Qdrant

SAP, Sybase

Dwayne Richard Hipp

Initial release

2014

1984

2021

1987

2000

Current release

4.0.5, February 2024

OpenEdge 12.2, March 2020

16.0

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2.0

commercial

Open Source

Public Domain

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

Rust

C and C++

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows

Docker
Linux
macOS
Windows

AIX
HP-UX
Linux
Solaris
Unix
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

yes

not rigid because of 'dynamic typing' concept.

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

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

close to SQL 92

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Progress proprietary ABL (Advanced Business Language)

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

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

Server-side scripts

Stored procedures

yes

Java and Transact-SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning

since Version 11.4

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

Collection-level 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

Eventual Consistency, tunable consistency

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

Users and groups

Key-based authentication

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.