News for hackers. Stuff that matters.
Re:CouchDB vs. MongoDB by candeira on Thursday June 15, 2017 @06:17PM (#14564927)
The article is strangely outdated on the CouchDB side, like someone wrote it two years ago.

It fails to mention that CouchDB now has Mango, which is a MongoDB-compatible query language.

Since 2.0, CouchDB also has Dynamo-like clustering thanks to Cloudant's open sourcing of the BigCouch code.

I wonder if the MongoDB side of the comparison is more up-to-date, or equally stale.

Re:CouchDB vs. MongoDB by nevi-me on Friday June 16, 2017 @12:44AM (#14566730)
Mango seems interesting, thanks for that. I got thrown into a tight spot at work, where I'm building a lease calculator for the accountants, I need to build the whole thing as a self-contained application, due on Monday. Long story is that it wasn't as easy as I thought, and I ended up having to replicate Journal entries, a trial balance and financial statements. Even though Mongo doesn't have transactions, I found a good way to make my journals balance. I'm using aggregating framework to post journals to TB and FS.

The last part I was worried about is the self-contained bit, so I'm going to give CouchDB a try, and use Mango to prevent redoing everything

Re:CouchDB vs. MongoDB by 6nf on Friday June 16, 2017 @08:57AM (#14568442)
You don't need a different NoSQL database, you need a relational database.
Re:CouchDB vs. MongoDB by lcarlson on Friday June 16, 2017 @07:02AM (#14567929)
I would assume a SQL database would be at least a tad easier to do accounting like tasks?