Currently,  annotations such as CacheEvict looks to be working only in some cases where we have Guice constructing the object. For instance, in module classes, it doesn't intercept the call for some reason that we don't know yet.

Either we have to fix that annotation to work everywhere across the codebase or we need an injectable mechanism which provides API to let us invalidate the cache in the downstream.

AC

• Introduce a mechanism to invalidate the cache in the downstream
  • Typical listener mechanism that receives calls and execute them accordingly in the cache level without exposing its implementation details
• Make sure cache is invalidated in S3 > EXTDAM-61