DBMS > Google Cloud Datastore vs. HarperDB vs. PouchDB vs. SQLite

System Properties Comparison Google Cloud Datastore vs. HarperDB vs. PouchDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

Primary database model

Document store

Relational DBMS

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

cloud.google.com/datastore

www.harperdb.io

pouchdb.com

www.sqlite.org

Technical documentation

cloud.google.com/datastore/docs

docs.harperdb.io/docs

pouchdb.com/guides

www.sqlite.org/docs.html

Developer

Google

HarperDB

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2008

2017

2012

2000

Current release

3.1, August 2021

7.1.1, June 2019

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

free community edition available

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

Node.js

JavaScript

Server operating systems

hosted

Linux
OS X

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

server-less

Data scheme

schema-free

dynamic schema

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes, details here

yes

JSON data types

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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like data manipulation statements

yes

SQL-92 is not fully supported

APIs and other access methods

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

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

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

Server-side scripts

Stored procedures

using Google App Engine

Custom Functions

since release 3.1

View functions in JavaScript

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

A table resides as a whole on one (or more) nodes in a cluster

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

the nodes on which a table resides can be defined

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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.

Immediate Consistency

Eventual Consistency

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

yes, using LMDB

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

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

Access rights for users and roles

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.