5 ms·
Postgres JSONB is strictly better performing on a single node than MongoDB. You can also create triggers and things to properly validate your data and do other
by angersock 9y ago
Postgres JSONB is strictly better performing on a single node than MongoDB. You can also create triggers and things to properly validate your data and do other cool stuff you can't with Mongo.
There is literally no reason to ever use Mongo for a small-medium project anymore.
If you need tooling, check out the new pgAdmin 4: https://www.pgadmin.org/ https://www.pgadmin.org/
- maerF0x0 9y agowhat about High Availability?
- tracker1 9y agoDepending on your needs, MongoDB (also look at RethinkDB) are more mature in terms of administration of clustered/replica nodes... PostgreSQL has more of this working its' way into the box, but imho not there yet... Also, write scaling will do much better with MongoDB sharding or RethinkDB clustering.
- memracom 9y agoPostgreSQL is not just a tool, it is now an ecosystem as well. There are numerous add-ons to provide various types of high availability. Some are plugins to PostgreSQL and some not. Also, some of these have commercial support if you need it. And PostgreSQL 10 which is out in September will have logical replication added, which is rather useful in engineering a high-availability database.
- angersock 9y agoJust use Amazon RDS and let them deal with it. None of the theoretical scaling benefits of Mongo outweigh the clusterfuck of maintenance, data inconsistency, and other general problems that shitty, shitty piece of software has.
- maerF0x0 9y agoname checks out. I didnt mind mongo in a couple of my previous jobs. We never noticed data issues and we did some crazy things like generating mongologs on one machine and moving them to another manually .
- weishan 9y agoMongoDB has HA built-in (replica sets). You will need to meddle with pacemaker/coroync or repmgr for HA in PostgreSQL.