Microsoft Project Code Named Velocity Introduction
[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]
Microsoft project code named "Velocity" provides a highly scalable in-memory application cache for all kinds of data. By using cache, your application performance can improve significantly by avoiding unnecessary calls to the data source.
By using distributed cache, your application can scale to match an increasing demand with increasing throughput. "Velocity" distributed cache is provided in the form of a cache cluster, which simplifies your application code by managing the complexities of load balancing behind the scenes.
When you use "Velocity," you can retrieve data by using keys or other identifiers, named "tags." "Velocity" supports optimistic and pessimistic concurrency models, high availabilty, and a variety of cache configurations.
You can install a small self-contained environment on your development workstation or use SQL Server to manage a large multi-server cache cluster for your enterprise.
The topics listed in the following table describe the various aspects of using the product.
| Topic | Description |
|---|---|
Describes what "Velocity" is and how to use it. |
|
Provides installation, configuration, troubleshooting, and administration guidance. |
|
Describes the APIs from a high level. Includes how-to topics for working with cache. |
|
Class Library |
Includes detailed descriptions of the distributed cache API. |
See Also
Tasks
How to: Prepare the Development Environment (Velocity)
Concepts
General Concept Models (Velocity)
Other Resources
Installation and Deployment (Velocity)
Using Basic Cache Methods (Velocity)