Speed up your applications with Microsoft's Distributed Cache ("Velocity")
Ido Flatow
Whenever we write an application for the distributed world, no matter if it is the client's side or the service's side, we always try to cache information, to make things "go faster". But what to do when the service is in a cluster? How can we invalidate cached information that has been changed? How can we share cached information between applications? Such a simple task often turns out to be an architectural issue that makes us spends weeks in developing a caching mechanism. In this session we'll introduce Microsoft's Distributed Cache (AKA project "Velocity") - a highly scalable, in-memory cache that can boost up your applications , and allow them to share information without the need to always access your data source.
