Spring Boot Cache with AES Parameter Encryption

Problem to solve

Spring Boot service methods often repeat database queries, but hand-written caching quickly runs into inconsistent key rules, sensitive parameters exposed in plaintext, and uneven Redis serialization. This skill targets those issues by providing an AOP plus Redis cache annotation pattern with AES parameter protection, suitable as a starting point for internal service caching.

How it works

• Use the CacheDataAnnotation annotation on a method, and let CacheDataAnnotationAop read or write the cache before and after method execution.
• Supports three key generation strategies: fixed key, SpEL expression, and class method name with AES parameter digest, in descending priority, so you can switch between stable keys and dynamic parameters.
• Method parameters are AES-encrypted before being used in keys or protected from plain exposure, reducing the risk of sensitive values entering cache keys directly.
• The setup includes Maven dependencies, Redis configuration, RedisConfig serializers, and annotation code; copy the files into the project and adjust package names.
• Null results are not cached by default, avoiding treating null as valid business data; caching nulls requires custom AOP changes.

Boundaries and cautions

• Cached objects must be serializable; prefer String, primitive wrappers, List, and Map with serializable elements.
• SpEL depends on parameter names, so compile with -parameters; methods must be public, non-static, and called through the Spring container, because self-invocation bypasses AOP.
• In production, configure Redis connection pooling, reasonable TTLs, key prefixes, and hotspot warm-up or invalidation policies.
• For queries that may return null, combine null caching, parameter validation, or Bloom filters to reduce cache penetration.