Mongofail
-
@blakeyrat said in Mongofail:
@AyGeePlus said in Mongofail:
take time to propagate to everyone,
That's what eventual consistency is.
@AyGeePlus said in Mongofail:
This isn't a question of consistency at all. It's not that <description of consistent behavior> it's that <other bad thing>
This particular flaw in mongodb has nothing to do with whether or not mongodb is eventually consistent or instantly consistent or not consistent at all. This is about mongodb not providing isolation, which is a different thing from consistency. We both agree about every part of this.
@blakeyrat I like you a lot, but cmon. Read.
-
Damn, beat me to it.
-
@AyGeePlus said in Mongofail:
Of the ACID guarantees, MongoDB provides just 'AC'.
No Durability? Ow…
-
@WPT I would argue no. Data accuracy/integrity is the whole point of using a database in the first place. If anything sacrifice speed since you can just not claim that you're a "real time" service (which is nonsense anyways, who cares how many seconds ago your friend tweeted something?). Or, fake it by only loading X number of results at a time (and waiting until we reach X before updating the feed). The user wouldn't know, or likely care, anyways.
If the accuracy of the data isn't important, there's no need to store it.
-
If the accuracy of the data isn't important, there's no need to store it.
If the durability of the data isn't important, you can just slap it in a CSV file and pretend that there are no issues with multiple systems accessing it. :)