3 ms·

Here's my one-word guide: Don't.

• hydrogen18 13y ago
  I came to here say this as well.
  • ukd1 13y ago
    If you do, be aware of gotchas: https://blog.rainforestqa.com/2012-11-05-mongodb-gotchas-and-how-to-avoid-them/ https://blog.rainforestqa.com/2012-11-05-mongodb-gotchas-and...
  • tptacek 13y ago
    You came here to write a one-word comment about a database too, found it already written, so instead decided to write "me too"? Or did you instead have a detailed and carefully plotted comment about the problems with Mongodb, but then you read "nasalgoat's" comment and found his concision so bold and bracing that you were intimidated from contributing your comment? If so, I urge you to reconsider.
• albertzeyer 13y ago
  Can you elaborate on this? What's wrong with MongoDB?
  • fennecfoxen 13y ago
    This. http://hackingdistributed.com/2013/01/29/mongo-ft/ http://hackingdistributed.com/2013/01/29/mongo-ft/ Also this. http://nyeggen.com/blog/2013/10/18/the-genius-and-folly-of-mongodb/ http://nyeggen.com/blog/2013/10/18/the-genius-and-folly-of-m...
    • dkhenry 13y ago
      Because some people don't use it correctly doesn't mean it can't be done. Here is a different random article about ServerDensity using it successfully https://blog.serverdensity.com/tech-behind-time-series-graphs-2bn-docs-per-day-30tb-per-month/ https://blog.serverdensity.com/tech-behind-time-series-graph... This is nothing wrong with MongoDB.
      • cheald 13y ago
        I don't know that it's fair to say there's nothing wrong with it. We use it heavily, and generally enjoy it, but there are quite a few things wrong with it (write locks and ridiculous disk space usage come to mind up front). None of them are dealbreakers for us and can be worked around, but we also use it with the knowledge that it's a young product.
        • mcot2 13y ago
          You might want to test out tokumx. Document level locking and compression are two of the features it has.
          • cheald 13y ago
            Yup, I have been working with it. It's promising so far.
      • fennecfoxen 13y ago
        I'm sure people have been successful. But per link#2 above, "Being able to walk with them doesn’t change the fact that as of right now, MongoDB is clown shoes."
• deleted 13y ago
  [deleted]
• twic 13y ago
  I am reminded of Jackson's First and Second Rules of Program Optimisation: 1. Don’t do it 2. [for experts only] Don’t do it yet
• nlh 13y ago
  As a newbie to the node.js world, there seems to be a lot of talk about the MEAN stack (http://mean.io http://mean.io). What do you (or others) suggest as a good replacement for MongoDB in that stack?
  • nasalgoat 13y ago
    You shouldn't try to run all-in-one stacks and instead carefully consider each of your tools as appropriate for your application. Picking something because it's easy is bad.
    • nlh 13y ago
      Thank you. I spent a few days digging into the Node world and came to the same conclusion. I'm actually a bit surprised how long it took me to figure out that's actually the best practice -- I dug around a bunch of rails-like frameworks and was wondering why they didn't seem to be more widely adopted (Sails, Compound, etc) until it finally made sense that "The Node Way" is to add bits and pieces (usually on top of Express) to build a stack that's specific to needs.