DBMS > EJDB vs. Riak KV vs. Sequoiadb vs. SwayDB

System Properties Comparison EJDB vs. Riak KV vs. Sequoiadb vs. SwayDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Distributed, fault tolerant key-value store

NewSQL database with distributed OLTP and SQL

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Document store

Key-value store

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

Document store
Relational DBMS

Key-value store

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

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

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

github.com/Softmotions/ejdb

www.sequoiadb.com

swaydb.simer.au

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

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

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Softmotions

OpenSource, formerly Basho Technologies

Sequoiadb Ltd.

Simer Plaha

Initial release

2012

2009

2013

2018

Current release

3.2.0, December 2022

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache version 2, commercial enterprise edition

Open Source

Server: AGPL; Client: Apache V2

Open Source

GNU Affero GPL V3.0

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

Scala

Server operating systems

server-less

Linux
OS X

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

oid, date, timestamp, binary, regex

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

restricted

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

in-process shared library

HTTP API
Native Erlang Interface

proprietary protocol using JSON

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

.Net
C++
Java
PHP
Python

Java
Kotlin
Scala

Server-side scripts

Stored procedures

Erlang

JavaScript

Triggers

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"

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

links between data sets can be stored

Transaction concepts

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

Document is locked during a transaction

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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.

yes

User concepts

Access control

yes, using Riak Security

simple password-based access control

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

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

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

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

provided by Google News

Share this page