ARCast.TV - Scott Hanselman on scaling websites with caching
- Posted: Jul 27, 2009 at 6:54 AM
- 54,170 Views
- 9 Comments
Download
How do I download the videos?
- To download, right click the file type you would like and pick “Save target as…” or “Save link as…”
Why should I download videos from Channel9?
- It's an easy way to save the videos you like locally.
- You can save the videos in order to watch them offline.
- If all you want is to hear the audio, you can download the MP3!
Which version should I choose?
- If you want to view the video on your PC, Xbox or Media Center, download the High Quality WMV file (this is the highest quality version we have available).
- If you'd like a lower bitrate version, to reduce the download time or cost, then choose the Medium Quality WMV file.
- If you have a Zune, WP7, iPhone, iPad, or iPod device, choose the low or medium MP4 file.
- If you just want to hear the audio of the video, choose the MP3 file.
Right click “Save as…”
- High Quality WMV (PC, Xbox, MCE)
- MP3 (Audio only)
- MP4 (iPod, Zune HD)
- Mid Quality WMV (Lo-band, Mobile)
- WMV (WMV Video)
Architecting an enterprise or web application for high performance, scale, and availability can be a challenge without an appropriate caching strategy. One approach is to leverage a distributed caching platform to support the needs of performance, scale,
and availability. In this ARCast episode,
Scott Hanselman and
Joe Shirey discuss Microsoft's codename "Velocity" project and how it supports building out these types of applications as well as what architects and developers need to think about when implementing a distributed caching approach.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
When this thing is gonna release, I've been hearing about it for years, and the last CTP was out last April, I though the whole thing is dead already
What are the plans to bring Velocity to Azure?
Just use memcached like the rest of the world.
Memcached is cool, but Velocity has some features like failover and regions that memcached doesn't. With memcached if you lose a node, it's gone. With Velocity your data is replicated.
To me that sounds like you're trying to add reliability where there shouldn't be any; The cache layer. A cache is volatile; If stuff is gone, or it expires, you repopulate it. Leave reliability to the database, it's very good at it.
Yes and no. It depends on how easy it is to repopulate. If the date is write-through and hasn't been written to a persistent store, like activity date, then it's gone forever. If you're in a situation like a bank, talking to a mainframe, you may get charged for each hit to the backend and losing a cache could mean a chargeback.
That's true, admittedly I hadn't considered such a case, only thinking about in scenarios where e.g. memcached would work. Isn't caching a bit of a wrong term for such use however?
Valid points...perhaps "distributed memory server"?
Hehe.. Something like that.
Bonus points if you can make Velocity into an abbreviation describing it.
Remove this comment
Remove this thread
close