3 ms·
MongoDB solves the problem of developer time being expensive. It's simple to use and understands JSON data. Once you grow past it you know where the problems i
by raverbashing 13y ago
MongoDB solves the problem of developer time being expensive. It's simple to use and understands JSON data.
Once you grow past it you know where the problems in your data are and can optimize accordingly.
- tracker1 13y agoI have to completely agree... MongoDB does do okay in terms of small-mid scale needs, and is dead-simple to work with. It's a very natural fit with node.js, and does "good enough" for most. I do think that over the next 2-3 years as PostgreSQL adapts and expands the V8 extensions (and JSON data type) that it will probably take over MongoDB, and that we may well see a "mongo" adapter for a postgresql based backend. The place where I have MongoDB in the wild, it's a great/natural fit for what it's being used for... searching (including geolocation) on about 30k active records for a vehicle classifieds site. It should work on up to 10x the current load on the single server instance it's on, and can be re-deployed to a larger cloud/vm instance. The SQL db is the source of record, and data is replicated to the mongo instance. ElasticSearch was also considered, but didn't work as well when development was done (over a year and a half ago).
- collyw 13y ago> MongoDB solves the problem of developer time being expensive. I don't know about this argument. I am involved with a project to build a rare diseases database, and it might get moderately big (maybe ~1Tb). Somewhere on a related project a MySQL server crashed, so the guys building this new system have jumped right on the NoSQL bandwagon (despite the fact we clearly have relational data). 6 months ago, it was all Mongo DB. Last week it was Tokyo Cabinet. I am currently benchmarking Postgres (they seem not to have done that). I think I could achieve similar functionality in two weeks what these guys have taken 6 months to do using all the NoSQL solutions they have had tried (and needed to learn). When you have mature frameworks like Rails or Django that take a lot of the grunt work out of traditional RDMBS systems, I don't think it really is correct to say that Mongo DB saves developer time. In Certain areas, yes, but think there is a bigger picture to take into account.
- raverbashing 13y ago"When you have mature frameworks like Rails or Django that take a lot of the grunt work out of traditional RDMBS systems, I don't think it really is correct to say that Mongo DB saves developer time." Depends. Sometimes Django ORM is great. Sometimes, it is awful (yes, sometimes the models have crazy links between them, this is the most frequent cause of problems) Sure, if your data is relational, go for a RDBMS. But sometimes it isn't. And yes, if they're taking 6 months to do something in MongoDB there's something wrong with what/how they're trying to do it.
- collyw 13y agoThey are choosing NoSQL hype for relational data. That's what they are doing wrong.
- raverbashing 13y agoYou can have relations in MongoDB of course, however they are not as in an Relational DB. The problem is that they get the "MongoDB == no relations" literally and are trying to put a round peg in a square hole. I personally find it hilarious when someone is hitting their head in the desk with the "no relations" thing, as if it's a huge sin to have a id (or other information) of an item in another table.