4 ms·
It's mongodb though... It's well documented at this point you shouldn't be using mongo on anything that matters
by exabrial 8y ago
It's mongodb though... It's well documented at this point you shouldn't be using mongo on anything that matters
- threeseed 8y agoAnd yet many of us are using it in Production. Including companies like Adobe, eBay, Expedia, Sony etc.
- pritambaral 8y agoThe fact that some are okay with and would use an unreliable tool is not inconsistent with the fact that it is documented that the tool is unreliable. Popularity among users has little to do with the tool being reliable, and this particular one is already popular for being unreliable.
- threeseed 8y agoWhat you are saying doesn't really make any sense. A systemically unreliable database would never be popular as its not a piece of your architecture that you can tolerate having constant outages with. And there is no evidence of MongoDB being systemically unreliable.
- macintux 8y agoThere are use cases where losing data is an acceptable tradeoff, particularly if the database is not the system of record.
- erik_seaberg 8y agoA reckless enough design (e.g., returning success when a request is merely buffered at the client) can lose writes without telling you that it lost writes, which won't affect its popularity among users who don't audit for that.
- pritambaral 8y ago> A systemically unreliable database would never be popular 1. Correctness and popularity are different 2. Not everyone looks for correctness, even when looking for a database. See: MySQL. > as its not a piece of your architecture that you can tolerate having constant outages with Reliability and correctness are not binary scales of 'works' vs. 'does not work'. Again, see MySQL. > there is no evidence of MongoDB being systemically unreliable There is plenty of evidence of MongoDB losing writes because of its (honestly) stupid design: writing to memory maps instead of files, never fsyncing, sharding and distributing without confirming disk flush. --- MySQL: For a long time, one needed to be aware of certain caveats and corners and limitations of MySQL or be surprised with data inconsistency and loss. That is not to say that MySQL could not be operated reliably; it could, just that the barrier was higher than it appeared. From truncating data (with a warning) to not accepting and silently (i.e., without warnings) ignoring CHECK constraints, I've had clients who lost business data and realized it only too late to go back to the original data source. I used to think MySQL was an bad database due to its concessions of correctness and poor documentation, until MongoDB came along with their lofty marketing and high-and-mighty "Nobody needs SQL anymore, we are Web-scale" blare-horn and failed to deliver on even keeping the data it claimed to have saved.
- Thaxll 8y agoLet me guess you're a Postgress troll?
- x3n0ph3n3 8y agoI think you just made his point with that list of companies.
- cheeze 8y agoAnd it might be fine at those companies. But I don't exactly expect the highest quality and reliability from Adobe, eBay, etc.
- arbie 8y agoWhat should one be using in its stead?
- dijit 8y agoThis is a fair question, I would advise not listening to anybody who says they have a "one size solution" for all data. For searchable structured data, I'd probably go with elasticsearch. It scales very well and you can turn off indexing and use it as a document store. I am a huge fan of postgresql and the more I use it the more awesome I find it, so I'd probably use postgresql's JSONB column type for unstructured data if that's a requirement. You can pair it with citus and make it scale quite well. For pure document storing there's RethinkDB which performs well and does not lose your data as MongoDB does.
- knocte 8y ago^ This. Best comment.
- skywhopper 8y agoThis is a funny joke, but a really dumb thing to say seriously. It all depends on your use case and knowing the tool. Mongo is far and away the best choice of DB for an internal app I’ve been building, but managing it is a pain and I’ve been unhappy about the direction the company has been headed. So I’m thrilled that AWS is going to take the burden away from me entirely with this new service, which I would have happily paid MongoDB for instead on the same usage-rated terms. Oh well.