4 ms·
I'm not the one who downvoted, but back when I ran a large critical Mongo setup, essentially the core flag to set when running was 'safe=true' on mongoD. That w
by reustle 9y ago
I'm not the one who downvoted, but back when I ran a large critical Mongo setup, essentially the core flag to set when running was 'safe=true' on mongoD. That was it. We had 30~ instances set up with sharding and replication, doing many thousands of operations per second at peak during the day. It was a great tool then, and I'm sure it's even better now. It was just fun to hate on it so people with 0 experience using it joined in.
- djrobstep 9y agoBack when I ran a larget critical mongo setup, developers had all sorts of problems due to bad poor transactional support. Why wouldn't you just use postgres with jsonb data type?
- vacri 9y agoIs a feature that's only been around for a couple of years really a suitable answer for a "back when" anecdote?
- mrgordon 9y agoSafe = false was set that way to game benchmarks and it caused people to lose mission critical data if they didn’t realize and reconfigure. It’s just sad to make such nonoptimal decisions to inflate benchmarks and get PR