DBMS > AlaSQL vs. GeoMesa vs. Oracle vs. Riak KV vs. Tarantool

System Properties Comparison AlaSQL vs. GeoMesa vs. Oracle vs. Riak KV vs. Tarantool

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.

Widely used RDBMS

Distributed, fault tolerant key-value store

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Relational DBMS

Spatial DBMS

Relational DBMS

Key-value store

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

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

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

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

alasql.org

www.geomesa.org

www.oracle.com/database

www.tarantool.io

Technical documentation

github.com/AlaSQL/alasql

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

docs.oracle.com/en/database

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

www.tarantool.io/en/doc

Developer

Andrey Gershun & Mathias R. Wulff

CCRi and others

Oracle

OpenSource, formerly Basho Technologies

Initial release

2014

1980

2009

2008

Current release

5.0.0, May 2024

23c, September 2023

3.2.0, December 2022

2.10.0, May 2022

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

Apache version 2, commercial enterprise edition

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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++

Erlang

C and C++

Server operating systems

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

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux
OS X

BSD
Linux
macOS

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

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

yes

with proprietary extensions

Full-featured ANSI SQL support

APIs and other access methods

JavaScript API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP API
Native Erlang Interface

Open binary protocol

Supported programming languages

JavaScript

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

Erlang

Lua, C and SQL stored procedures

Triggers

yes

pre-commit hooks and post-commit hooks

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding, horizontal partitioning

Sharding

no "single point of failure"

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

Multi-source replication
Source-replica replication

selectable replication factor

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

depending on storage layer

Immediate Consistency

Eventual Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

isolation level can be parameterized

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

yes, write ahead 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

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes, full featured in-memory storage engine with persistence

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

yes, using Riak Security

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.