ARCast.TV - Scott Hanselman on scaling websites with caching

Posted By: Bob Familiar | Jul 27th @ 6:54 AM | 49,990 Views | 9 Comments
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.
Rating:
2
0
#Jul 27th @ 11:55 PM
bashmohandesx
bashmohandesx
Me

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 Perplexed

#Jul 29th @ 11:01 AM
robvolk
robvolk

What are the plans to bring Velocity to Azure?

#Aug 1st @ 5:20 PM
Ian Joyce
Ian Joyce

Just use memcached like the rest of the world.

#Aug 2nd @ 2:02 AM
Glucose
Glucose
Scott Hanselman

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.

#Aug 2nd @ 10:34 AM
prencher
prencher

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.

#Aug 2nd @ 11:00 PM
Glucose
Glucose
Scott Hanselman

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.

#Aug 3rd @ 12:23 AM
prencher
prencher

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?

#Aug 3rd @ 12:45 AM
Glucose
Glucose
Scott Hanselman

Valid points...perhaps "distributed memory server"?

#Aug 3rd @ 10:09 AM
prencher
prencher

Hehe.. Something like that.

 

Bonus points if you can make Velocity into an abbreviation describing it. Wink

Microsoft Communities