Is MongoDB good for transactional data?

Question

For situations that require atomicity of reads and writes to multiple documents (in a single or multiple collections), MongoDB supports multi-document transactions. With distributed transactions, transactions can be used across multiple operations, collections, databases, documents, and shards.

Why MongoDB is not good for transaction?

MongoDB, unfortunately, does not support transactions. So if you need to update more than one document or collection per user request, don't use MongoDB. It may lead to corrupted data, as there is no ACID guarantee. Rollbacks have to be handled by your application.

What type of data is MongoDB good for?

MongoDB is built on a scale-out architecture that has become popular with developers of all kinds for developing scalable applications with evolving data schemas. As a document database, MongoDB makes it easy for developers to store structured or unstructured data. It uses a JSON-like format to store documents.

Which database is best for transaction?

A SQL database is a great fit for transaction-oriented systems such as customer relationship management tools, accounting software, and e-commerce platforms.

Is NoSQL good for transactions?

Therefore, NoSQL databases would be useful for managing data in such applications. However, the lack of support for transactions, table joins and referential integrity in NoSQL databases, mean that they are not suitable for applications such as banking, online gaming, etc.

Expert · Answer