Why is an in-process cache like EHCache or Caffeine risky in a multi-instance deployment?

Each application instance holds its own separate copy of the cache — an update on one instance doesn't invalidate another instance's stale cached copy, since there's no shared state between them. A distributed cache like Redis solves this by giving every instance a single shared view.