Study notes 47_ about the limitations of the session, Memcache

Three big questions:

1.Session Performance Issues

2. Unable to stabilize the output. Consider using an out-of-process session

3. Compose a cluster, log in data for sharing

(for example, such as Baidu, Baidu Network disk, Baidu Library, etc. is the use of different service machines, how to avoid the use of the time without repeated login)

To address this type of problem, a dedicated machine is used to handle the public cache

A distributed Cache system: Memcache

Scene:

There are three machines, each deploying IIS, and the OA system

If you use a local session, then if you access the machine 1, then only the machine 1 has user information

At this time to use other functional modules, using the Machine 2, then can only re-login, not to get machine 1 user information

Distributed System: Memcache

Distributed Cache storage mode: Cache:key-value

Supplement: Session running mechanism is, when the user first request, will request a GUID as SessionID, return when put SessionID in the cookie, send to the user, at the same time in the native cache, place sessionid-session value; Each time a user requests a cookie containing SessionID to the server, the service can use the Key-value method to get the session value of the current requesting user.

The same is true for distributed systems, but not locally.

Study notes 47_ about the limitations of the session, Memcache