DBMS > Google Cloud Bigtable vs. Graph Engine vs. HBase vs. SQLite

System Properties Comparison Google Cloud Bigtable vs. Graph Engine vs. HBase vs. SQLite

Please select another system to include it in the comparison.

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.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store
Wide column store

Graph DBMS
Key-value store

Wide column store

Relational 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	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

cloud.google.com/bigtable

www.graphengine.io

hbase.apache.org

www.sqlite.org

Technical documentation

cloud.google.com/bigtable/docs

www.graphengine.io/docs/manual

hbase.apache.org/book.html

www.sqlite.org/docs.html

Developer

Google

Microsoft

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Dwayne Richard Hipp

Initial release

2015

2010

2008

2000

Current release

2.3.4, January 2021

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache version 2

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

.NET and C

Java

Server operating systems

hosted

.NET

Linux
Unix
Windows

using Cygwin

server-less

Data scheme

schema-free

yes

schema-free, schema definition possible

yes

dynamic column types

Typing

predefined data types such as float or date

yes

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

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

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

RESTful HTTP API

Java API
RESTful HTTP API
Thrift

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

C#
C++
F#
Visual Basic

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

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

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

Foreign keys

Referential integrity

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

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.