DBMS > BaseX vs. EsgynDB vs. FatDB vs. Riak KV

System Properties Comparison BaseX vs. EsgynDB vs. FatDB vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Distributed, fault tolerant key-value store

Primary database model

Native XML DBMS

Relational DBMS

Document store
Key-value store

Key-value store

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

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

Score	1.56
Rank	#141	Overall
	#4	Native XML DBMS

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Website

basex.org

www.esgyn.cn

Technical documentation

docs.basex.org

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

Developer

BaseX GmbH

Esgyn

FatCloud

OpenSource, formerly Basho Technologies

Initial release

2007

2015

2012

2009

Current release

11.2, August 2024

3.2.0, December 2022

License

Commercial or Open Source

Open Source

BSD license

commercial

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

Java

C++, Java

Erlang

Server operating systems

Linux
OS X
Windows

Linux

Windows

Linux
OS X

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

XQuery supports types

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

restricted

SQL

Support of SQL

yes

Via inetgration in SQL Server

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

ADO.NET
JDBC
ODBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

HTTP API
Native Erlang Interface

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

All languages supporting JDBC/ODBC/ADO.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

yes

Java Stored Procedures

yes

via applications

Erlang

Triggers

yes

via events

yes

via applications

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication between multi datacenters

selectable replication factor

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
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

multiple readers, single writer

ACID

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.

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

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

Recent citations in the news

XML Injection Attacks: What to Know About XPath, XQuery, XXE & More
18 May 2022, Hashed Out by The SSL Store™

9 Skills You Need to Become a Data Engineer
2 November 2022, KDnuggets

provided by Google News

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

Top 8 Best NoSQL Databases in 2024
9 September 2024, AIM

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

If you wagered Bet365 would buy up Basho's remains, you'd be a big winner right now
25 August 2017, The Register

provided by Google News

Share this page