DBMS > Drizzle vs. PouchDB vs. Riak TS vs. YottaDB

System Properties Comparison Drizzle vs. PouchDB vs. Riak TS vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

A fast and solid embedded Key-value store

Primary database model

Secondary database models

Relational DBMS

using the Octo plugin

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

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

pouchdb.com

yottadb.com

Technical documentation

pouchdb.com/guides

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

yottadb.com/resources/documentation

Developer

Drizzle project, originally started by Brian Aker

Apache Software Foundation

Open Source, formerly Basho Technologies

YottaDB, LLC

Initial release

2008

2012

2015

2001

Current release

7.2.4, September 2012

7.1.1, June 2019

3.0.0, September 2022

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

AGPL 3.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

C++

JavaScript

Erlang

Server operating systems

FreeBSD
Linux
OS X

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

Linux
OS X

Docker
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

via views

restricted

SQL

Support of SQL

yes

with proprietary extensions

yes, limited

by using the Octo plugin

APIs and other access methods

JDBC

HTTP REST

only for PouchDB Server
JavaScript API

HTTP API
Native Erlang Interface

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

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

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

View functions in JavaScript

Erlang

Triggers

hooks for callbacks inside the server can be used.

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

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

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users and groups based on OS-security mechanisms

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

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

New kids on the block: database management systems implemented in JavaScript
1 December 2014, Matthias Gelbmann

show all

Recent citations in the news

Building an Offline First App with PouchDB — SitePoint
10 March 2014, SitePoint

Getting Started with PouchDB Client-Side JavaScript Database — SitePoint
7 September 2016, SitePoint

3 Reasons To Think Offline First
22 March 2017, IBM

Create Offline Web Apps Using Service Workers & PouchDB — SitePoint
7 March 2017, SitePoint

Offline-first web and mobile apps: Top frameworks and components
22 January 2019, TechBeacon

provided by Google News

Share this page