This morning, when I saw livesino's RSS feed, I found this message hidden in "teched 2008 developers: News Summary". Microsoft finally launched their distributed cache ( Distributed in-memory cache) .
Currently, the cache in Asp.net is on the local machine. If each machine in the Web farm needs to maintain its own cache, the most common cacheitem has a copy on each server. this not only wastes memory, but may also cause non-synchronization issues. The distributed cache solves this problem. in addition to large-scale enterprise applications, distributed cache is also widely used in Web websites to solve scaling problems. for example, the famous open-source software memcached is used by many large websites such as Wikipedia and Slashdot. For distributed cache, You can Google memcached and find many introductions.
Microsoft launched velocity (code name), which is still ctp1 currently. I Googled it and there is very little information, mainly including the two:
Velocity team blog: http://blogs.msdn.com/velocity/
. NET developers Journal: http://dotnetaddict.dotnetdevelopersjournal.com/velocity_introduction.htm
The main situations are summarized as follows:
- it runs as a Windows Service. It can be a cluster and runs on several cache servers
- TCP communication
- call add, put, and get to read/write cache. You can cache any serialized. Net object.
- In addition to key-based fetching, a cool function is to use tags to extract cached object sets.
- according to team blog, velocity is not only intended for Asp.net development, but also for. NET applications, such as non-. Net IIS applications and Windows Services.
- A currently unavailable but widely required function is push (notification, Message notification). After cached item is modified, the Code of the notification. velocity team said this is what they will focus on next (push-based notifications is a request we 've heard from getting folks. this is certainly an area we're re looking very deeply .)
- currently, it is a separate product and is said to be free of charge. It will be integrated into the. NET Framework in the future.
