DBMS > Apache IoTDB vs. Google Cloud Datastore vs. PouchDB vs. Prometheus vs. SQLite

System Properties Comparison Apache IoTDB vs. Google Cloud Datastore vs. PouchDB vs. Prometheus vs. SQLite

Editorial information provided by DB-Engines

Name

Description

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

JavaScript DBMS with an API inspired by CouchDB

Open-source Time Series DBMS and monitoring system

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

iotdb.apache.org

cloud.google.com/datastore

pouchdb.com

prometheus.io

www.sqlite.org

Technical documentation

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

cloud.google.com/datastore/docs

pouchdb.com/guides

prometheus.io/docs

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Google

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2018

2008

2012

2015

2000

Current release

1.1.0, April 2023

7.1.1, June 2019

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

JavaScript

Server operating systems

All OS with a Java VM (>= 1.8)

hosted

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

Linux
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

yes, details here

Numeric data only

yes

not rigid because of 'dynamic typing' concept.

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.

Import of XML data possible

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language (GQL)

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
Native API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

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

Server-side scripts

Stored procedures

yes

using Google App Engine

View functions in JavaScript

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

Multi-source replication using Paxos

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

by Federation

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

none

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

yes

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.