Disadvantages
of MongoDB
* If something crashes while it’s updating
‘table-contents’ – you loose all you data.
Repair takes a lot of time, but usually ends up in 50-90% data loss if you aren’t lucky. So only way to be fully secure is to have 2 replicas in different data centers.
Repair takes a lot of time, but usually ends up in 50-90% data loss if you aren’t lucky. So only way to be fully secure is to have 2 replicas in different data centers.
* Indexes take up a lot of RAM. They are B-tree indexes
and if you have many, you can run out of system resources really fast.
* Data size in MongoDB is typically higher due to e.g.
each document has field names stored it
* Less flexibility with more complex querying (e.g. no
joins)
* No support for transactions – certain atomic
operations are supported, at a single document level
* At the moment Map/Reduce (e.g. to do
aggregations/data analysis) is OK, but not blisteringly fast. So if that’s
required, something like Hadoop may need to be added into the mix
No comments:
Post a Comment