Hacker News Reader

Comment by Thaxll | Hacker News Reader

That post fails to mention something critical, Postgres doesn't scale and is not HA out of the box so you're comparing a single server solution vs another one that as built-in cluster feature ... What do you do when you need HA? or your data is too big or you need a lot write/sec ect ...

The hate on MongoDB is strong on Hacker News / Reddit but I suspect most of you never had to design a solution when master/slave is not enough.

Also: https://www.mongodb.com/mongodb-3.4-passes-jepsen-test

View on HN

I'm curious whether the parent poster knows about the most recent HA features in Postgres, such as those introduced in v10, and if so, what is still missing for comparable HA. Here's a link to the HA docs for out-of-the-box postgres: https://www.postgresql.org/docs/10/static/high-availability....

As for scaling, it certainly scales out of the box with partitioning, but admittedly a partitioned table doesn't offer all the features that a non-partitioned sql table offers. A great assessment of the current state of postgres scaling can be found here: https://blog.timescale.com/scaling-partitioning-data-postgre...

While json fields in traditional SQL are useful in many ways (avoiding that infamous "extra" column) it really doesn't compare to mongodb. The aggregation framework in mongo for working with these documents is very powerful and if you run pg json fields to do anything other than retrieve extra fields (ie: if you try to query/aggregate it's fields meaningfully as you would a standard field) you'll find they fall over pretty fast with modest amounts of records.

The simple scalability of mongo (sharding/replication) is something that, while the recipient of much mocking initially, now at 3.6, gives enterprise level availability and scale with minimal oversight or expertise.

I'm really liking the features in 3.6 (over the wire compression, replication hardening, streaming query subscriptions to name a few) and every release packs a ton of features and improvements without breaking anything.

Postgre is a great relational database (one of my favorites) but its json field (which even mssql sports nowadays) is not a stand-in replacement for mongo in anyway way.

Just a suggestion that may be worth considering. Sometimes hate is confused with disagreement, and sometimes assuming people you’ve never met have less wisdom can cause hate before you’ve had a fair chance to make your point.

Reply on news.ycombinator.com