tbh if you are running .NET and SQL Server you don't really need a cache like redis or memcache since SQL Server has had an in-memory query cache built in for 12+ years now.
Thinking that would help is a mistake. Take it from someone who went to optimize SQL Server 2008 R2 to its limits.
Cache framework's are absolutely necessary. The whole idea is to avoid a SQL Server hit and return a cached data object in memory. I think Stackoverflow is the best case study here.
Same here. Considering what can be done with careful tuning of hardware and database structure, I can tell SQL Server's limits are very high, but nowhere near close to whatever MySpace needed.
SQL Server is the third best Microsoft product. Right after their natural keyboard and their mice lineup.
Cache framework's are absolutely necessary. The whole idea is to avoid a SQL Server hit and return a cached data object in memory. I think Stackoverflow is the best case study here.