@Cacheable checks the cache first and may skip the method entirely on a hit. @CachePut always executes the method (never skips it) and then updates the cache with the fresh result — used for methods that must always run (like a save/update operation) while still keeping the cache current. @CacheEvict removes an entry (or clears the entire cache with `allEntries = true`) from the cache, typically called on delete/update operations to invalidate now-stale cached data.

Intermediate5 min

AccentureCapgeminiCognizantOracleIBMAmazon

#@CachePut#@CacheEvict

What is the difference between @Cacheable, @CachePut, and @CacheEvict?

Forgetting @CacheEvict on Writes Is a Very Common Stale-Cache Bug

If a delete or update method isn't paired with a corresponding @CacheEvict (or @CachePut), the cache silently continues serving a now-outdated value indefinitely — this is one of the most common real-world caching bugs, precisely because the read path (@Cacheable) works perfectly and the bug only manifests as 'why is this stale data showing up' well after the write happened.

Keeping the Cache Consistent on Writes

java

@CachePut(value = "users", key = "#user.id")
User update(User user) { return userRepository.save(user); }

@CacheEvict(value = "users", key = "#id")
void delete(Long id) { userRepository.deleteById(id); }