News for hackers. Stuff that matters.
Re:Bye Bye Mongo, Hello Postgres (2018) by znpy on Sunday December 27, 2020 @10:00AM (#25551464)
> I wonder what this ultimately cost.

> That’s a lot of engineer time to develop, test, and do the data migration.

Downtime is more expensive.

EDIT: Also, the article says that they spent at least two months a year planning and executiting database upgrades, since the OpsManager tool from MongoDB Inc wasn't able to help.

Re:Bye Bye Mongo, Hello Postgres (2018) by sokoloff on Sunday December 27, 2020 @10:49AM (#25551779)
Two months a year planning and executing upgrades isn't that outrageous-sounding to me. We did that for years on a commercially supported RDBMS (MS-SQL Enterprise in our case). It wasn't the whole engineering organization, but the overall "scale existing capabilities" effort was a 3K-10K hour project every year depending on how extensive the work was.
Re:Bye Bye Mongo, Hello Postgres (2018) by znpy on Sunday December 27, 2020 @01:25PM (#25553070)
Well it kinda is if you bought a product that supposedly lets you do upgrades easily, from the vendor itself, and also have the support package from the vendor.