in reply to Re^6: Randomization as a cache clearing mechanism (races)
in thread Randomization as a cache clearing mechanism
Hm. The memcached API has five principal commands: get, add, set, replace & delete. Distinct add which fails in case the key is already present in the cache along with a deletion delay helps prevent races (not completely). I think that developers' intention is to avoid introducing locks or versions by all costs.
And yes, I wouldn't use memcached in a banking environment, it seems to be a MySQL-type product -- speed ahead of reliability.
Thanks for bringing it up. Doing things which will not do much harm to humanity in case of failure tends to shift priorities :)
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^8: Randomization as a cache clearing mechanism (races)
by ryantate (Friar) on Nov 21, 2004 at 23:01 UTC | |
by tye (Sage) on Nov 22, 2004 at 00:55 UTC | |
by kappa (Chaplain) on Nov 22, 2004 at 08:15 UTC | |
by tye (Sage) on Nov 22, 2004 at 15:23 UTC |