2.0 版本里产品被分成了 Membase,Memcached 和 Single,而每个产品又被进一步分成了 Enterprise 和 Community 版本。在目前产品还比较单薄的情况下,这么分下去实在是有点折腾。
且不说 2.0 版本的有点吓人的 Enterprise 授权费用。
大家有在自己的项目中使用 CouchDB 么?对现状和未来有什么想法么? ]]>CouchConf World Tourtag:www.v2ex.com,2011-09-11:/t/180112011-09-11T08:40:53Z2011-09-12T08:40:53ZLividmember/Lividhttp://www.couchbase.com/couchconf-world-tour ]]>Kanso, The surprisingly simple way to write CouchAppstag:www.v2ex.com,2011-05-09:/t/127972011-05-09T16:04:03Z2011-09-24T21:38:05Zlainuomember/lainuo http://lainuo.couchone.com//traces/_design/traces_couch/_list/articles/articles
项目主页是: http://kansojs.org/ ]]>Couchbase for iOStag:www.v2ex.com,2011-05-02:/t/124312011-05-02T06:56:25Z2011-05-03T06:56:26ZLividmember/Lividhttps://github.com/couchbaselabs/iOS-Couchbase ]]>CouchOne Hosting Updatetag:www.v2ex.com,2010-12-01:/t/52772010-12-01T21:23:40Z2010-12-03T03:14:34ZLividmember/Livid * SSL support * GeoCouch geolocation support
BigCouch for clusters. ]]>Couch.io is now CouchOnetag:www.v2ex.com,2010-09-24:/t/28392010-09-24T17:17:22Z2010-09-25T19:47:19ZLividmember/Lividhttp://www.couch.io/
所有的这些麻烦都提醒我 Project Babel 0.6 曾经存在过。 ]]>BBC x CouchDBtag:www.v2ex.com,2010-09-03:/t/22652010-09-03T11:02:04Z2010-09-04T11:38:53ZLividmember/Lividhttp://www.couch.io/case-studies#bbc
The BBC has a public obligation to ensure that their main site www.bbc.co.uk is always on, 24/7, no matter what is going on in the world. Even if a catastrophe affects their datacenters they have contingency plans to make sure that their website stays up and is able to provide the latest news to readers wherever they are. ]]>修改 CouchDBX 的绑定地址tag:www.v2ex.com,2010-08-28:/t/21232010-08-28T18:33:29Z2010-08-29T18:33:29ZLividmember/Livid国内有项目在用 CouchDB 么?tag:www.v2ex.com,2010-08-28:/t/21222010-08-28T18:32:17Z2011-09-03T20:02:39ZLividmember/Livid 如果和 web 项目配合的话,什么框架/语言是最好的选择呢。 ]]>CouchDB: The Definitive Guidetag:www.v2ex.com,2010-08-28:/t/21212010-08-28T18:22:11Z2010-08-29T18:22:11ZLividmember/Lividhttp://guide.couchdb.org/