DBMS > PouchDB vs. SAP HANA vs. STSdb vs. TimescaleDB vs. TimesTen

System Properties Comparison PouchDB vs. SAP HANA vs. STSdb vs. TimescaleDB vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS with an API inspired by CouchDB

In-memory, column based data store. Available as appliance or cloud service

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

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

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Relational DBMS

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

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

pouchdb.com

www.sap.com/products/hana.html

github.com/STSSoft/STSdb4

www.timescale.com

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

Technical documentation

pouchdb.com/guides

help.sap.com/hana

docs.timescale.com

docs.oracle.com/database/timesten-18.1

Developer

Apache Software Foundation

SAP

STS Soft SC

Timescale

Oracle, TimesTen Performance Software, HP

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

Initial release

2012

2010

2011

2017

1998

Current release

7.1.1, June 2019

2.0 SPS07 (April 4, 2023), April 2023

4.0.8, September 2015

2.15.0, May 2024

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

commercial

Open Source

GPLv2, commercial license available

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

JavaScript

Server operating systems

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

Appliance or cloud-service

Windows

Linux
OS X
Windows

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

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

full PostgreSQL SQL syntax

yes

APIs and other access methods

HTTP REST

only for PouchDB Server
JavaScript API

JDBC
ODBC

.NET Client API

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

JavaScript

C#
Java

.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

SQLScript, R

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

yes

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

yes

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

Concurrency

Support for concurrent manipulation of data

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

yes

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.