- Recent
- Popular
- Tags (1)
- Subscribers (3)
- PDC Videos are here!October 31 2008
-
Anil and myself presented Velocity at PDC - I did an overview (Intro) session while Anil did an under-the-hood and futures session. The videos are here
TL14 Project "Velocity": A First Look - Changes to Session State Provider Configuration (web.config) for CTP2October 29 2008
-
Some changes are needed to be done in the application's configuration (web.config) to use the session state provider with CTP2 binaries. The changes (the differences between CTP1 Yellow and CTP2 green) are listed below:
1) <configSections> :Under this tag the type attribute of "dcacheClient" and "fabric" elements are changed. The old and new values are shown below.
CTP1 config:
<configSections>
<sectionname="dcacheClient"type="System.Configuration.IgnoreSectionHandler"
allowLocation="true"allowDefinition="Everywhere"/>
<sectionname="fabric"type="System.Fabric.Common.ConfigFile, FabricCommon"
- Announcing CTP2 of Microsoft project code name "Velocity"October 27 2008
-
Today we are announcing CTP2 of Microsoft Project Code Name Velocity. Please download the CTP2 bits here. This entry will highlight what’s new with CTP2 and a follow-up request for feedback on what you would like to see in the product as we finalize on V1.
What’s New with CTP2?
CTP2 includes several new enhancements including High Availability, Performance improvements, PowerShell integration, Additional Configuration Store options and native 64 bit support.
-
High Availability: Starting in CTP2, "Velocity" supports continuous availability of cached data by storing copies of that data on separate cache hosts. By using high availability enabled on a multi-server cluster, your application can retrieve its cached data even if a cache server fails. Because the high availability feature is managed by the cache cluster, no code changes in your application are required to take advantage of it.
-
Performance and Stress Enhancements: In CTP2 we spent substantial effort on improving the Latency and Thruput of the system as well as the stress and uptime requirements of the distributed cache. The success of a caching product is defined inherently by its performance and stress capabilities and we will continue on enhancing our exit goals as we move towards V1 of
-
- Are you going to PDC? We are...October 3 2008
-
Come meet the Velocity Team in the pavilion and learn about Project "Velocity" in our 2 breakout sessions.
Project "Velocity": A First Look presented by Murali Krishnaprasad, Architect
It is predicted that all large applications will use a distributed data cache as the initial tier for all data access. This session presents an overview of "Velocity," Microsoft's distributed in-memory cache, and shows how it works with IIS, ASP.NET, ADO.NET and SQL Server Data Services.
Under the Hood: Velocity Architecture and Future Roadmap presented by Anil Nori, Distinguished Engineer
Velocity is an explicit, in-memory distributed cache. In this talk, we present Velocity's architecture to meet the high performance, scale, and availability requirements of web and enterprise applications. We will discuss mechanisms for data placement, data distribution, and data replication for performance, scale, availability respectively. We will describe mechanisms for providing database capabilities like LINQ support, indexing, concurrency control, and data consistency. We will also present the feature roadmap for Velocity.
- Velocity podcastJune 19 2008
-
Craig Shoemaker interviewed us at TechEd and has posted the podcast on his website -
Architecting Web Scalability
http://polymorphicpodcast.com/shows/scaletheweb/Muralidhar Krishnaprasad (MK) - MSFT