Google Cloud Bigtable

active

by Google · since 2015 · also known as Bigtable, Cloud Bigtable

Google's managed wide-column store, the original Bigtable, with HBase API and SQL access.

wide-columnkey-valuemanaged serviceproprietarymature

Overview

Cloud Bigtable is the externally offered version of the system that has backed Google Search, Maps and Gmail since the mid-2000s. You get a sorted, sparse, petabyte-scale table keyed by a single row key, with throughput that scales linearly by adding nodes and replication across clusters in multiple regions. It speaks the HBase client API and, since 2025, GoogleSQL for reads, and change streams feed Dataflow and BigQuery. It is excellent for time-series, ad-tech and ML feature serving where row-key design is everything, and a poor fit for small or relational datasets because of its per-node minimum cost.

Strengths & trade-offs

Strengths

  • +Linear throughput scaling by adding nodes, with consistent low-millisecond latency
  • +HBase API compatibility eases Hadoop migrations
  • +Multi-region replication with automatic failover routing
  • +Change streams and native BigQuery, Dataflow and Spark integration
  • +No storage limit per table; storage and compute scale independently

Trade-offs

  • −Single row key index; no secondary indexes
  • −Single-row atomicity only, no multi-row transactions
  • −Minimum node cost makes small workloads expensive
  • −GCP-only; hot-spotting from poor row-key design hurts badly

Great for

  • +Time-series and IoT telemetry
  • +Ad-tech user profiles and bidding data
  • +ML feature serving
  • +Financial market data
  • +HBase workloads moving to the cloud

Think twice for

  • −Relational data with joins
  • −Small datasets under ~1 TB
  • −Multi-row transactional consistency
  • −Multi-cloud deployments

Capabilities

Native or official first-party support · 8 of 25 tracked

✓Change data capture
✓TTL / expiry
✓Durable persistence
✓Compression
✓Encryption at rest
✓Role-based access
✓Time travel
✓Streaming ingest
–Transactions
–Joins
–Secondary indexes
–Full-text search
–Vector search
–Geospatial
–JSON
–Triggers
–Stored procedures
–Materialized views
–Pub/Sub
–Columnar storage
–In-memory
–Branching
–Online schema changes
–Offline sync
–Runs in WebAssembly

Scale & consistency

Comfortable data size
Massive · Multi-PB
Horizontal scaling
Native
Multi-region
Active active
Transactions
Limited ACID
Consistency
Strong, Eventual
Schema
Flexible
Architecture
Distributed, Shared storage
Query languages
Bigtable API, GoogleSQL

Storage separated from compute on Colossus; multi-cluster routing accepts writes in any replicated cluster with eventual consistency between them.

Deployment

Self-hosted Vendor-managed cloud Serverless Embedded Edge Kubernetes operator

available on · Google Cloud

Ecosystem

compatible withHBase
apis & protocolsgRPC Data API, HBase client API
client languagesJava, Go, Python, JavaScript, C++, C#, Ruby, PHP
used byGoogle, Spotify

Alternatives to Google Cloud Bigtable

Compare all→
Apache HBaseWide-Column26.6

Hadoop's Bigtable clone: strongly consistent wide-column tables on top of HDFS.

google-cloud-bigtable vs apache-hbase →
Amazon DynamoDBKey-Value63.3

AWS's serverless key-value and document store with single-digit-millisecond reads at any scale.

google-cloud-bigtable vs amazon-dynamodb →
Apache CassandraWide-Column55.9

Masterless wide-column database built for always-on writes across data centers.

google-cloud-bigtable vs apache-cassandra →
ScyllaDBWide-Column45.9

C++ rewrite of Cassandra with shard-per-core design; also speaks the DynamoDB API.

google-cloud-bigtable vs scylladb →
Google Cloud SpannerRelational34.5

Google's globally consistent, horizontally scaling SQL service with graph, vector and full-text built in.

google-cloud-bigtable vs google-cloud-spanner →
Azure Cosmos DBDocument45.3

Microsoft's globally distributed, multi-API NoSQL and vector database with SLA-backed latency.

google-cloud-bigtable vs azure-cosmos-db →

Google Cloud Bigtable FAQ

What is Google Cloud Bigtable?

Google Cloud Bigtable is a wide-column database by Google, first released in 2015. Cloud Bigtable is the externally offered version of the system that has backed Google Search, Maps and Gmail since the mid-2000s. You get a sorted, sparse, petabyte-scale table keyed by a single row key, with throughput that scales linearly by adding nodes and replication across clusters in multiple regions. It speaks the HBase client API and, since 2025, GoogleSQL for reads, and change streams feed Dataflow and BigQuery. It is excellent for time-series, ad-tech and ML feature serving where row-key design is everything, and a poor fit for small or relational datasets because of its per-node minimum cost.

Is Google Cloud Bigtable open source?

No. Google Cloud Bigtable is proprietary, closed-source software.

Does Google Cloud Bigtable support ACID transactions?

Partly. Google Cloud Bigtable offers limited ACID guarantees (for example, single-record or single-partition transactions), with strong, eventual consistency.

Does Google Cloud Bigtable scale horizontally?

Google Cloud Bigtable scales horizontally out of the box, with built-in sharding or partitioning. It is comfortable at massive scale (Multi-PB). It supports active-active multi-region writes.

How can I run Google Cloud Bigtable?

You can use the vendor's managed cloud. Managed offerings include Cloud Bigtable. It is available on Google Cloud.

What is Google Cloud Bigtable best for?

Google Cloud Bigtable is a strong fit for time-series and IoT telemetry; ad-tech user profiles and bidding data; and ML feature serving. Think twice for relational data with joins.

What are the best alternatives to Google Cloud Bigtable?

Common alternatives to Google Cloud Bigtable include Apache HBase, Amazon DynamoDB, Apache Cassandra, ScyllaDB and Google Cloud Spanner. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.

How popular is Google Cloud Bigtable?

Google Cloud Bigtable ranks #66 of 844 databases on the WhichDB Score (33.3/100), and #3 among wide-column databases. The score combines public adoption signals such as package downloads, GitHub activity, job posts and developer discussion.