One more war story about the bad design decision in MongoDB resulting in unresponsive nodes and data loss.
Hopefully, people will have figured out by now that MongoDB is not ready for production.
Hopefully, people will have figured out by now that MongoDB is not ready for production.
Hopefully people will stop trolling like this. And hopefully I'll stop reading and relying to them -- like it will make a difference.
Was mysql "ready for production" when google used it? facebook? Lol.
Storage engines are hard. I'm boggled that they recommend that you keep the old replica around for ten days. When we did the MMAPv1 migration to RocksDB at Parse, we kept at least one MMAP replica around for 6-9 months, as we worked through the integration of Mongo + rocksdb ... even though RocksDB the storage engine is powering fucking Facebook.
I get so fucking annoyed at the Hacker News armchair brigade that wants to talk shit about MongoDB, when they don't know a goddamn thing about databases -- or, from the looks of it, Facts About Stateful Services In General.
Eyeroll.
Actually, yes, yes it was. It had been used in production environments for quite a while by the time they came to use it. It was stable, reliable and had known performance characteristics and replication behaviour.