MongoDB gets support for multi-document ACID transactions
We have been using mongo over the last three years on our project and it has been pretty smooth so far. However, lately I gave some thoughts into what our project would look like if we used PostgreSQL instead. I tried to figure out what problems Mongo solves that PostgreSQL doesn&#x27;t.<p>I am far from being a database expert, I just know enough  basics to query what I need, so feel free to correct&#x2F;complete the following:<p>- Mongo has been built to store json objects -&gt; Yes, but from what I understand benchmarks indicate that PostgreSQL is faster at reading&#x2F;storing&#x2F;indexing json&#x2F;jsonb content. I don&#x27;t think that it is good reason to use it.<p>- Mongo is schemaless -&gt; There might be some usecases, but I bet in most cases this problem can be worked around. Especially in a database with JSONB support.<p>- MongoDB horizontal scaling is way easier than PostgreSQL. Yes, it seems that scaling horizontally Mongo is extremely easy compared to any other relational database.<p>And ... that&#x27;s it. But there is probably more.<p>At the moment, here&#x27;s how I would summarize MongoDB benefits if asked my opinion when starting a project:<p>- For a small projects or a prototype: ease of use, ease of configuration, don&#x27;t require too much thinking into my data model while I am experimenting<p>- For a bigger project: horizontal scaling should be easier<p>Does that sound accurate to you? Am I missing anything important?