DBMS > Apache Drill vs. Riak KV vs. searchxml vs. STSdb

System Properties Comparison Apache Drill vs. Riak KV vs. searchxml vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Distributed, fault tolerant key-value store

DBMS for structured and unstructured content wrapped with an application server

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Relational DBMS

Key-value store

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

Native XML DBMS
Search engine

Key-value store

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

drill.apache.org

www.searchxml.net/category/products

github.com/STSSoft/STSdb4

Technical documentation

drill.apache.org/docs

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

www.searchxml.net/support/handouts

Developer

Apache Software Foundation

OpenSource, formerly Basho Technologies

informationpartners gmbh

STS Soft SC

Initial release

2012

2009

2015

2011

Current release

1.20.3, January 2023

3.2.0, December 2022

1.0

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache version 2, commercial enterprise edition

commercial

Open Source

GPLv2, commercial license available

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

Erlang

C++

Server operating systems

Linux
OS X
Windows

Linux
OS X

Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

restricted

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

HTTP API
Native Erlang Interface

RESTful HTTP API
WebDAV
XQuery
XSLT

.NET Client API

Supported programming languages

C++

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

most other programming languages supported via APIs

C#
Java

Server-side scripts

Stored procedures

user defined functions

Erlang

yes

on the application server

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

sychronisation to multiple collections

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

User concepts

Access control

Depending on the underlying data source

yes, using Riak Security

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

Recent citations in the news

Apache Drill case study: A tutorial on processing CSV files
9 June 2016, TheServerSide.com

Analyse Kafka messages with SQL queries using Apache Drill
23 September 2019, Towards Data Science

Apache Drill Poised to Crack Tough Data Challenges
19 May 2015, Datanami

Apache Drill Eliminates ETL, Data Transformation for MapR Database
11 April 2016, The New Stack

Drill Mines Diverse Data Sets, Google Style
20 May 2015, The Next Platform

provided by Google 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

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 distributes Riak to more customers - DCD
28 November 2013, DatacenterDynamics

provided by Google News

Share this page