> Oh, Thank you Maibeck for your feekback!
> Have they confirmed those issues or they are for your case of
> configuration!?

> On Wednesday, August 15, 2012 6:32:55 PM UTC+4:30, maibeck wrote:

>> I cannot recommend going to production using the current release (0.4.0).
>>  There are still some major bugs that need to be addressed in order to
>> create a stable environment ready for production.  

>> The biggest issue for us was that views would often need to be rebuilt
>> from scratch.  View generation can take hours/days to complete with large
>> data sets, which in a couple cases took down our applications for days at a
>> time.  We weren't ever able to consistently repeat the behavior, but it
>> seemed to occur under high load, or after the server/service was restarted.

>> Cloudant's hosted platform appears to be quite stable, and has some
>> additional features not found in bigcouch, namely chained map-reduce.
>>  I would recommend using Cloudant if you're considering taking the bigcouch
>> path.

>> On Tuesday, August 14, 2012 8:18:37 AM UTC-6, Behrad Zari wrote:

>>> Howdy Big! Couchers,

>>> We are estimating to deal with large-scale couchdb views (about more
>>> than hundred Gigs of couchdb indexes) in production.
>>> (Which I don't think is a feasible size on a single couchdb on one
>>> machine, because of limited machine memory !?)
>>> To provide index partitioning, we are thinking of BigCouch, which is
>>> lovely fork of Couchdb, but I'm not sure about the future!?
>>> I've read links but have not found any roadmap or planned merge! Since
>>> we are planing for a critical system in production, I wonder
>>> if using BigCouch will be risky or not?

>>> Thank you in advance,