These numbers seem representational to me from what I've seen/heard in the SF Bay Area.
MongoDB is typically introduced to optimize part of a stack, although more and more it is used as a sole/primary data store. I think ORMs and use of Mongo by prominent consulting shops helped boost adoption.
The particularities of CouchDB replication are very well suited to a enterprise application with a distributed architecture that I'm working on. I hope it sticks around for a long time, even if it doesn't have the biggest dev user base.
> The particularities of CouchDB replication are very well suited to a enterprise application with a distributed architecture that I'm working on.
That is what made it stand out for us. CouchDB carved itself a nice niche in that area and currently doesn't have any viable competitors. We have a cluster that runs continuous replications to sync data around and it works great. Had we used Erlang we would have used Mnesia (the dataset and pattern of access fits it well) but we use Python & C so CouchDB works great for us.
Also wondering what future will bring and if they'll ever end up with some hybrid of Membase+Couchbase? Reliable document saving and replication + fast key value store, rolled all in one?
MongoDB is typically introduced to optimize part of a stack, although more and more it is used as a sole/primary data store. I think ORMs and use of Mongo by prominent consulting shops helped boost adoption.
The particularities of CouchDB replication are very well suited to a enterprise application with a distributed architecture that I'm working on. I hope it sticks around for a long time, even if it doesn't have the biggest dev user base.