DBMS > PouchDB vs. SQLite vs. SwayDB vs. TimescaleDB vs. TimesTen

System Properties Comparison PouchDB vs. SQLite vs. SwayDB vs. TimescaleDB vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

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

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

In-Memory RDBMS compatible to Oracle

Primary database model

Secondary database models

Relational DBMS

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

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

pouchdb.com/guides

www.sqlite.org/docs.html

docs.timescale.com

docs.oracle.com/database/timesten-18.1

Developer

Apache Software Foundation

Dwayne Richard Hipp

Simer Plaha

Timescale

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2012

2000

2018

2017

1998

Current release

7.1.1, June 2019

3.46.0 (23 May 2024), May 2024

2.15.0, May 2024

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Public Domain

Open Source

GNU Affero GPL V3.0

Open Source

Apache 2.0

commercial

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

Scala

Server operating systems

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

server-less

Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

schema-free

yes

dynamic column types

schema-free

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

full PostgreSQL SQL syntax

yes

APIs and other access methods

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

JavaScript

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

Java
Kotlin
Scala

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

none

yes, across time and space (hash partitioning) attributes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

Source-replica replication with hot standby and reads on replicas

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

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

by means of logfiles and checkpoints

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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.