4 ms·
Obligatory reminder that Mongo is shit and you should never use it for data you care about.
by djrobstep 9y ago
Obligatory reminder that Mongo is shit and you should never use it for data you care about.
- redwood 9y agoLet's try to keep the discussion out of the gutter, please.
- meowface 9y agoReliability-wise, it sucks. Maybe it's gotten better recently, but I still probably wouldn't trust it. But is there a document store out there that's faster than MongoDB?
- Operyl 9y agoI was a big fan of a RethinkDB, but growth has stagnated since the parent company shut down. It’s technically a Linux Foundation project now.
- judah 9y agoI'm biased (I work part-time for the company), but RavenDB[0] 4.0 is damn fast, cross platform, and has beautiful tooling. It's built on .NET Core, and our current performance is 140k writes/sec. We also bend over backwards to optimize read speeds: we generated indexes automatically based on your query patterns, discarding unused indexes and throwing server resources behind the hot ones. Also, unlike many other NoSQL databases, we support transactions and atomic writes. [0]: https://ravendb.net https://ravendb.net
- tehlike 9y agoShameless promotion: the guy running the company is pretty solid, too.
- strayamaaate 9y agoWe use ArangoDB currently and are pretty happy with it. Installs and upgrades could be better though. Very curious about RavenDB as I’m writing a lot of .NET Core these days. How would you say it stacks up against ArangoDB? Edit: Ok, just saw the pricing. Ouch.
- judah 9y agoActually, the pricing for the new version (4.0, .NET Core): - Free, with a max of 3 cores and 3 distributed nodes The paid version will be an Enterprise license without these limits.
- tytytytytytytyt 9y agoWhat about Redis?
- pille 9y agoThere are quite a few better options for trustworthy databases. One is my employer, MarkLogic, which is an ACID compliant NoSQL document db with a lot more indexing capabilities. Especially if you’re using the search tools to retrieve data, I think a properly indexed MarkLogic would be quite a bit faster, and still more reliable.
- jinqueeny 9y agoThere are also quite some NewSQL solutions out there. TiDB, CockroachDB, Spanner, just to name a few. Besides, the first two are open source... https://github.com/pingcap/tidb https://github.com/pingcap/tidb https://github.com/cockroachdb/cockroach https://github.com/cockroachdb/cockroach They provide the features of both RDBMS, such as ACID transactions, SQL, and the scalability of NoSQL.
- oulu2006 9y agoHave you tried postgresql with JSONB support? I used to use Mongo a while ago and found it a very painful experience (this was a few years ago). With postgresql I can use SQL and get the benefits of document storage, and so-far I've found it efficient and rock-solid.
- eridius 9y agoIf you don't care about reliability, you can't beat the speed of /dev/null.
- reustle 9y ago* If you don't know how to set it up properly
- Operyl 9y agoSo, call me nuts, but then shouldn’t there be sane defaults? I’ve not set up or tinkered with MongoDB in a looooong time, but that seems like a must for any project. EDIT: instead of downvoting me explain to me what I said wrong, I’m seriously wondering why it needs to be configured for sane defaults ..
- reustle 9y agoI'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
- ydg88 9y agoyour comment is shit. shame on you.
- rawrmaan 9y agoI wonder how it feels to be running or working for a company that develops a product that almost all informed members of the developer community think is bad. They must be in some serious denial.
- threeseed 9y agoActually more informed members of the community don't think it is entirely bad. It's just a sad circlejerk that exists on HN amongst people who have clearly never even used the database before. The people who are informed don't think it is suitable for every use case but understand that it does serves a purpose. There's a lesson in life. If you think everyone else is an idiot then chances are you're the idiot.
- vacri 9y agoYou say 'informed members', but most of the mongo hate seems to stem from bad reputation from the early days. Most of the hate seems to come from historical bandwagoning, rather than informed DBAs commenting on current versions. For a long time here on HN, mongo was terrible, never to be trusted, and everyone should move to RethinkDB. But the RethinkDB boat has now foundered, and might be resuscitated by the LF, or it might sink again. If you'd followed the zeitgeist, you'd be in a worrisome spot right now.
- dang 9y agoPlease don't post unsubstantive comments here, especially not ragey ones. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html