Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There's another easier way built into memcached:

When you issue a delete you can specify "the amount of time the client wishes the server to refuse 'add' and 'replace' commands"

Maybe they couldn't afford to increase the read load so much but this seems easier than rewriting mysql's replication engine.



That would not be guaranteed to be correct since you don't know the precise time required for the dbs to be consistent.


memcached != memcache




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: