bigtable vs cassandra vs simpledb vs dynamo vs couchdb vs hypertable和riak和hbase，他们有什么共同点？ [英] bigtable vs cassandra vs simpledb vs dynamo vs couchdb vs hypertable vs riak vs hbase, what do they have in common?

问题描述

如果这个问题有点主观，很抱歉。我是新的'可以存储'，'分布式存储'或一些这样的概念。我真的很想知道他们有什么共同点，并想了解所有的概述。

Sorry if this question is somewhat subjective. I am new to 'could store', 'distributed store' or some concepts like this. I really wonder what do they have in common and want to get an overview on all of them. What do I need to prepare if I want to write a product similar to this?

推荐答案

NoSQL数据库网站总结了这样的概念：

下一代数据库主要是
解决一些要点：正在
非关系，分布式，
开源和水平可扩展。
原来的意图是现代的
网络规模的数据库。运动
从2009年初开始，并迅速增长
。通常更多的特性
适用于：无模式，复制
支持，易于API，最终
一致性等。因此，
误导词nosql（社区
现在主要用not
only sql翻译）应该被视为别名
到类似定义
以上。

Next Generation Databases mostly address some of the points: being non-relational, distributed, open-source and horizontal scalable. The original intention has been modern web-scale databases. The movement began early 2009 and is growing rapidly. Often more characteristics apply as: schema-free, replication support, easy API, eventually consistency, and more. So the misleading term "nosql" (the community now translates it mostly with "not only sql") should be seen as an alias to something like the definition above.

该网站还维护 NoSQL数据库上的文章的归档。他们大多数似乎专注于特定的产品，但有一些更一般的概述。如果您认真建立自己的设计模式，请分布式设计模式非关系数据库对你需要考虑的事情进行了很好的整理。

That site also maintains an archive of articles on NoSQL databases. Most of them seem to focus on particular products but there are some more general overviews. If you are serious about building your own one then Design Patterns for Distributed Non-Relational Databases does a good round up of things you need to consider.

这篇关于bigtable vs cassandra vs simpledb vs dynamo vs couchdb vs hypertable和riak和hbase，他们有什么共同点？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！