How We Moved from MongoDB to Postgres Without Downtime and Cut Our Costs by 30%? (opens in new tab)

I have used mongo heavily in the past and had similar problems.

More often than not I hear the rationalization the no-sql is easier to develop because you don't need schemas. In my opinion that is a horrible anit-pattern.

What I am curious about is the use-cases where mongo actually is the correct choice of pg.

The argument that a schemaless DB would be easier for developers is pretty much the same argument that a programming language with dynamic tpying would be easier than a language with static typing. That might be true in the short term, but just like static typing a schema helps in the long run. Types and schemas make explicit what would otherwise be implicit knowledge and help to catch bugs early.