Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
awesome-bigtable
:zap: Delightful list of Google Bigtable resources, packages and interesting finds.
https://github.com/zrosenbauer/awesome-bigtable
Last synced: about 6 hours ago
JSON representation
-
Resources
-
Articles & Blogs
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- Bigtable: A Distributed Storage System for Structured Data - Published on 2006.
- A NoSQL massively parallel table - Published on 2011-11.
- How we moved our Historical Stats from MySQL to Bigtable with zero downtime - Published on 2017-07.
- Medium @duhroach - Bigtable centric posts by Colt McAnlis, DA @ Google.
- Cloud Bigtable Performance 101 - Published on 2018-11.
- The right Cloud Bigtable index makes all the difference. - Published on 2019-1.
- Cloud Bigtable : Getting the geography right - Published on 2019-1.
- Using Cloud Bigtable Monitoring UI - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- Using Google Cloud Emulators in Integration Tests - Published on 2017-6.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
- Bigtable: storing Protobuf bytes in one column vs splitting the content into column families/qualifiers - Published on 2018-1.
- The Joy and Pain of using Google Bigtable - Published on 2019-1.
-
Tutorials
- Cloud Bigtable Examples - Repo containing official examples of using Bigtable.
- Introduction to Google Cloud Bigtable - CloudAcademy provided intro tutorial to Bigtable (membership required).
- Introduction to Google Cloud Bigtable - CloudAcademy provided intro tutorial to Bigtable (membership required).
-
-
Tools
-
Official Client Libraries
- C# - Official implementation of the Google Cloud Bigtable .NET client.
- Node.js - Official implementation of the Google Cloud Bigtable Node.js client.
- Python - Official implementation of the Google Cloud Bigtable python client.
- HappyBase - Official client which uses a HappyBase emulation layer which uses Bigtable as the underlying storage layer.
- Java - Official implementation of the Google Cloud Bigtable Java client.
- HBase Java - Official Java libraries and HBase client extensions for accessing Google Cloud Bigtable.
- PHP - Official implementation of the Google Cloud Bigtable PHP client.
- C++ - Official implementation of the Google Cloud Bigtable C++ client.
- Go - Official implementation of the Google Cloud Bigtable Go client.
-
Other Client Libraries
- Rust Bigtable - Rust library for working with Google Bigtable Data API.
- AsyncBigtable - Implementation of AsyncHBase but on top of Google's Cloud Bigtable service.
-
Command-line
-
GUI
- vscode-bigtable - VSCode extension that provides an easy to use GUI for querying bigtable instances.
-
Emulators
- Spotify Docker Bigtable - Docker container with an in memory implementation of Google Cloud Bigtable.
- Shopify Bigtable Emulator - In memory Go implementation of Bigtable.
- LittleTable - In-memory JVM-based emulator for Bigtable.
- Google Emulator - Official in-memory emulator for Cloud Bigtable, included with the Google Cloud SDK.
-
Databases
- Heroic - Scalable time series database based on Bigtable, Cassandra, and Elasticsearch.
- Janusgraph - Open-source, distributed graph database that can use Bigtable as its storage layer.
- GeoMesa - Suite of tools for working with big geo-spatial data in a distributed fashion, that can leverage Bigtable as its backend.
- GeoWave - Tool that provides geospatial and temporal indexing on top of Accumulo, HBase, Bigtable, Cassandra, and DynamoDB.
- HGraphDB - Client layer for using HBase (Bigtable) as a graph database.
- OpenTSDB - An Open Source Time Series Data Base that can levearge Bigtable as its storage layer.
- Cattle DB - Timeseries store built on top of Bigtable.
- YildizDB - Graph database layer on top of Bigtable.
-
-
Cool Stuff
-
Inspired by Bigtable
- Apache Accumulo - Sorted, distributed key/value store that provides robust, scalable data storage and retrieval.
- Tera - High performance distributed NoSQL database.
- obigstore - Database with Bigtable-like data model atop LevelDB.
- Apache HBase - The Hadoop database, a distributed, scalable, big data store.
-
Interesting Projects
- Bigtable Autoscaler - Service that autoscales Bigtable clusters based on CPU load.
- ![Mentioned in Awesome Bigtable - bigtable)
- YildizDB Bigtable - TypeScript Bigtable Client with 🔋🔋 included.
-
Categories
Sub Categories
Keywords
bigtable
9
hbase
5
big-data
3
graph-database
3
nodejs
3
database
3
google-cloud
3
cassandra
3
nosql
2
google-bigtable
2
elasticsearch
2
graph
2
java
2
tinkerpop
2
accumulo
2
google-pubsub
1
ha
1
monitoring
1
time-series
1
tsdb
1
vscode
1
gui
1
editor
1
client
1
google-cloud-platform
1
golang
1
go
1
gcp
1
cli
1
rust-library
1
dotnet
1
typescript
1
key-value
1
google
1
storage
1
data
1
c-plus-plus
1
baidu
1
samples
1
yildiz
1
nodes
1
hyper-relational
1
event-relation
1
edges
1
spatiotemporal
1
rocksdb
1
redis
1
kudu
1
geowave
1
geospatial-data
1