This commit is contained in:
Yann Esposito 2015-11-07 19:39:57 +01:00
parent 2a9d8741a8
commit 2d379d777f

View file

@ -104,7 +104,7 @@ Each time you read or write, nobody could read or write at the same time.
And even using very expensive clusters, they couldn't handle these hard limits.
As a result, when we asked Mongo to reas and write a lot at the same time, we started to witness data loss...
As a result, when we asked Mongo to read and write a lot at the same time, we started to witness data loss...
If you can't write them, let's destroy them.
Furthermore the code dealing with tweet insertion in MongoDB was really hard to manipulate. No correct error handling. In the end, data loss...