Official News from Microsoft’s Information Platform
Machine Learning Blog
o For example, a high-traffic online retailer could use Velocity to cache their product catalog information. Caching this information would drastically reduce the number of requests for the same data from the database. In this case, not only would Velocity provide better performance and a better user experience, but it would also reduce the load on the database backend.
o An ideal scenario for using Velocity is to cache application data across the entire web farm. Velocity allows the information cache to be scaled similarly to how website hosting scales across a large server farm or across a cluster of machines. Velocity’s information cache can be scaled as if it were a single unified entity while providing high availability to the cached data.
o Velocity also eases the development complexities that are often associated with high availability web sites by allowing any serializable CLR object to be cached and by providing access through simple cache APIs. Velocity can be configured to run as a service that can be accessed over the network or it can be run embedded within the application.
Comments in this blog are open and monitored for each post for a period of two weeks after the posting date. If you have a specific question about a blog post that is older than two weeks, please submit your question via our Twitter handle @SQLServer