Every cache pattern so far accepts that cache misses happen: a key expires, a request misses, and someone pays the cost of reloading from the database. Refresh-ahead attacks that directly. Instead of waiting for a hot key to expire and then reloading it (while a user waits), it refreshes the key in the background before it expires, so the cache is...