Invalidating cache love connection dating
If you want to invalidate selected objects but your users don't necessarily access every object on your origin, you can determine which objects viewers have requested from Cloud Front and invalidate only those objects.To determine which objects viewers have requested, enable Cloud Front access logging.
If you want to invalidate multiple objects such as all of the objects in a directory or all of the objects whose names begin with the same characters, you can include the wildcard, see Invalidation paths.For more information about the charges for invalidation, see Paying for Object Invalidation.To control the versions of objects that are served from your distribution, you can either invalidate objects or give them versioned file names.Now if the token is revoked, we have to remove the token from the data base and then invalidate the cache in all the nodes. Problem is that even a short term load spike lead to system level reset and repair. When I invalidate the cache, distributed cache has to know what nodes have the entry ( or send a message to all the nodes).
Setting up a cluster of stateless servers is easy ( or so we believe). OAuth), start a session, and keep invoking servers. When you invalidate an entry, it will take care of talking to all the nodes and invalidating the entry. If you want to recreate this problem, pick one of your favourite distributed cache, load about 1G data, and then run some cpu hogging processes in a those servers.