📖 Scenario: You are building a simple Spring Boot application that fetches product details. To improve performance, you want to cache the product data so repeated requests do not hit the database every time.
🎯 Goal: Learn how to enable caching in a Spring Boot application using the @EnableCaching annotation and create a simple cacheable method.
📋 What You'll Learn
Create a Spring Boot application main class
Add the @EnableCaching annotation to the main class
Create a service class with a method to fetch product details
Use @Cacheable annotation on the service method to enable caching
💡 Why This Matters
🌍 Real World
Caching is used in real applications to speed up data retrieval and reduce load on databases or external services.
💼 Career
Understanding @EnableCaching and @Cacheable is important for backend developers working with Spring Boot to build efficient, scalable applications.
Progress0 / 4 steps
1
Create Spring Boot main application class
Create a class called ProductApplication annotated with @SpringBootApplication and add a main method that runs SpringApplication.run(ProductApplication.class, args).
Spring Boot
Hint
Use SpringApplication.run(ProductApplication.class, args); inside the main method.
2
Enable caching with @EnableCaching annotation
Add the @EnableCaching annotation above the ProductApplication class declaration to enable caching support in the Spring Boot application.
Spring Boot
Hint
Place @EnableCaching above @SpringBootApplication.
3
Create ProductService with cacheable method
Create a class called ProductService annotated with @Service. Inside it, create a method getProductById that takes a Long id and returns a String. Annotate this method with @Cacheable("products") and return a string like "Product " + id.
Spring Boot
Hint
Use @Cacheable("products") on the method that returns product details.
4
Complete application with caching enabled
Ensure the ProductApplication class has @EnableCaching and the ProductService class has the @Cacheable("products") method getProductById. This completes the caching setup in the Spring Boot app.
Spring Boot
Hint
Verify both classes have the correct annotations and method.
Practice
(1/5)
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
Step 1: Understand @EnableCaching role
This annotation activates Spring's caching support, allowing caching annotations to work.
Step 2: Connect with @Cacheable
Methods annotated with @Cacheable store their results in cache only if caching is enabled.
Final Answer:
To activate caching support so methods annotated with @Cacheable can cache results -> Option A
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
Step 1: Recall the exact annotation name
The correct annotation to enable caching is @EnableCaching.
Step 2: Check other options for typos
Options B, C, and D are incorrect because they are not valid Spring annotations.
Final Answer:
@EnableCaching -> Option C
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
Step 1: Understand caching effect on method calls
The first call to getData() runs the method, increments count to 1, and caches the result.
Step 2: Analyze second call behavior
The second call returns the cached result without running the method again, so count stays 1.
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
Step 1: Check caching activation
Defining a CacheManager bean is not enough; caching must be enabled with @EnableCaching.
Step 2: Verify other options
CacheManager returning null or invalid cache names are incorrect; @Service is unrelated here.
Final Answer:
Missing @EnableCaching annotation on configuration class -> Option B
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
Step 1: Enable caching globally
Add @EnableCaching on a configuration or main class to activate caching support.
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.
Final Answer:
Use @EnableCaching on config class, @Cacheable("users") on get method, and @CacheEvict(value = "users", key = "#userId") on update method -> Option D
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
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.