> "What happens in this case is that the cache is not invalidated. Because the transaction had not yet committed, the old version of object 12345 was loaded. Th

> "What happens in this case is that the cache is not invalidated. Because the transaction had not yet committed, the old version of object 12345 was loaded. The cache will now remain out of date until the TTL (if any) has passed." This seems contrived, does anybody actually do this ? Why wouldn't the app layer re-warm the cache itself, seeing as how it has the object already in hand ? Even if the app layer populates the cache, it shouldn't do so before the transaction is committed.