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-da...
McDonalds is very popular, doesn’t mean it’s good food. Be wary the metrics of success you use.
You could have said the same thing about storing your passwords in plain text.
2. MongoDB is a great database if you have a data model that suits it. Problem is a lot of people have treated like it was relational. And operationally it's far simpler than most systems out there.
Both AWS and GCE offer hosted Postgres for less than third party hosted mongo.
What model is good for mango? Postgres has jsonb. Cassandra has large scale data. Mongo is in a weird spot in the middle that isn’t great at anything.
Not sure why you brought up Cassandra it is not a document store and completely irrelevant to this discussion.
There's a tendency in web development towards using well known stacks, and some of them are quite poor choices for most projects. MongoDB features heavily in these stacks despite relational databases being a better fit most of the time, possibly because there's less visibility of alternatives in the JS community.