As promised during my TechTalk today at Microsoft Denmark, here are the links to all slides and demo code. Unfortunately you'll not be able to download the VPC's as those total around 30GB.
Read the complete 533 bytes...
Digg it |
Kick it |
Dzone it |
Reddit
Once you start distributing your ASP.NET website across multiple webservers, you're going to need a way to share session state. That is, unless your app is stateless, in which case scaling it should be a breeze!
Read the complete 3521 bytes...
Digg it |
Kick it |
Dzone it |
Reddit
One of the best way to improve performance of any website is to reduce the load from clients by allowing them to cache resources. There are various ways to ensure we utilize client side caching to the fullest extent, an often overlooked parameter however, is the actual URL for the resource we want to cache.
Read the complete 6743 bytes...
Digg it |
Kick it |
Dzone it |
Reddit
Once you start receiving visitors from all over the world, a new kind of scaling issue arise. It's not a matter of adding more servers to the cluster or optimizing code (we'll assume these factors are perfect), it's a simple matter of geography and mathematics. Serving code from one end of the world to the other will take time, no matter how quick your servers are handling the request. The speed of light suddenly seems quite slow.
Read the complete 16333 bytes...
Digg it |
Kick it |
Dzone it |
Reddit
There are two primary reasons for venturing into the realms of clustering/load balancing - availability & scalability. In this post I'll give a quick demo of how to setup Windows Network Load Balancing (NLB) on Server 2003 and how it affects the availability of a web application.
Read the complete 4885 bytes...
Digg it |
Kick it |
Dzone it |
Reddit