DBMS > OrigoDB vs. PouchDB vs. SAP HANA vs. TimescaleDB

System Properties Comparison OrigoDB vs. PouchDB vs. SAP HANA vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A fully ACID in-memory object graph database

JavaScript DBMS with an API inspired by CouchDB

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

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

Primary database model

Document store
Object oriented DBMS

Document store

Relational DBMS

Time Series DBMS

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	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

origodb.com

pouchdb.com

www.sap.com/products/hana.html

www.timescale.com

Technical documentation

Developer

Robert Friberg et al

Apache Software Foundation

SAP

Timescale

Initial release

2009

under the name LiveDB

2012

2010

2017

Current release

7.1.1, June 2019

2.0 SPS07 (April 4, 2023), April 2023

2.15.0, May 2024

License

Commercial or Open Source

Open Source

commercial

Open Source

Apache 2.0

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

Linux
Windows

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

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

User defined using .NET types and collections

yes

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

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.

can be achieved using .NET

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

full PostgreSQL SQL syntax

APIs and other access methods

.NET Client API
HTTP API
LINQ

HTTP REST

only for PouchDB Server
JavaScript API

JDBC
ODBC

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

Supported programming languages

.Net

JavaScript

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

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

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

Sharding

with a proxy-based framework, named couchdb-lounge

yes

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

Source-replica replication with hot standby and reads on replicas

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

Foreign keys

Referential integrity

depending on model

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

Write ahead log

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

Role based authorization

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.