Comment by Juha Lindstedt on "MongoDB Vs Postgres"

I've used MongoDB in all my projects since 2011 and it's been great! I never learned SQL because I found it confusing and error-prone (a lot of escaping etc needed to be done at least with PHP+MySQL). MongoDB + node.js works together like magic and I like the fact that I can do queries with JavaScript and not some weird string-based query hocus pocus language.

I haven't yet found a single thing couldn't be done with MongoDB. Complex tree structures work great, relations between collections no problem, etc.

I can't compare to PostgreSQL since I haven't used that, but what I can say is that MongoDB work great even in large projects. With every version it has gained new features and better performance. It's different alright, but for me that's a good thing.

Juha Lindstedt, I have got one for you. Have you found a way to do transactions with MongoDB?

What do you mean by transaction?

Juha Lindstedt Transaction is a single unit of updates - Either all or none. In order for a transaction to succeed all the updates in that transaction should execute successfully. If an error occurs, the updates are rolled back. MongoDB is not designed to handle transactions. So, e-commerce, banking sites etc that are dependant on transactions, use an SQL database.

ok, not sure about those – never needed them, but there's some ways to do those kind of things, maybe: docs.mongodb.com/manual/core/write-operations-ato… docs.mongodb.com/manual/tutorial/perform-two-phas… :)

..and if not out-of-the-box, I bet there's ways to do it anyway

Search Hashnode