4 ms·
> why no run your own DB? Running your own DB introduces tons of risk that just isn't worth saving a couple bucks (until you're at the scale that it is). > Th
by a13n 8y ago
> why no run your own DB?
Running your own DB introduces tons of risk that just isn't worth saving a couple bucks (until you're at the scale that it is).
> That said, Mongo is a poor choice for any app ever written.
Sorry, that just isn't true. It works great for us, and is the 4th most popular database by usage (and growing). https://insights.stackoverflow.com/survey/2018#technology-databases https://insights.stackoverflow.com/survey/2018#technology-da...
- brianwawok 8y agoUsing mongo as a DB adds more risk then using self hosted Postgres or MySQL. You can use provider hosted Postgres or MySQL for less money and a better product. McDonalds is very popular, doesn’t mean it’s good food. Be wary the metrics of success you use.
- a13n 8y agoCan you quantify anything? How does mongo add more risk? How is mysql a better product. It doesn't seem like you're saying anything.
- Aeolun 8y agoJust because it works doesn’t mean it wasn’t a poor choice still. You could have said the same thing about storing your passwords in plain text.
- dman 8y agoHow can it be your largest expense but running your own db would save only a couple of bucks?
- a13n 8y agoWe don't spend much :)
- CleanShirt 8y agoBit of a disingenuous statistic. It’s popularity is down to being the default choice for people learning the MEAN/MERN stack. Which is a large number of people currently teaching themselves web dev and goes hand in hand with the rise in popularity of Javascript. It’s got little to do with wether people need a document store or wether it’s good at that job, 99% of the time it’s being used to dump relational data.