问题描述
我最近听说过很多关于的问题，并对其提供的内容感到困惑。
I've heard a lot about couchdb lately, and am confused about what it offers.
推荐答案
很难解释严格优势/劣势形式的所有差异。
It's hard to explain all the differences in strict advantage/disadvantage form.
我建议和CouchDB一起玩一点。你会注意到的第一件事是，在初始使用期间的学习曲线完全从RDBMS反转。
I would suggest playing with CouchDB a little yourself. The first thing you'll notice is that the learning curve during initial usage is totally inverted from RDBMS.
使用RDBMS，你花费了很多前期时间建模你的真实世界数据将其导入到数据库。一旦你处理了建模，你可以做各种查询。
With RDBMS you spend a lot of up front time modeling your real world data to get it in to the Database. Once you've dealt with the modeling you can do all kinds of queries.
使用CouchDB，你只是得到所有的JSON数据并存储在DB中，分钟。你不需要做任何规范化或类似的东西，传输是HTTP，所以你有很多客户端选项。
With CouchDB you just get all your data in JSON and stored in the DB in, literally, minutes. You don't need to do any normalization or anything like that, and the transport is HTTP so you have plenty of client options.
然后你会注意到一个大的学习写入映射函数时学习曲线，以及学习键排序规则是如何工作的，以及针对您写的视图的查询。一旦你学习了它们，你就会开始看到视图如何允许你正常化索引，同时保持数据不规范化和自然。
Then you'll notice a big learning curve when writing map functions and learning how the key collation works and the queries against the views you write. Once you learn them, you'll start to see how views allow you to normalize the indexes while leaving the data un-normalized and "natural".
这篇关于CouchDB和RDBMS的优点是什么的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！