Bigtable

BigTable 是一种高效能的Google档案系统(Google File System, GFS)，用于储存大规模结构化资料，适用于云端计算。

BigTable 发展于 2004年^[1] 现今已成为 Google 的应用程式, 像是 MapReduce就常透过 BigTable来储存或更改资料,^[2]至于其他还有 Google Reader,^[3] Google Maps,^[4] Google Book Search, "My Search History", Google Earth, Blogger.com, Google Code hosting, Orkut,^[4] YouTube,^[5] and Gmail.^[6] Google自行发展出特别的巨型资料库的原因自然是效能的问题.^[7]

BigTable不是传统的关连性资料库，不支援 JOIN 这样的SQL语法, BigTable更像今日的NoSQL, 优势在于扩展性和性能。

注释

^ "First an overview. BigTable has been in development since early 2004 and has been in active use for about eight months (about February 2005)." Google's BigTable
^ "Bigtable can be used with MapReduce, a framework for running large-scale parallel computations developed at Google. We have written a set of wrappers that allow a Bigtable to be used both as an input source and as an output target for MapReduce jobs". pg 3 of "Bigtable: A Distributed Storage System for Structured Data", 2006
^ "Reader is using Google's BigTable in order to create a haven for what is likely to be a massive trove of items." Official Google Reader blog.
^ ^4.0 ^4.1 "There are currently around 100 cells for services such as Print, Search History, Maps, and Orkut." Google's BigTable
^ "Their new solution for thumbnails is to use Google’s BigTable, which provides high performance for a large number of rows, fault tolerance, caching, etc. This is a nice (and rare?) example of actual synergy in an acquisition." YouTube Scalability Talk
^ "How Entities and Indexes are Stored - Google App Engine - Google Code"
^ "We have described Bigtable, a distributed system for storing structured data at Google....Our users like the performance and high availability provided by the Bigtable implementation, and that they can scale the capacity of their clusters by simply adding more machines to the system as their resource demands change over time...Finally, we have found that there are significant advantages to building our own storage solution at Google. We have gotten a substantial amount of flexibility from designing our own data model for Bigtable." from the Conclusion of "Bigtable: A Distributed Storage System for Structured Data", 2006

[1st-blog-1] "First an overview. BigTable has been in development since early 2004 and has been in active use for about eight months (about February 2005)." Google's BigTable

[2] "Bigtable can be used with MapReduce, a framework for running large-scale parallel computations developed at Google. We have written a set of wrappers that allow a Bigtable to be used both as an input source and as an output target for MapReduce jobs". pg 3 of "Bigtable: A Distributed Storage System for Structured Data", 2006

[google-reader-3] "Reader is using Google's BigTable in order to create a haven for what is likely to be a massive trove of items." Official Google Reader blog.

[maps-orkut-4] 4.0 ^4.1 "There are currently around 100 cells for services such as Print, Search History, Maps, and Orkut." Google's BigTable

[5] "Their new solution for thumbnails is to use Google’s BigTable, which provides high performance for a large number of rows, fault tolerance, caching, etc. This is a nice (and rare?) example of actual synergy in an acquisition." YouTube Scalability Talk

[6] "How Entities and Indexes are Stored - Google App Engine - Google Code"

[7] "We have described Bigtable, a distributed system for storing structured data at Google....Our users like the performance and high availability provided by the Bigtable implementation, and that they can scale the capacity of their clusters by simply adding more machines to the system as their resource demands change over time...Finally, we have found that there are significant advantages to building our own storage solution at Google. We have gotten a substantial amount of flexibility from designing our own data model for Bigtable." from the Conclusion of "Bigtable: A Distributed Storage System for Structured Data", 2006

[1]

[2]

[3]

[4]

[5]

[6]

[7]