使用CouchDB和Couchbase困惑 [英] Confused with CouchDB and Couchbase
问题描述
我调查的CouchDB和Couchbase，因为我在寻找一个web应用程序，我将最终能够使成原生的Android / iOS应用程序，以及一个数据库解决方案。据我了解，CouchDB的/ Couchbase擅长能够使用数据库脱机并使其尽快恢复连接同步。
I'm investigating CouchDB and Couchbase as I am looking for a DB solution for a web application that I will eventually be able to make into a native Android/iOS app as well. From what I understand, CouchDB/Couchbase excel at being able to use the DB offline and have it synchronize as soon as the connection is restored.
我进一步了解到的CouchDB和Couchbase 2个不同的产品，从2个不同的组织 - CouchDB是由Apache和Couchbase是Couchbase。有一个在所以这里了很大的反响解释一些差异的。
I further understand that CouchDB and Couchbase are 2 distinct products from 2 different organizations - CouchDB is from Apache and Couchbase is from Couchbase. There is a great response in SO here explaining some of the differences.
Couchbase有 Couchbase - 精简版，Android版，并针对iOS类似原生内置的DB移动应用它与Couchbase服务器同步。
Couchbase has Couchbase-Lite-Android and similar for iOS as native embedded DBs for mobile apps which sync with Couchbase server.
我在哪里迷路是，当我试图找到CouchDB的等价物。 24，一切都TouchDB然后说，这已不再是积极发展，而是指向Couchbase - 精简版，Android作为已superceeded它的项目。但确实Couchbase名录-的Android / iOS版同步使用CouchDB或者只是Couchbase？根据维基，表明它可以使用CouchDB同步，但它是用于接收低优先级和/或缺陷修复仲后端。
Where I get lost is when I try to find the CouchDB equivalent. Everything points to TouchDB which then says it is no longer actively developed and instead points to Couchbase-Lite-Android as the project that has superceeded it. But does Couchbase-List-Android/iOS sync with CouchDB or just Couchbase? According to the Wiki, it indicates that it can sync with CouchDB, but it is a secondary backend which receives lower priority and/or bug fixes.
，那么什么是应该用来为Android / iOS版的CouchDB的嵌入式/移动版本？
So then what are the embedded/mobile versions of CouchDB that should be used for Android/iOS?
推荐答案
这是 Couchbase精简版
我这里回答过类似的问题/混淆。
TouchDB被建立适合嵌入到移动/桌面应用程序的一个Apache CouchDB的兼容的数据库引擎。这里的兼容因素是CouchDB的复制协议和放大器; NoSQL的数据模型。
I've answered a similar question/confusion over here. TouchDB was built to be an Apache-CouchDB compatible database engine suitable for embedding into mobile/desktop apps. The compatible factor here is CouchDB's replication protocol & NoSQL data model.
在一个过程提供移动同步为Couchbase Server的功能，他们修改并更名为TouchDB Couchbase精简版还内置 SYNC网关来充当之间的服务器端桥Couchbase Server和Couchbase精简版。
In a process to offer mobile synchronization as a feature of Couchbase Server, they altered and renamed TouchDB as Couchbase Lite and also, built Sync Gateway to act as a server-side bridge between Couchbase Server and Couchbase Lite.
但是，数据模型和放大器;复制协议仍然是相同的Apache的CouchDB的和Couchbase精简版的复制是使用CouchDB完全兼容。
But the data model & replication protocol are still the same as Apache-CouchDB and Couchbase Lite's replication is entirely compatible with CouchDB.
要总结，Couchbase精简版＆LT; -sync-> Apache的CouchDB的＆放大器; Couchbase精简版＆LT; -sync->（通过SYNC网关）Couchbase服务器
To conclude, Couchbase Lite <-sync-> Apache-CouchDB & Couchbase Lite <-sync-> (via Sync Gateway) Couchbase Server.
我怀疑，CouchDB是接收较低优先级和/或错误修复次要后端。我们一直在使用Couchbase精简版，因为TouchDB的日子和国际海事组织，Couchbase，精简版正在积极开发和大力支持。
I doubt that CouchDB is a secondary backend which receives lower priority and/or bug fixes. We've been using Couchbase Lite since the days of TouchDB and IMO, Couchbase-Lite is actively developed and greatly supported.
这篇关于使用CouchDB和Couchbase困惑的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
