DBMS > GeoMesa vs. Riak KV vs. SAP Advantage Database Server vs. searchxml

System Properties Comparison GeoMesa vs. Riak KV vs. SAP Advantage Database Server vs. searchxml

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Distributed, fault tolerant key-value store

Low-cost RDBMS with access to ISAM and FoxPro data structures

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Spatial DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Native XML DBMS
Search engine

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

www.geomesa.org

www.sap.com/products/advantage-database-server.html

www.searchxml.net/category/products

Technical documentation

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

www.tiot.jp/riak-docs/riak/kv/latest

www.searchxml.net/support/handouts

Developer

CCRi and others

OpenSource, formerly Basho Technologies

Sybase, SAP

informationpartners gmbh

Initial release

2014

2009

1993

2015

Current release

5.0.0, May 2024

3.2.0, December 2022

1.0

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

C++

Server operating systems

Linux
OS X

Linux
Windows

Windows

Data scheme

yes

schema-free

yes

schema-free

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

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

HTTP API
Native Erlang Interface

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Delphi
Perl
PHP

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

Erlang

yes

on the application server

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

selectable replication factor

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

sychronisation to multiple collections

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

links between data sets can be stored

yes

Transaction concepts

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

ACID

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

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

caching of (temporary) tables can be configured

User concepts

Access control

yes

depending on the DBMS used for storage

yes, using Riak Security

fine grained access rights according to SQL-standard

Domain, group and role-based access control at the document level and for application services

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

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Basho to Bolster Riak with DB Plug-Ins
5 May 2014, Datanami

Basho Advances NoSQL Riak Enterprise 2.0 With Search, Advanced Data Types
15 September 2014, Data Center Knowledge

provided by Google News

SAP Announces Q3 2023 Results: Asia Pacific and Japan View
19 October 2023, SAP News

provided by Google News

Share this page