We have a bunch of microservices that manage their own cache keys and sometimes when they release they need to invalidate a bunch of their old cache keys at once. Prior to using memcached we were using redis as a cache and we just ran a single redis server per service so we would just flush all. Now that we are on a memcached cluster this is no longer acceptable.
I'm wondering what the best practices for this is? Do you prefix cache keys with <service>.<version> so that when a new version comes out they automatically get ignored and LRU'd? Or is there a way to scan through the servers/slabs and find the keys we want to kick out? Thanks, John -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
