4 ms·

Engineers need to be disciplined. You know there's a problem with the culture when things like MongoDB become popular, despite very highly public failures, and

by nirvana 14y ago

Engineers need to be disciplined. You know there's a problem with the culture when things like MongoDB become popular, despite very highly public failures, and fundamentally bad engineering choices. It shows the power of marketing and ideology (people like mongoDB because it's fast on a single node and they can use SQL rather than having to learn something new, so they become "believers" in it without regard for its lack of scalability, or reliability, etc.)

luigi 14y ago
> people like mongoDB because it's fast on a single node and they can use SQL rather than having to learn something new You can use SQL on MongoDB? And thanks for telling people who like MongoDB why exactly they like it.
dschiptsov 14y ago
It is exactly how to sell - give what users want - documentation full of adjectives but omitting important details, success stories, examples. Javascript! NoSQL! Fast! Always OK. (and never loses data) Grab, don't think.) To be little more serious, this is an example of what happens when professional sales strategies from proprietary shops come to open source. Now we have open source crapware. Actually, the best heuristic to evaluate open source project - why it was created - for sale, or for internal use. Ryak or redis, for example, were made for use, not for sale.
cullenking 14y ago
Wow, axe to grind or what? You have three comments on here all belittling something that many people find perfectly acceptable and successful in production. Of all the non-SQL choices, Mongo isn't a terrible one. We've got (along with many other companies) 300gb in Mongo and it's been loads more enjoyable to use in a replica set than MySQL has been in a master/slave architecture, and every bit as reliable. More so if you count the simple live failover that just works. It's a data model that works very very well for some datasets. We use MySQL for stuff that is obviously relational, but we store a bunch of geo data as JSON for fast serving to javascript etc. It's a perfect fit. But seriously, if you don't have a backup of any of your data stores, that's a big problem.
deleted 14y ago
[deleted]

by nirvana 14y ago

luigi 14y ago

> people like mongoDB because it's fast on a single node and they can use SQL rather than having to learn something new You can use SQL on MongoDB? And thanks for telling people who like MongoDB why exactly they like it.

dschiptsov 14y ago

It is exactly how to sell - give what users want - documentation full of adjectives but omitting important details, success stories, examples. Javascript! NoSQL! Fast! Always OK. (and never loses data) Grab, don't think.) To be little more serious, this is an example of what happens when professional sales strategies from proprietary shops come to open source. Now we have open source crapware. Actually, the best heuristic to evaluate open source project - why it was created - for sale, or for internal use. Ryak or redis, for example, were made for use, not for sale.

cullenking 14y ago

Wow, axe to grind or what? You have three comments on here all belittling something that many people find perfectly acceptable and successful in production. Of all the non-SQL choices, Mongo isn't a terrible one. We've got (along with many other companies) 300gb in Mongo and it's been loads more enjoyable to use in a replica set than MySQL has been in a master/slave architecture, and every bit as reliable. More so if you count the simple live failover that just works. It's a data model that works very very well for some datasets. We use MySQL for stuff that is obviously relational, but we store a bunch of geo data as JSON for fast serving to javascript etc. It's a perfect fit. But seriously, if you don't have a backup of any of your data stores, that's a big problem.

deleted 14y ago

[deleted]