DBMS > Altibase vs. Apache IoTDB vs. PouchDB vs. SQLite vs. TerminusDB

System Properties Comparison Altibase vs. Apache IoTDB vs. PouchDB vs. SQLite vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

An enterprise grade, high-performance RDBMS

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store
RDF store

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

Score	1.07
Rank	#186	Overall
	#87	Relational DBMS

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

pouchdb.com/guides

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

Developer

Altibase

Apache Software Foundation

Dwayne Richard Hipp

DataChemist Ltd.

Initial release

1999

2018

2012

2000

2018

Current release

v7.3, 2023, August 2023

1.1.0, April 2023

7.1.1, June 2019

3.45.3 (15 April 2024), April 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

Open Source

Apache Version 2.0

Open Source

Public Domain

Open Source

GPL V3

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

C++

Java

JavaScript

Prolog, Rust

Server operating systems

AIX
HP-UX
Linux

All OS with a Java VM (>= 1.8)

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

server-less

Linux

Data scheme

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

ANSI SQL-92

SQL-like query language

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC
Proprietary protocol

JDBC
Native API

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C
C++
Java

C
C#
C++
Go
Java
Python
Scala

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

JavaScript
Python

Server-side scripts

Stored procedures

stored procedures and stored functions

yes

View functions in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

Sharding

with a proxy-based framework, named couchdb-lounge

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong Consistency with Raft

Eventual Consistency

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

via file-system locks

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

in-memory journaling

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

yes

Role-based access control

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.