@EnableCaching annotation in Spring Boot - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the @EnableCaching annotation in Spring Boot?

It activates Spring's annotation-driven cache management capability, allowing the use of caching annotations like @Cacheable in the application.

beginner

Where should you place the @EnableCaching annotation in a Spring Boot project?

You place it on a configuration class, often the main application class annotated with <code>@SpringBootApplication</code>, to enable caching across the app.

beginner

Which Spring annotation works together with @EnableCaching to cache method results?

The @Cacheable annotation marks methods whose results should be cached when @EnableCaching is active.

intermediate

True or False: @EnableCaching automatically configures the cache storage for you.

False. @EnableCaching enables caching support but you must configure the cache manager or use defaults like ConcurrentMapCacheManager.

intermediate

What happens if you forget to add @EnableCaching but use @Cacheable annotations?

The caching annotations will be ignored and no caching will occur because caching support is not activated without @EnableCaching.

What does the @EnableCaching annotation do in a Spring Boot app?

A Activates caching support for annotations like <code>@Cacheable</code>

B Automatically caches all database queries

C Disables caching in the application

D Configures the cache storage location

@EnableCaching turns on Spring's caching support so you can use caching annotations. It does not configure storage or cache all queries automatically.

Where is @EnableCaching typically placed?

A On every method to be cached

B On the database entity classes

C On a configuration or main application class

D On the cache manager bean only

It is placed on a configuration class to enable caching globally, not on individual methods or entities.

Which annotation requires @EnableCaching to work properly?

A <code>@Service</code>

B <code>@Cacheable</code>

C <code>@Component</code>

D <code>@Autowired</code>

@Cacheable needs caching enabled by @EnableCaching to cache method results.

If @EnableCaching is missing, what happens to @Cacheable methods?

A They run normally without caching

B They throw an error

C They cache results anyway

D They are ignored by Spring

Without @EnableCaching, caching annotations are ignored and methods run without caching.

Does @EnableCaching configure the cache storage automatically?

A No, it disables caching storage

B Yes, it sets up Redis by default

C Yes, it uses a file system cache

D No, you must configure or use defaults

@EnableCaching enables caching but you need to configure a cache manager or rely on Spring Boot defaults like in-memory cache.

Explain how @EnableCaching works in a Spring Boot application and why it is important.

Think about what happens when you want to cache method results.

Describe what happens if you use @Cacheable without @EnableCaching in your Spring Boot app.

Consider the role of <code>@EnableCaching</code> in activating caching.

Practice

1. What is the main purpose of the @EnableCaching annotation in a Spring Boot application?

easy

A. To activate caching support so methods annotated with @Cacheable can cache results

B. To disable all caching mechanisms in the application

C. To configure database connections automatically

D. To enable security features for REST endpoints

Solution

1. Step 1: Understand @EnableCaching role

   This annotation activates Spring's caching support, allowing caching annotations to work.

2. Step 2: Connect with @Cacheable

   Methods annotated with @Cacheable store their results in cache only if caching is enabled.

3. Final Answer:

   To activate caching support so methods annotated with @Cacheable can cache results -> Option A

4. Quick Check:

   @EnableCaching enables caching [OK]

Hint: Remember: @EnableCaching turns caching ON [OK]

Common Mistakes:

• Thinking @EnableCaching disables caching
• Confusing it with database or security annotations
• Assuming it caches data by itself without @Cacheable

2. Which of the following is the correct way to enable caching in a Spring Boot application?

easy

A. @CacheEnable

B. @EnableCache

C. @EnableCaching

D. @CachingEnable

Solution

1. Step 1: Recall the exact annotation name

   The correct annotation to enable caching is @EnableCaching.

2. Step 2: Check other options for typos

   Options B, C, and D are incorrect because they are not valid Spring annotations.

3. Final Answer:

   @EnableCaching -> Option C

4. Quick Check:

   Correct annotation spelling is @EnableCaching [OK]

Hint: Look for exact spelling: EnableCaching, not EnableCache [OK]

Common Mistakes:

• Using incorrect annotation names with similar words
• Missing the capital 'C' in Caching
• Confusing with other Spring annotations

3. Given the following Spring Boot code snippet, what will be the output when getData() is called twice?

@EnableCaching
@Service
public class DataService {
  private int count = 0;

  @Cacheable("dataCache")
  public String getData() {
    count++;
    return "Call number: " + count;
  }
}

medium

A. ["Call number: 1", "Call number: 1"]

B. ["Call number: 2", "Call number: 2"]

C. ["Call number: 0", "Call number: 1"]

D. ["Call number: 1", "Call number: 2"]

Solution

1. Step 1: Understand caching effect on method calls

   The first call to getData() runs the method, increments count to 1, and caches the result.

2. Step 2: Analyze second call behavior

   The second call returns the cached result without running the method again, so count stays 1.

3. Final Answer:

   ["Call number: 1", "Call number: 1"] -> Option A

4. Quick Check:

   Cache returns same result on repeated calls [OK]

Hint: Cached method runs once; repeated calls return cached result [OK]

Common Mistakes:

• Assuming count increments on every call despite caching
• Ignoring that @Cacheable caches method output
• Confusing cache key usage

4. Identify the error in the following Spring Boot configuration that prevents caching from working:

@Configuration
public class CacheConfig {
  @Bean
  public CacheManager cacheManager() {
    return new ConcurrentMapCacheManager("items");
  }
}

medium

A. Cache name "items" is invalid

B. Missing @EnableCaching annotation on configuration class

C. CacheManager bean should return null

D. CacheManager must be annotated with @Service

Solution

1. Step 1: Check caching activation

   Defining a CacheManager bean is not enough; caching must be enabled with @EnableCaching.

2. Step 2: Verify other options

   CacheManager returning null or invalid cache names are incorrect; @Service is unrelated here.

3. Final Answer:

   Missing @EnableCaching annotation on configuration class -> Option B

4. Quick Check:

   Enable caching with @EnableCaching [OK]

Hint: Always add @EnableCaching to activate caching [OK]

Common Mistakes:

• Forgetting to add @EnableCaching annotation
• Misunderstanding CacheManager bean role
• Wrong annotation usage on CacheManager

5. You want to cache results of a method that takes a user ID and returns user details. You also want to clear the cache when user data updates. Which combination of annotations and configuration correctly achieves this in Spring Boot?

hard

A. Use @EnableCaching on service class, @CachePut("users") on get method, and no annotation on update method

B. Use @CacheEvict on config class, @EnableCaching on update method, and no caching on get method

C. Use @Cacheable("users") on config class, @EnableCaching on get method, and @CacheEvict on update method

D. Use @EnableCaching on config class, @Cacheable("users") on get method, and @CacheEvict(value = "users", key = "#userId") on update method

Solution

1. Step 1: Enable caching globally

   Add @EnableCaching on a configuration or main class to activate caching support.

2. Step 2: Cache method results and evict on update

   Use @Cacheable("users") on the method fetching user details to cache results. Use @CacheEvict(value = "users", key = "#userId") on the update method to clear cache for that user.

3. Final Answer:

   Use @EnableCaching on config class, @Cacheable("users") on get method, and @CacheEvict(value = "users", key = "#userId") on update method -> Option D

4. Quick Check:

   Enable caching + cache get + evict on update [OK]

Hint: Enable caching, cache gets, evict on updates [OK]

Common Mistakes:

• Not enabling caching globally with @EnableCaching
• Using @CachePut instead of @CacheEvict for clearing cache
• Placing annotations on wrong classes or methods