3 ms·

eknkc has a point. Let me explain our needs and why we chose MongoDB over PostgreSQL (and I have been a huge fan of PGQL since before the MySQL/PGSQL flame war

eknkc has a point. Let me explain our needs and why we chose MongoDB over PostgreSQL (and I have been a huge fan of PGQL since before the MySQL/PGSQL flame wars). Replication is not very easy to setup in PGSQL. Sure, I can do it, but our product is an on-prem product that our users are responsible for configuring and maintaining. Having them configure PGSQL replication would be something they're not willing to do. MongoDB's configuration of replica sets is quite trivial compared to PGSQLs. I bring this up every time someone says "PGSQL > MongoDB", even on PGSQL threads where PGSQL devs participate and they admit it's not quite there yet, but that they're working on it. And all that said, it is getting demonstrably better to configure replication in PGSQL, so it's going to get there some day and I can't wait.

crdoconnor 12y ago
>I bring this up every time someone says "PGSQL > MongoDB", even on PGSQL threads where PGSQL devs participate and they admit it's not quite there yet Do you have a link to such a thread where pgsql devs admit its inferiority?
- craigching 12y ago
  Here's a link to my thread. I don't know that I'd say "inferior" just "harder to configure." Please bear that in mind, that's all I'm saying here. https://news.ycombinator.com/item?id=6693027 https://news.ycombinator.com/item?id=6693027
eddd 12y ago
If your users have problems with configuring replication for something give them a tool to do it, i advise some template engine i simple python script. Once you write data to mongo, it is not your data - don't forget it.