4 ms·
Absolutely. If your data model is document orientated then it is an excellent choice. And EVERY database has limitations. You just need to be pragmatic and det
by threeseed 12y ago
Absolutely. If your data model is document orientated then it is an excellent choice.
And EVERY database has limitations. You just need to be pragmatic and determine if you will ever really hit them.
- chris_wot 12y agoWhich is a completely niche market. And even those people find they hit snags - like when they discover that their data model isn't actually document oriented, like they thought. Given this, why don't they just use Postgres?
- threeseed 12y agoAre you replying to the right person ? I have no idea what your point is. If I am building an application with a document model (which actually isn't that niche for SPA sites) then MongoDB is a great choice. It is much easier to use and manage than PostgreSQL which is important if you are trying to get something off the ground. This is why I would use it. But that doesn't mean it's the right choice for everyone nor is PostgreSQL, Oracle, MySQL or any other database.
- chris_wot 12y agoMy point is that it's so limited that for most people (and that includes single-page apps) you're better off using a relational database. I've been watching hierarchical data models for some time now - I honestly can think of only a few, limited applications for something like MongoDB. I'm not the only one who thinks so - see http://www.sarahmei.com/blog/2013/11/11/why-you-should-never-use-mongodb/ http://www.sarahmei.com/blog/2013/11/11/why-you-should-never... Edit: Look, I know I'm being negative on MongoDB. But I really wanted it to be awesome, but it's inherent limitations are just so start that I feel that most people who use it are doing so because they are misinformed or misled. If you have found success with it, that's great. I just have very strong reservations about the entire data model for most people. As someone has posted above: if you have data that is relational, then it's relational - you should use a RDBMS.
- threeseed 12y agoThe relational data model is not perfect for every use case. I use Cassandra for high volume, time series data, MongoDB for documents, Titan/Neo4J for graph data, ElasticSearch when I need better indexing. I pick a different technology depending on what I think works best for the use case. At no point have I thought so condescendingly as you do that MY choices are the best for everyone. They aren't. And I promise you that picking the one technology/approach for everything doesn't work anymore. It's a heterogeneous world out there. And that link you posted is pathetic. MongoDB is not suited for social network style data neither is many other databases. Doesn't mean they are useless for every use case.
- aikah 12y agoare you really juggling with 3 dbs in the same project?
- chris_wot 12y agoLook, I know I'm being negative on MongoDB. But I really wanted it to be awesome, but it's inherent limitations are just so start that I feel that most people who use it are doing so because they are misinformed or misled. If you have found success with it, that's great. I just have very strong reservations about the entire data model for most people. Ease up there buddy! I wasn't being condescending. I just think that for most people a relational model is probably what they are looking for. I don't think the article I posted is "pathetic", as that's a bit condescending... Just showing one datapoint that shows where people think they need a hierarchical data model, in fact they need an relational model.