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

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

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

A fully ACID in-memory object graph database

Distributed, fault tolerant key-value store

Primary database model

Document store
Relational DBMS

Spatial DBMS

Relational DBMS

Document store
Object oriented DBMS

Key-value store

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

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

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	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

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

Website

alasql.org

www.geomesa.org

www.oracle.com/database

origodb.com

Technical documentation

github.com/AlaSQL/alasql

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

docs.oracle.com/en/database

origodb.com/docs

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

Developer

Andrey Gershun & Mathias R. Wulff

CCRi and others

Oracle

Robert Friberg et al

OpenSource, formerly Basho Technologies

Initial release

2014

1980

2009

under the name LiveDB

2009

Current release

5.0.0, May 2024

23c, September 2023

3.2.0, December 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

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

Server operating systems

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

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

Linux
Windows

Linux
OS X

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

restricted

SQL

Support of SQL

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

yes

with proprietary extensions

APIs and other access methods

JavaScript API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

.NET Client API
HTTP API
LINQ

HTTP API
Native Erlang Interface

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

.Net

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

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

yes

Erlang

Triggers

yes

Domain Events

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding, horizontal partitioning

horizontal partitioning

client side managed; servers are not synchronized

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

Multi-source replication
Source-replica replication

Source-replica replication

selectable replication factor

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

Foreign keys

Referential integrity

yes

depending on model

links between data sets can be stored

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

Write ahead log

yes

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

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Role based authorization

yes, using Riak Security

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.