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.
I’m really asking this by proxy, another team at work has had a change request from our customer.
The problem is that our customer doesn’t want their employees to login with one user more than one at the same time. That they are getting locked out and sharing logins.
Since this is on a web farm, what would be the best way to tackle this issue?
Wouldn’t caching to the database cause performance issues?
You could look at using a distributed cache system like memcached
It would solve this problem pretty well (it’s MUCH faster than a database), and is also excellent for caching pretty much anything else too