bigtable vs cassandra vs simpledb vs dynamo vs couchdb vs hypertable vs riak vs 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 数据库站点 总结了这个概念像这样:

The NoSQL Database site summarizes the concept like this:

主要是下一代数据库解决一些问题:非关系，分布式，开源和水平可扩展.初衷是现代的网络规模的数据库.运动始于 2009 年初，并且正在增长迅速.往往更多的特点申请为:无模式，复制支持，简单的 API，最终一致性等等.所以误导性术语nosql"(社区现在主要用不只有 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 数据库文章存档.他们中的大多数似乎都专注于特定产品，但也有一些更一般的概述.如果你真的想建立自己的，那么 分布式非设计模式-Relational Databases 很好地总结了您需要考虑的事情.

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 vs riak vs hbase，它们有什么共同点?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！