title: How to handle cache stampede when using hazelcast?
body: <p>My spring service is using hazelcast(embedded cluster) as local cache.</p>
  <p>When the cache expires due to TTL, if a large number of user requests come at once, the requests are transferred to the DB to update the cache. (cache stampede)</p>
  <p>For this reason, I thought about applying the PER algorithm, but from my understanding, the algorithm seems to be meaningful when the cache expiration time can be different for each node.
  However, it seems that hazelcast cluster cache cannot be applied because it uses a cache synchronized on a per-cluster basis. Is that correct?</p>
  <p>So, what strategy should hazlecast take to handle cache stampede?</p>