Cache consistency
Who should handle it?
- All current solutions, except object-oriented DBMSs leave most burden to application:
- application is conscious of cache
- application decides when to refresh
- Most caches are write-through
- No coordination among multiple caches
- Model does not scale (did not scale for OODBMSs, or for shared disk models)
How should it be handled?
- Two-phase commit
- Automatic (possibly delayed) propagation of updates
- ??