The Great Migration from MongoDB to PostgreSQL

Post by jononor » Sun, Mar 31, 2024, 12:21 AM UTC

KingOfCoders wrote: post #49

Ozzie_osman wrote: post #37

Earlier quoted context omitted.

Read replicas are pretty easy on postgres using replication. That said, you need to be careful about replica lag. If you want to distribute your writes, that's a little trickier. There are options like Citus and such. But still not natively supported.

Second that. A client hat PG replica lag, was doing backups from the replica and found out during restoring a backup, that some hours of data were missing.

Post by hahn-kev » Sun, Mar 31, 2024, 2:34 AM UTC

riku_iki wrote: post #288

BiteCode_dev wrote: post #280

Earlier quoted context omitted.

Because vertical scaling can take you so far these days that 99% of companies will never, ever reach the scale where they need more. There is just few incentives. Especially since: - Servers will keep getting better and cheaper with time. - Data is not only in postgres, you probably have redis, clickhouse and others, so the charge is balanced. In fact you may have different dedicated postgres, like one for GIS tasks.…

> vertical scaling can take you so far these days that 99% of companies will never, ever reach the scale where they need more its less about the scale and more about HA and service interruption: your service will be down if server dies.

Post by Semionilo » Sun, Mar 31, 2024, 8:27 AM UTC

b9b10eb736 wrote: post #322

Semionilo wrote: post #242

General speaking: don't use mongodb. It was super shitty when it came out and using postgres gives you a better and faster solution which you can also use in other projects. I'm always impressed when I see mongodb still making money.

While I'd agree with the general stance of avoiding MongoDB for any new project, I find the statement that postgres always gives better and faster solution dubious. They don't really solve the same problems. If you happen to really need horizontal scaling, actual HA (not failovers) or documents with many field-level atomic operations, MongoDB might still be a better fit than postgres. For on-premise hosting, not havi…

Post by 5Qn8mNbc2FNCiVV » Sun, Mar 31, 2024, 6:00 PM UTC

jononor wrote: post #321

KingOfCoders wrote: post #49

Earlier quoted context omitted.

Second that. A client hat PG replica lag, was doing backups from the replica and found out during restoring a backup, that some hours of data were missing.

Ouch? Are there standard tools to monitor that? Any best practice to avoid? I am considering exactly tha kind of setup...

Post by mushi » Mon, Apr 01, 2024, 1:04 PM UTC

smt88 wrote: post #297

dangtony98 wrote: post #101

Earlier quoted context omitted.

I'm actually very bullish on MongoDB. While the article and significant sentiment in threads suggest a push off MongoDB toward PostgreSQL, I do think MongoDB has its own place in the stack and that it won't be obsoleted. I've personally had many pleasant experiences working with it in past projects. Regarding business metrics, I may have a slight bias coming from the startup world but we often value revenue the most,…

HN should be full of Mongo's users and advocates, and yet this site loathes it. That by itself is a sign that it's a zombie. The reason we don't just look at revenue is that you can "buy" revenue with ads and sales teams. But if that revenue growth costs more than it pays because your customers aren't sticky, then your business doesn't work. You can't apply startup principles to this large, aging public company.