Scott Hanselman

Hanselminutes Podcast 116 - Distributed Caching with Microsoft's Velocity

June 8, '08 Comments [6] Posted in ASP.NET | ASP.NET Dynamic Data | ASP.NET MVC | Podcast | Programming
Sponsored By

image My one-hundred-and-sixteenth podcast is up. One of the big announcements coming out of TechEd this week was Microsoft' "Velocity" product, a distributed in-memory cache. I sit down with two of the architects of the project and try to get the real story. Check out Dare's excellent analysis of Velocity as well as the MSDN Page for Velocity where you can download the CTP1 and try it on your sites today.

Also check out memcached (Win32 port) and the unofficial memcached .net library as well as the ASP.NET providers for memcached as well as the providers on CodePlex. Hopefully we'll see some detailed benchmarks soon comparing Velocity and memcached. I'll also personally be looking at the Velocity APIs giving my feedback to the team for future CTPs.

Subscribe: Subscribe to Hanselminutes Subscribe to my Podcast in iTunes

If you have trouble downloading, or your download is slow, do try the torrent with µtorrent or another BitTorrent Downloader.

Do also remember the complete archives are always up and they have PDF Transcripts, a little known feature that show up a few weeks after each show.

Telerik is our sponsor for this show.

Telerik's new stuff is pretty sweet, check out the ONLINE DEMO of their new ASP.NET AJAX suite. RadGrid handles sorting, filtering, and paging of hundreds of thousands of records in milliseconds, and the RadEditor loads up to 4 times faster and the navigation controls now support binding to web services on the client.

As I've said before this show comes to you with the audio expertise and stewardship of Carl Franklin. The name comes from Travis Illig, but the goal of the show is simple. Avoid wasting the listener's time. (and make the commute less boring)

Enjoy. Who knows what'll happen in the next show?

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Sponsored By
Hosting By
Dedicated Windows Server Hosting by ORCS Web
Sunday, June 08, 2008 12:39:04 PM UTC
Although just coded this week, it is worth including a link to Ayende's NMemcached implementation: http://www.ayende.com/Blog/archive/2008/06/06/Scratching-an-itch-NMemcached.aspx . This is a memcached server written completely in managed code (wrapper around System.Web.Caching).
Monday, June 09, 2008 7:48:35 AM UTC
With all the new stuff coming up - SSDS, Velocity I'm really starting to wonder if this is the end of the database as we know it? Will the database become less relevant and just a backup mechanism for in memory objects or feeds? Is Prevalayer the future?
What if Flash based memory as mentioned in the podcast might totally change the game, maybe B-trees are no longer the appropriate?

Monday, June 09, 2008 10:53:43 AM UTC
Velocity is a cool name for this product - but did anyone ask the current maintainers of the Velocity and NVelocity view engine how they feel about the name ambiguity? Especially as it will swamp Google search results.
Monday, June 09, 2008 9:15:17 PM UTC
I think "Velocity" is just a codename. The actual product name will turn out to be something like Microsoft Distributed Caching Engine Via Super Fancy Clustering Suite Version 4 or MDCEVSFCS V4 for short (which of course will require .Net 3.0 or higher).

BTW MDCEVSFCS will simply be pronounced like "Mid-Sev-Suffix".

Wednesday, June 11, 2008 1:50:12 PM UTC
This will make life so much easier once it is released. Distributed session state out of the box...sweet!
Friday, July 18, 2008 2:20:48 PM UTC
pingback

Цветик-семицветик ... Velocity... или зачем нам еще один Distributed Cache?
http://dev.net.ua/blogs/leshchinsky/archive/2008/07/16/6492.aspx
Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.