Why are people still using Mongo when you can just set up a jsonb column in Postgres now?
Is this just legacy applications that are stuck with Mongo? Certainly nobody is starting new projects on Mongo?
Serious question.
Is this just legacy applications that are stuck with Mongo? Certainly nobody is starting new projects on Mongo?
Serious question.
Having used both, I personally would never choose mongo over Postgres, there are just too many conveniences Postgres offers that are a pain with Mongo.
Serious question.
E.g. around the 300GB mark I had to constantly remind myself and others to be careful of it because it might have normal relational columns you think are fine to query, but it also has a fat json payload on each row and if you're careless the query planner would basically do a table scan for things you wouldn't expect.
This isn't so much a problem with json in an rdbms but more the false sense of query performance on non-json columns in the same table...after moving it to mongo never had the same problems because people knew not to query it in an unsupported manner.
I don't use mongodb in particular but I never want to go back to worrying about what a SQL application instance is up to, either.
because that is how they compare feature wise.
postgres is not easily comparable to mongo, these are totally different db engines with different tradeoffs made for different purposes.
They very obviously have a significant degree of feature parity.