DBMS > Galaxybase vs. OrigoDB vs. Riak KV vs. SpatiaLite

System Properties Comparison Galaxybase vs. OrigoDB vs. Riak KV vs. SpatiaLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable, ACID-compliant native distributed parallel graph platform

A fully ACID in-memory object graph database

Distributed, fault tolerant key-value store

Spatial extension of SQLite

Primary database model

Graph DBMS

Document store
Object oriented DBMS

Key-value store

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

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#39	Graph DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

galaxybase.com

origodb.com

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

origodb.com/docs

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

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Robert Friberg et al

OpenSource, formerly Basho Technologies

Alessandro Furieri

Initial release

2017

2009

under the name LiveDB

2009

2008

Current release

Nov 20, November 2021

3.2.0, December 2022

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

C and Java

Erlang

C++

Server operating systems

Linux

Linux
Windows

Linux
OS X

server-less

Data scheme

Strong typed schema

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

.NET Client API
HTTP API
LINQ

HTTP API
Native Erlang Interface

Supported programming languages

Go
Java
Python

.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

user defined procedures and functions

yes

Erlang

Triggers

yes

Domain Events

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

depending on model

links between data sets can be stored

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

User concepts

Access control

Role-based access control

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.

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

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

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

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

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

provided by Google News

Share this page