DBMS > AlaSQL vs. GeoMesa vs. SAP Adaptive Server vs. VoltDB

System Properties Comparison AlaSQL vs. GeoMesa vs. SAP Adaptive Server vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store
Relational DBMS

Spatial DBMS

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.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

alasql.org

www.geomesa.org

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

www.voltdb.com

Technical documentation

github.com/AlaSQL/alasql

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

help.sap.com/docs/SAP_ASE

docs.voltdb.com

Developer

Andrey Gershun & Mathias R. Wulff

CCRi and others

SAP, Sybase

VoltDB Inc.

Initial release

2014

1987

2010

Current release

5.0.0, May 2024

16.0

11.3, April 2022

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache License 2.0

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

JavaScript

Scala

C and C++

Java, C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

AIX
HP-UX
Linux
Solaris
Unix
Windows

Linux
OS X

for development

Data scheme

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

yes

only a subset of SQL 99

APIs and other access methods

JavaScript API

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

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

JavaScript

C
C++
Cobol
Java
Java
Perl
PHP
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Java and Transact-SQL

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

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

none

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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

Create a Marvel Database with SQL and Javascript, the easy way
2 July 2019, Towards Data Science

HarperDB - How and Why We Built It From The Ground Up on NodeJS
28 February 2021, hackernoon.com

Multi faceted data exploration in the browser using Leaflet and amCharts
3 May 2020, Towards Data Science

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

New Services for SAP HANA Cloud Database
7 April 2021, SAP News

Arcion Introduces SAP Sybase ASE Connector for Ultimate Migration Flexibility
5 January 2023, businesswire.com

Patch SAP Adaptive Server Enterprise now to avoid takeover risk
3 June 2020, BleepingComputer

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

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page