NOTE
Spring Boot Cache Auto-Configuration
How Spring Boot conditionally creates cache infrastructure from classpath, properties, beans, and provider availability.
This is a historical learning note and may contain outdated or incomplete understanding.
Spring Boot cache auto-configuration follows the general Boot model: configuration classes are activated when required classes/properties/beans are present and when the application has not already supplied overriding infrastructure.
The result is typically a CacheManager and supporting cache abstraction integration selected from available providers/configuration.
Provider ordering and exact conditional classes change between Boot releases. The durable model is classpath + properties + conditional beans + user override backs off auto-configuration. Inspect the condition evaluation report when an unexpected cache implementation is selected.