With "multi-level loosely-coordinated best-effort distributed cache" you certainly got the naming, all that's left is the cache invalidation. :)
Pascal On Jul 6, 2010, at 18:10 , John Kalucki wrote: > These lockouts are almost certainly due to a performance optimization > intended to reduce network utilization by increasing physical reference > locality in a multi-level loosely-coordinated best-effort distributed cache. > Not easy to get right, and the engineers involved are working to resolve the > issue. There's absolutely no intention to lock people out. > > -John Kalucki > http://twitter.com/jkalucki > Infrastructure, Twitter Inc. >
