Getting Started with Velocity

Getting Started with Velocity

Sergey Barskiy Principal consultant at Magenic Technologies SergeyB@Magenic.com http://DotNetSpeak.com www.Magenic.com info@Magenic.com

Velocity Velocity is now part of AppFabric

software (http://msdn.microsoft.com/en-us/library/bb896679.aspx)

AppFabric is available for Azure and Windows servers, so that you can have consistent coding regardless of where the application will be run.

What is Velocity Windows AppFabric Caching (previously called Velocity) is

a distributed in memory caching software. “Velocity” fuses memory across multiple computers to give a single unified cache view to applications. It allows for high-performance in memory access to cached data across multiple servers that use caching access. Thus, it is well suited for applications that run on web farms. It allows for clustering, so that you can scale up your caching solution as your needs grow. “Velocity” can be configured to run as a service accessed over the network or can be run embedded with the distributed application

Velocity Features

Caching of any serializable CLR object

Automatic load balancing across cache cluster (scalability)

Data stored on multiple nodes (availability)

Velocity Features (Cont.)

Integration with ASP.NET to be able to cache ASP.NET session data in the cache via custom sessionState provider (http://blogs.msdn.com/velocity/archive/2008/06/05/how-to-use-session-store-provider-microsoft-project-code-named-velocity.aspx ). This increases the performance and scalability of ASP.NET applications

Velocity Features (Cont.)

Regions ( data segregation into logical segments)

Expiration (time span based expiration of cached data)

Evictions (memory conservation) Notifications (when a cache operation

is performed)