News: Look at the CTP3 of our upcoming Distributed Cache technology – Velocity

If you develop high scale, scale out/distributed apps, check out

Microsoft Project Code Named “Velocity” Community Technology Preview 3 (CTP3) Released to Web on 7 April 09.

"Velocity" is a distributed in-memory application cache platform for developing scalable, high-performance applications. "Velocity" can be used to cache any common language runtime (CLR) object and provides access through simple APIs. The key aspects of "Velocity" are distributed cache performance, scalability, and availability.

This release contains several security and performance enhancements, as well as the new cache notifications feature which allows clients to be notified when changes are made at either the key, region, or cache level. In addition, it also includes numerous refactorings to its API, making it more conformant to the .NET Framework guidelines as well as easier to consume. “Velocity” is currently slated for release in the middle of this year and will represent an integral piece of our overall web/data story.
When complete it will be part of the .NET platform, ie: Free


Comments (2)

  1. joe says:

    Curious newbe question. I have a website I am working on where item detail pages allow the user to comment on the item. Then when the user hits their back button in the browser they are returned to the list of items which is saved in the browsers cache so it does not have to re-query to get the list again.

    My problem, is that I want the user to be able to add a comment on the item’s detail page, then hit the back button and when looking at the list, be able to see their comment on the list view for that item. I don’t want the page to have to reload everything from the database, everytime the user hits the back button, but I do want the list to have the updated comments from the user.

    Right now I am using some pretty kludgy cookies, ajax and jquery to get this to work but hopefully this "velocity" thing can help.

    There seems to be some big holes that still need to be filled by to maintain persistent state without constant reloads of data.

    Thanks for any thoughts.

Skip to main content