https://dev.to/franckpachot/mongodb-transaction-performance-4dc7
🌱 TL;DR: it's the same. Choose the consistency boundaries based on your application, not myths or guesses.
| https://twitter.com/FranckPachot | |
| ✍🏼Blog | https://dev.to/franckpachot |
| https://www.linkedin.com/in/franckpachot/ | |
| 📺Youtube | https://www.youtube.com/@franckpachot/community |
Top‑K BM25 range + text search on 100 million MongoDB documents in under two seconds (I reused the excellent ParadeDB example for this test)
https://dev.to/franckpachot/top-k-queries-with-mongodb-search-indexes-bm25-3a41
No rewind needed! MongoDB smoothly handles secondary nodes rejoining the replica set thanks to its recover-to-timestamp rollback in its Raft-inspired algorithm. Observe this in action with w:1 writes, where the rolled-back data isn’t lost but saved in a rollback directory: