4 ms·
They used it in a startup where I used to work. Their data was fully relational, and they were doing the one thing that really really kills performance in mong
by LtWorf 2y ago
They used it in a startup where I used to work.
Their data was fully relational, and they were doing the one thing that really really kills performance in mongodb: growing documents.
Also it had no constraints so the data was all fucked up by the various bugs that were in the code over the years.
Ah yes they used sharding. Probably there wouldn't have been a need for it if they had just used postgres, since the data was not that much.
- winrid 2y agoPG and Mongo will vertically scale about the same depending on your queries. They were probably using sharding with tiny instances which is dumb. Also, large documents doesn't really hurt performance with mongo, except maybe with writes, or with large array fields due to replication implication.
- LtWorf 2y agoNot large documents, but documents where the most common operation is to add a number to a list of numbers.