DBMS > 4D vs. PouchDB vs. Riak TS vs. SQLite vs. VoltDB

System Properties Comparison 4D vs. PouchDB vs. Riak TS vs. SQLite vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

JavaScript DBMS with an API inspired by CouchDB

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Widely used embeddable, in-process RDBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

Technical documentation

developer.4d.com

pouchdb.com/guides

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

www.sqlite.org/docs.html

docs.voltdb.com

Developer

4D, Inc

Apache Software Foundation

Open Source, formerly Basho Technologies

Dwayne Richard Hipp

VoltDB Inc.

Initial release

1984

2012

2015

2000

2010

Current release

v20, April 2023

7.1.1, June 2019

3.0.0, September 2022

3.46.0 (23 May 2024), May 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Public Domain

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Erlang

Java, C++

Server operating systems

OS X
Windows

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

Linux
OS X

server-less

Linux
OS X

for development

Data scheme

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

yes

Secondary indexes

yes

via views

restricted

yes

SQL

Support of SQL

yes

close to SQL 92

yes, limited

yes

SQL-92 is not fully supported

yes

only a subset of SQL 99

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

HTTP REST

only for PouchDB Server
JavaScript API

HTTP API
Native Erlang Interface

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

4D proprietary IDE
PHP

JavaScript

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

View functions in JavaScript

Erlang

Java

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

selectable replication factor

none

Multi-source replication
Source-replica replication

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

links between datasets can be stored

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

Snapshots and command logging

In-memory capabilities

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

yes

User concepts

Access control

Users and groups

Users and roles with access to stored procedures

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.