News for hackers. Stuff that matters.
Re:Bye Bye Mongo, Hello Postgres (2018) by golergka on Sunday December 27, 2020 @10:22AM (#25551606)
When you never need to work with two different documents at once, but need cheap scale. I once worked on a mobile game which saved player progress by uploading JSON to the server — the server never even parsed it, just saved directly to Mongo. And later retrieved it back when the player logged in.

That was the only time when I experienced a Mongo-based system which didn't suffer from any Mongo-induced problems.

Re:Bye Bye Mongo, Hello Postgres (2018) by ssijak on Sunday December 27, 2020 @11:05AM (#25551905)
Why even use a server and mongodb behind it for that when you can straight up save the document to Firestore from the game. No servers, no mongodb maintenence.
Re:Bye Bye Mongo, Hello Postgres (2018) by wgjordan on Sunday December 27, 2020 @11:46AM (#25552221)
One is document-oriented database software while the other is a fully-managed document-oriented database-as-a-service, so not at all a useful comparison.

MongoDB offers a fully-managed database-as-a-service as well (Atlas), for what it's worth.

Re:Bye Bye Mongo, Hello Postgres (2018) by tpetry on Sunday December 27, 2020 @01:42PM (#25553216)
I swa a talk once from one of the facebook game companies who simply stored the player state in a file. There is nothing more simple! They simply loaded the files content into the memory as long as the player was playing and then serialized to file