DBMS > GeoMesa vs. Graph Engine vs. InfinityDB vs. SAP Adaptive Server

System Properties Comparison GeoMesa vs. Graph Engine vs. InfinityDB 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.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A Java embedded Key-Value Store which extends the Java Map interface

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

Primary database model

Spatial DBMS

Graph DBMS
Key-value store

Key-value store

Relational 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	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.00
Rank	#378	Overall
	#57	Key-value stores

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Website

www.geomesa.org

www.graphengine.io

boilerbay.com

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

Technical documentation

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

www.graphengine.io/docs/manual

boilerbay.com/infinitydb/manual

help.sap.com/docs/SAP_ASE

Developer

CCRi and others

Microsoft

Boiler Bay Inc.

SAP, Sybase

Initial release

2014

2010

2002

1987

Current release

4.0.5, February 2024

4.0

16.0

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

MIT License

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

.NET and C

Java

C and C++

Server operating systems

.NET

All OS with a Java VM

AIX
HP-UX
Linux
Solaris
Unix
Windows

Data scheme

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

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

Supported programming languages

C#
C++
F#
Visual Basic

Java

C
C++
Cobol
Java
Java
Perl
PHP
Python

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

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

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

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

yes

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Trinity
2 June 2023, Microsoft

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

The graph analytics landscape 2019 - DataScienceCentral.com
27 February 2019, Data Science Central

provided by Google News

Achieve zero RPO for your SAP ASE (Sybase) databases with Amazon FSx for NetApp ONTAP | Amazon Web Services
7 May 2024, AWS Blog

Arcion Introduces SAP Sybase ASE Connector for Ultimate Migration Flexibility
5 January 2023, Business Wire

AWS Launch Wizard is now available in Melbourne, Spain, and Zurich Regions
26 January 2024, AWS Blog

Newly Patched SAP ASE Flaws Could Let Attackers Hack Database Servers
3 June 2020, The Hacker News

Critical SAP ASE Flaws Allow Complete Control of Databases
3 June 2020, Threatpost

provided by Google News

Share this page