Announcing Windows Server AppFabric Beta2 Release

We are excited to announce that the Beta 2 release of Windows Server AppFabric is now available for download via .  This is the Windows Server AppFabric build that works with the RC (Release Candidate) build of Visual Studio 2010/.NET 4. Windows Server AppFabric is a set of application services focused on improving the speed, scale,…


PDC talk My PDC talk on AppFabric Caching

Announcing "Windows Server AppFabric"

 At PDC 2009 we have announced roadmap and details on release of Microsoft project codenamed “Velocity” under Windows Server AppFabric, to download latest bits and more details please check out following links. On-Premises or in the Cloud, One Consistent Composite Application Experience for Developers Windows Server AppFabric  Thanks Microsoft project codenamed “Velocity” Team


Griddynamics benchmark on Velocity

Benchmark showcases Microsoft’s Project Code-named “Velocity” ability to Scale Web Application Grid Dynamics, a Microsoft partner, created three sample applications, designed to be typical use cases for data caching, and ran extensive benchmarking tests to evaluate their performance characteristics. The applications were a blogging engine, demonstrating the most basic features of Velocity caching technology; a…


PowerShell Scripting for Microsoft project code named "Velocity"

Windows PowerShell allows you to invoke C# code directly from the PowerShell scripts. This offers a powerful way to “script” cache operations such as puts/gets etc. This can be used to prime the cache as part of an automated setup or to perform other management tasks such as exploring the cache etc. This blog shows…

Troubleshooting “Velocity” Series – III (Continued)

How to control ETW sessions and collect traces   In this section I will describe how to work with an ETW sink. ETW stands for “Event Tracing for Windows”. It is a high speed tracing facility provided by the OS. It uses buffering and logging mechanism implemented in the OS kernel. The buffers used are…


Troubleshooting “Velocity” Series – III

How to use “Velocity” logging framework Microsoft project code named “Velocity” provides the ability to trace events on the cache client and cache host. These events are captured by enabling log sinks. A sink represents a valid destination to which logs or events can be emitted. “Velocity” supports three log sinks: ·         Console sink -…

Troubleshooting “Velocity” Series – II

How to ensure you have correct client libraries This section is more important for people who are upgrading from CTP2 to CTP3. Since Microsoft project code named “Velocity” bits are not backward compatible, while upgrading the cache hosts, “Velocity” clients have to be upgraded as well. There are four client libraries: 1.       ClientLibrary.dll 2.       CacheBaseLibrary.dll…

Troubleshooting “Velocity” Series

  Hi, Hope all of you are having great time caching your data with Microsoft project code named “Velocity”. This post is first in the series of some practices and guidelines to follow in order to make best use of “Velocity” and for troubleshooting any common issues you may face. I also recommend that you…


EF Query caching with Velocity

Jarek has written a blog and a sample of integrating caches into EF. One integration sample is using Velocity CTP3 bits. Take a look at Sample code at