5 ms·
at v2.6 the product was only about 4 years old and underwent a lot of change during that time. (For comparison Postgres version 3 was released in 1991) I think
by hitgeek 10y ago
at v2.6 the product was only about 4 years old and underwent a lot of change during that time. (For comparison Postgres version 3 was released in 1991)
I think the main guilty parties at mongodb were/are in marketing.
technically sophisticated users understood the immaturity of the product and the tradeoffs that came with its architecture.
however it was sometimes marketed as a general purpose data store, or as an alternative to much more mature relational data stores, which was and still is an unfair comparison.
- nailer 10y agoEven technically sophisticated users should be able to expect secure defaults.
- omni 10y agoSemantic counterargument: If you put a database into production without understanding its network and auth configuration then you are by definition not "technically sophisticated"
- nailer 10y agoBy this standard, every programmer who puts an app into production without understanding assembly is not technically sophisticated. We could expect every programmer to have domain knowledge of databases, even when it's not normally needed to operate one. Or we could just make databases not acknowledge writes that haven't happened, not listen on all ports, not hide information about data loss in non-clustered setups deep inside the documentation. Counterargument: many people who are good at a particular topic enjoy feeling superior to people who don't have their knowledge.
- hitgeek 10y agoat the time these versions of mongodb were released, it was only a few years old, and DID require considerable domain knowledge to run in production. This does not seem unreasonable for new immature technologies. unfortunately, I don't think this was always communicated effectively by the explosion of mongodb marketing and hype.
- nailer 10y ago> DID require considerable domain knowledge to run in production. What do you mean? If you you mean it took knowledge to run per se: it didn't: unzip and run the service, it's up. It wasn't any more complex than any other piece of software. Or do you mean it did require considerable knowledge to avoid data loss on software marked as 'stable'? Yes, that's the problem, and yes, that's unreasonable.
- salvor 10y agoThis. So much this.
- user5994461 10y agoSophisticated users understand when to adopt a product. MongoDB had all the red flags, a sophisticated user would have done a trial and ban it with a company-wide memo after the first week and already the 3rd disaster.
- at_tt 10y agoSophisticated users without setting up authentication and backup for their valuable data?
- raverbashing 10y agoYes, you could expect. But you would check.