Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
“one memcache namespace per entity kind” Is a good idea? Any other impacts when compared to single namespace?
MemcacheServiceFactory.getMemcacheService("K1");
MemcacheServiceFactory.getMemcacheService("K2");
MemcacheServiceFactory.getMemcacheService("K3");
bad idea.
There’s a bunch of memecache APIs like cas_multi() which allows you to work with multiple keys in one efficient call. They’ll require all your keys to be within one namespace though, so splitting namespace by kind will mean you’re artificially limiting yourself.
Just use a prefix per kind when generating your keys.