DBMS > Google Cloud Bigtable vs. HBase vs. PlanetScale vs. PouchDB vs. SQLite

System Properties Comparison Google Cloud Bigtable vs. HBase vs. PlanetScale vs. PouchDB vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Wide-column store based on Apache Hadoop and on concepts of BigTable

Scalable, distributed, serverless MySQL database platform built on top of Vitess

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store
Wide column store

Secondary database models

Document store
Spatial DBMS

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

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

cloud.google.com/bigtable

Technical documentation

cloud.google.com/bigtable/docs

hbase.apache.org/book.html

planetscale.com/docs

pouchdb.com/guides

www.sqlite.org/docs.html

Developer

Google

Apache Software Foundation

Apache top-level project, originally developed by Powerset

PlanetScale

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2015

2008

2020

2012

2000

Current release

2.3.4, January 2021

7.1.1, June 2019

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

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

hosted

Linux
Unix
Windows

using Cygwin

Docker
Linux
macOS

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

server-less

Data scheme

schema-free

schema-free, schema definition possible

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

options to bring your own types, AVRO

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

yes

with proprietary extensions

yes

SQL-92 is not fully supported

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Java API
RESTful HTTP API
Thrift

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Groovy
Java
PHP
Python
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

yes

Coprocessors in Java

yes

proprietary syntax

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

Multi-source replication
Source-replica replication

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency or Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

Atomic single-row operations

Single row ACID (across millions of columns)

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

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

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Users with fine-grained authorization concept

no user groups or 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.