How We Moved from MongoDB to Postgres Without Downtime and Cut Our Costs by 30%?

https://www.voucherify.io/blog/how-we-moved-from-mongodb-to-postgres-without-downtime-and-cut-our-costs-by-30

by noren64 • 5 years ago

43 5 5 years ago

diveanon2• 5 years ago

I'm not trying to bike shed, but I am genuinely curious about what use cases people who choose mdb over pg are optimizing for.

With hstore and jsonb fields I don't really see any reason to support mdb. Is it scaling / replication that makes it worthwhile?

beckler• 5 years ago

I have to use mongo at work. They used it because they thought it would be easier for the developers, but I find the query pipelines confusing at best. It can be extremely nuanced depending on how complex your aggregations are. I usually have to rewrite complex queries often because there are so many subtle details that can make your queries return incorrect data.

Even the docs in mongo tell you what kind of SQL query certain operators perform… I would rather just do SQL.

diveanon2• 5 years ago

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.

cryptos• 5 years ago

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.

How We Moved from MongoDB to Postgres Without Downtime and Cut Our Costs by 30%?

Related Stories