DBMS > PouchDB vs. Sequoiadb vs. TerarkDB vs. Vitess

System Properties Comparison PouchDB vs. Sequoiadb vs. TerarkDB vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS with an API inspired by CouchDB

NewSQL database with distributed OLTP and SQL

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store

Document store
Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.28
Rank	#115	Overall
	#21	Document stores

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

pouchdb.com

www.sequoiadb.com

github.com/bytedance/terarkdb

vitess.io

Technical documentation

pouchdb.com/guides

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

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

vitess.io/docs

Developer

Apache Software Foundation

Sequoiadb Ltd.

ByteDance, originally Terark

The Linux Foundation, PlanetScale

Initial release

2012

2013

2016

2013

Current release

7.1.1, June 2019

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Server: AGPL; Client: Apache V2

commercial

restricted open source version available

Open Source

Apache Version 2.0, commercial licenses 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

JavaScript

C++

Server operating systems

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

Linux

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

HTTP REST

only for PouchDB Server
JavaScript API

proprietary protocol using JSON

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

JavaScript

.Net
C++
Java
PHP
Python

C++
Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

View functions in JavaScript

JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Source-replica replication

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

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Document is locked during a transaction

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

simple password-based access control

Users with fine-grained authorization concept

no user groups or roles

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

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.com

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

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

provided by Google News

Share this page