跳转到内容

Bigtable：修订间差异

本页使用了标题或全文手工转换
维基百科，自由的百科全书
以互动方式浏览历史
←上一版本
删除的内容 添加的内容
可视化wikitext
南方的小鳥（留言 | 贡献）
555次编辑
小 南方的小鳥 已移動頁面 BigTable 至 Cloud Bigtable
小无编辑摘要
 
（未显示4个用户的9个中间版本）
第5行： 第5行：
'''BigTable'''是一種[[数据压缩|壓縮]]的、高效能的、高可擴展性的，基于[[Google檔案系統]]（Google File System，GFS）的数据存储系统，用於儲存大规模結構化数据，適用於[[雲端計算]]。
'''BigTable'''是一種[[数据压缩|壓縮]]的、高效能的、高可擴展性的，基于[[Google檔案系統]]（Google File System，GFS）的数据存储系统，用於儲存大规模結構化数据，適用於[[雲端計算]]。


BigTable發展於2004年<ref name="1st-blog">"First an overview. BigTable has been in development since early 2004 and has been in active use for about eight months (about February 2005)." [http://andrewhitchcock.org/?post=214 Google's BigTable]</ref>，現今已成為Google的應用程式。像是[[MapReduce]]就常透過BigTable來儲存或更改資料，<ref>"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</ref>其他還有[[Google Reader]]<ref name="google-reader">"Reader is using Google's BigTable in order to create a haven for what is likely to be a massive trove of items." [http://googlereader.blogspot.com/2005/10/google-reader-two-weeks.html Official Google Reader] blog.</ref>、[[Google Maps]]<ref name="maps-orkut">"There are currently around 100 cells for services such as Print, Search History, Maps, and Orkut." [http://andrewhitchcock.org/?post=214 Google's BigTable]</ref>、[[Google Book Search]]、"My Search History"、[[Google Earth]]、[[Blogger.com]]、[[Google Code]] hosting、[[Orkut]]<ref name="maps-orkut"/>、[[YouTube]]<ref>"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." [http://kylecordes.com/2007/07/12/youtube-scalability/ YouTube Scalability Talk]</ref>以及[[Gmail]]<ref>[http://code.google.com/intl/pl/appengine/articles/storage_breakdown.html#anc-background "How Entities and Indexes are Stored - Google App Engine - Google Code"]</ref>等。Google自行發展出特別的巨型資料庫的原因，自然是效能的問題<ref>"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</ref>。
BigTable發展於2004年<ref name="1st-blog">"First an overview. BigTable has been in development since early 2004 and has been in active use for about eight months (about February 2005)." [http://andrewhitchcock.org/?post=214 Google's BigTable] {{Wayback|url=http://andrewhitchcock.org/?post=214 |date=20060616203323 }}</ref>，現今已成為Google的應用程式。像是[[MapReduce]]就常透過BigTable來儲存或更改資料，<ref>"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</ref>其他還有[[Google Reader]]<ref name="google-reader">"Reader is using Google's BigTable in order to create a haven for what is likely to be a massive trove of items." [http://googlereader.blogspot.com/2005/10/google-reader-two-weeks.html Official Google Reader] {{Wayback|url=http://googlereader.blogspot.com/2005/10/google-reader-two-weeks.html |date=20110708041343 }} blog.</ref>、[[Google Maps]]<ref name="maps-orkut">"There are currently around 100 cells for services such as Print, Search History, Maps, and Orkut." [http://andrewhitchcock.org/?post=214 Google's BigTable] {{Wayback|url=http://andrewhitchcock.org/?post=214 |date=20060616203323 }}</ref>、[[Google Book Search]]、"My Search History"、[[Google Earth]]、[[Blogger.com]]、[[Google Code]] hosting、[[Orkut]]<ref name="maps-orkut"/>、[[YouTube]]<ref>"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." [http://kylecordes.com/2007/07/12/youtube-scalability/ YouTube Scalability Talk] {{Wayback|url=http://kylecordes.com/2007/07/12/youtube-scalability/ |date=20100410072851 }}</ref>以及[[Gmail]]<ref>{{Cite web |url=http://code.google.com/intl/pl/appengine/articles/storage_breakdown.html#anc-background |title="How Entities and Indexes are Stored - Google App Engine - Google Code" |accessdate=2011-04-05 |archive-date=2011-10-06 |archive-url=https://web.archive.org/web/20111006163250/http://code.google.com/intl/pl/appengine/articles/storage_breakdown.html#anc-background |dead-url=no }}</ref>等。Google自行發展出特別的巨型資料庫的原因，自然是效能的問題<ref>"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</ref>。


BigTable不是传统的[[关系型数据库]]，不支援JOIN这样的[[SQL]]語法，BigTable更像今日的[[NoSQL]]的Table-oriented，优势在于扩展性和性能。BigTable的Table資料結構包括row key、col key和timestamp，其中row key用於儲存倒轉的[[URL]]，例如www.google.com必須改成com.google.www。BigTable使用大量的Table，在Table之下還有Tablet。每一個Tablets大概有100-200MB，每台机器有100個左右的Tablets。所謂的Table是屬於immutable的SSTables，也就是存储方式不可修改。另外Table還必須進行壓縮，其壓縮又分成table的壓縮或系統的壓縮。客户端有一指向META0的Tablets的指標，METAO tablets保儲所有的META1的tablets的資料記錄。
BigTable不是传统的[[关系型数据库]]，不支援JOIN这样的[[SQL]]語法，BigTable更像今日的[[NoSQL]]的Table-oriented，优势在于扩展性和性能。BigTable的Table資料結構包括row key、col key和timestamp，其中row key用於儲存倒轉的[[URL]]，例如www.google.com必須改成com.google.www。BigTable使用大量的Table，在Table之下還有Tablet。每一個Tablets大概有100-200MB，每台机器有100個左右的Tablets。所謂的Table是屬於immutable的SSTables，也就是存储方式不可修改。另外Table還必須進行壓縮，其壓縮又分成table的壓縮或系統的壓縮。客户端有一指向META0的Tablets的指標，META0 tablets保儲所有的META1的tablets的資料記錄。


==相關條目==
==相關條目==
第16行： 第16行：


==外部連結==
==外部連結==
*[http://research.google.com/archive/bigtable.html Bigtable: A Distributed Storage System for Structured Data] -（official paper; [http://research.google.com/archive/bigtable-osdi06.pdf PDF]）
*[http://research.google.com/archive/bigtable.html Bigtable: A Distributed Storage System for Structured Data]{{Wayback|url=http://research.google.com/archive/bigtable.html |date=20150208070244 }} -（official paper; [http://research.google.com/archive/bigtable-osdi06.pdf PDF]{{Wayback|url=http://research.google.com/archive/bigtable-osdi06.pdf |date=20091214180249 }}）
*[http://www.cs.washington.edu/htbin-post/mvis/mvis?ID=437 BigTable: A Distributed Structured Storage System]（[http://video.google.com/videoplay?docid=7278544055668715642 video]）
*[http://www.cs.washington.edu/htbin-post/mvis/mvis?ID=437 BigTable: A Distributed Structured Storage System]（[http://video.google.com/videoplay?docid=7278544055668715642 video]{{Wayback|url=http://video.google.com/videoplay?docid=7278544055668715642 |date=20110418072707 }}）
**[http://www.uwtv.org/programs/displayevent.asp?rid=2787 more video]
**[https://web.archive.org/web/20060615164406/http://www.uwtv.org/programs/displayevent.asp?rid=2787 more video]
**[http://andrewhitchcock.org/?post=214 Google's BigTable] -（notes on the official presentation）
**[https://web.archive.org/web/20060616203323/http://andrewhitchcock.org/?post=214 Google's BigTable] -（notes on the official presentation）
*[http://www.baselinemag.com/article2/0,1540,1985047,00.asp "How Google Works"]
*[http://www.baselinemag.com/article2/0,1540,1985047,00.asp "How Google Works"]{{Dead link}}
*[http://www.readwriteweb.com/archives/is_the_relational_database_doomed.php Is the Relational Database Doomed ?]
*[https://web.archive.org/web/20090504062325/http://www.readwriteweb.com/archives/is_the_relational_database_doomed.php Is the Relational Database Doomed ?]


{{NoSQL}}
{{NoSQL}}
{{Google Inc.}}
{{Google Inc.}}
{{Google Cloud}}


[[category:数据库]]
[[Category:数据库]]
[[Category:Google]]
[[Category:Google]]
[[Category:NoSQL]]
[[Category:键-值数据库]]

2021年5月19日 (三) 10:19的最新版本

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]以及Gmail[6]等。Google自行發展出特別的巨型資料庫的原因，自然是效能的問題[7]。

BigTable不是传统的关系型数据库，不支援JOIN这样的SQL語法，BigTable更像今日的NoSQL的Table-oriented，优势在于扩展性和性能。BigTable的Table資料結構包括row key、col key和timestamp，其中row key用於儲存倒轉的URL，例如www.google.com必須改成com.google.www。BigTable使用大量的Table，在Table之下還有Tablet。每一個Tablets大概有100-200MB，每台机器有100個左右的Tablets。所謂的Table是屬於immutable的SSTables，也就是存储方式不可修改。另外Table還必須進行壓縮，其壓縮又分成table的壓縮或系統的壓縮。客户端有一指向META0的Tablets的指標，META0 tablets保儲所有的META1的tablets的資料記錄。

相關條目

[编辑]
  • LevelDB - Google的鍵／值對（Key/Value Pair）嵌入式數據庫管理系統編程庫，BSD特許條款開源

注釋

[编辑]
  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
  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.
  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". [2011-04-05]. （原始内容存档于2011-10-06）. 
  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

外部連結

[编辑]
检索自“https://zh.wikipedia.org/zhwiki/w/index.php?title=Bigtable&oldid=65698396”