本文介绍了Google Cloud Bigtable 与 Google Cloud Datastore的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
Google Cloud Bigtable 之间有什么区别和 Google Cloud Datastore/App Engine 数据存储区,主要的实际优势/劣势是什么?AFAIK Cloud Datastore 建立在 Bigtable 之上.
What is the difference between Google Cloud Bigtable and Google Cloud Datastore / App Engine datastore, and what are the main practical advantages/disadvantages? AFAIK Cloud Datastore is build on top of Bigtable.
推荐答案基于使用 Datastore 和阅读 Bigtable 的经验 docs,主要区别是:
Based on experience with Datastore and reading the Bigtable docs, the main differences are:
- Bigtable 最初是为与 HBase 兼容而设计的,但现在具有多种语言的客户端库.Datastore 最初更适合 Python/Java/Go 网络应用程序开发人员(最初是 App Engine)
- Bigtable 比 Datastore 更多一点 IaaS",因为它不是就在那里",而是需要一个集群已配置.
- Bigtable 只支持一个索引——行键"(Datastore 中的实体键)
- 这意味着查询是在 Key 上进行的,这与 Datastore 的索引属性不同
- Bigtable was originally designed for HBase compatibility, but now has client libraries in multiple languages. Datastore was originally more geared towards Python/Java/Go web app developers (originally App Engine)
- Bigtable is 'a bit more IaaS' than Datastore in that it's not 'just there' but requires a cluster to be configured.
- Bigtable supports only one index - the 'row key' (the entity key in Datastore)
- This means queries are on the Key, unlike Datastore's indexed properties
- 数据存储区针对读/写操作、存储和带宽收费
- Bigtable 费用节点"、存储和带宽
- Datastore charges for read/write operations, storage and bandwidth
- Bigtable charges for 'nodes', storage and bandwidth
更多推荐
Google Cloud Bigtable 与 Google Cloud Datastore
发布评论