3 ms·
Mongo 3.0 contains an engine that was acquired and is very decent, much like InnoDB in MySQL.
by mayank 11y ago
Mongo 3.0 contains an engine that was acquired and is very decent, much like InnoDB in MySQL.
- prodigal_erik 11y agoHaving read https://gist.github.com/mapopa/3619146 https://gist.github.com/mapopa/3619146, I'm not eager to trust the judgment of a team who was ever willing to handle users' data so recklessly. Same reason I avoid MySQL when I can.
- hendzen 11y agoThe authors of the new storage layer mentioned in the GP are the team that originally wrote BerkeleyDB, which has been used for misson critical workloads for decades. One of the authors actually invented Serializable Snapshot Isolation (SSI), the concurrency control mechanism used in Postgres. If you don't trust them to handle your data, I don't really know who you should trust.
- prodigal_erik 11y agoFor quite a long time, mongodb defaulted to buffering writes (presumably to win benchmarks) and dropping errors on the floor. Storage is not the only layer at which their dangerously poor judgment could screw me and my users.