Hacker News Reader

Comment by Thaxll | Hacker News Reader

It's not a great article tbh, it's well written but it shows the clear lack of knowledge running a backend. The title should be "we didn't know what we were doing so we switched to a managed DB"

I mean yeah who knew that blocking NTP therefore time drifting would break everything...

For those criticizing MongoDB, Fortnite generates $3B/year and runs on MongoDB, you should tell them it's a mistake and that they should use PG instead.

View on HN

Epic have also had at least 2 major outages directly related to MongoDB

https://www.epicgames.com/fortnite/en-US/news/postmortem-of-...

It was not because of MongoDB itself if you've read the article.

I don't usually bite for these "X uses Y, so Y must be good", but I didn't know about Fortnite and MongoDB. A quick google suggest they've had downtime due to issues with Mongo and have had problems scaling it though.

Their level of scale is .. amazingly higher up there than most companies using mongo I imagine, and they seem to be doing a good job at it now.

I thought the article was well written but I have to agree about the MongoDB use case by Epic. Mongo has its place and it is mature enough that it can handle itself in a production setting.

That being said they had a massive outage due to a MongoDB issue.

Yeah except not every use case is the same. Treating every use case as the same shows, let's see what was it, 'clear lack of knowledge running a backend'.

Having a successful product doesn't mean that all technical decisions that were involved in making that product were successful. It raises the bayesian estimate that they were, of course - but not to an absolute boolean value.

I'm sure mongodb is fine and powers a lot of high-profile sites and services. But I've never had a good experience running it or administering it.

But I'm also one of the the people that still prefers to run MySQL over PostreSQL just because the tooling is still far superior

Can you give an example of superior tooling or tooling that isn’t good in PostgreSQL compared to MySQL. Serious question. I’m curious cos I mostly use PostgreSQL.

All the Percona tool are for MySQL and there is nothing comparable for PG afaik.

https://www.percona.com/doc/percona-monitoring-and-managemen...

https://www.percona.com/software/database-tools/percona-tool...

It looks like Percona has partial support for PostgreSQL. It's not as detailed as MySQL.

https://www.percona.com/software/database-tools/percona-moni...

Reply on news.ycombinator.com