DBMS > Immudb vs. PouchDB vs. SQLite vs. TimescaleDB vs. Transbase

System Properties Comparison Immudb vs. PouchDB vs. SQLite vs. TimescaleDB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

Relational DBMS

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

Score	0.24
Rank	#305	Overall
	#43	Key-value stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

github.com/codenotary/immudb
immudb.io

pouchdb.com

www.sqlite.org

www.timescale.com

www.transaction.de/en/products/transbase.html

Technical documentation

docs.immudb.io

pouchdb.com/guides

www.sqlite.org/docs.html

docs.timescale.com

www.transaction.de/en/products/transbase/features.html

Developer

Codenotary

Apache Software Foundation

Dwayne Richard Hipp

Timescale

Transaction Software GmbH

Initial release

2020

2012

2000

2017

1987

Current release

1.2.3, April 2022

7.1.1, June 2019

3.45.3 (15 April 2024), April 2024

2.15.0, May 2024

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Public Domain

Open Source

Apache 2.0

commercial

free development license

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

Server operating systems

BSD
Linux
macOS
Solaris
Windows
z/OS

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

server-less

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

dynamic column types

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

SQL-like syntax

yes

SQL-92 is not fully supported

yes

full PostgreSQL SQL syntax

yes

APIs and other access methods

gRPC protocol
PostgreSQL wire protocol

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
Python

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

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

yes

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

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

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

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.