I find it unfortunate that CouchDB is pretty much a dead project even though it's fundamentals are for most projects better than MongoDB. Master-master databases are the future for most scaled architectures.
Do.... I'm trying to phrase this the right way. These are serious questions.<p>Do people actually consider using MongoDB for new projects? Do they want to add it to existing infrastructure? Why, with only a cursory search on the limitations?!
So if Mongo is such shit and Couch is a pain in the ass to configure with not so great documentation, what <i>can</i> I use as a NoSQL database? From time to time, I find myself wanting a database that is flexible with document definition but every tool I've tried has kind of sucked.
What is the go to use case for a document database?<p>Things like ElasticSearch (search database), Neo4j (graph database), and Redis (key/value store) seemed to be used along-side a traditional RDBMS, and have specific use cases that make them superior than trying to shoe-horn the functionality into a traditional RDBMS.
With the new CRO appointment, what changes to their business model are now expected in order for them to try to realise these investments? I guess they cannot do much about s/w licensing remaining at zero cost, so will they be targeting just support revenues?
So I guess we can look forward to a lot more marketing selling MongoDB as some incredible database? It would be nice if they spent that money making it less of a pain to use and less brittle.
I dont know so much about internal architecture of database's, but I really loved how mongodb care about people with providing such great course on udacity.