ASP.NET Issues Concerning Scalability

[amitos]

Scalability Issues - Any Ideas?

Dear All!

I'm working on the design of an ASP.NET 2.0-based web application that
has to scale horizontally (i.e. more web servers in parallel).

The main issue here is what are the coding, architectural and design
"best practices" that will allow the application to scale up. The
development environment is VS 2005. Hosting is done on Windows Server
2003 / IIS 6.0.

Have been looking around for books or articles about this, and couldn't
find anything that is both useful and simple to understand.

Awaiting your fruitful advice...
Thanks!

J.

[Juan T. Llibre]

What you need to do is setup MSCS
( Microsoft Windows Server 2003 Clustering Services ).

There's two types of clustering services : the cluster itself and Network Load Balancing.
If I'm not mistaken, configuring NIB should cover it for you.

There's an MSDN info center which has lots of info at :
http://msdn.microsoft.com/library/de...clustering.asp

And there's another info center at :
http://www.microsoft.com/windowsserv...g/default.mspx

The Technet info center for clustering is at :
http://technet2.microsoft.com/window.../genclust.mspx

The Technet chapters dedicated to Network Load Balancing should get you up and running.

These two are particluarly helpful :

http://technet2.microsoft.com/Window....mspx?mfr=true
http://technet2.microsoft.com/Window....mspx?mfr=true

Also, looking up Load Balancing in Windows Help and Support (on the Start Menu)
produces a lot of info on the specific steps you need to take to enable NLB.


Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"amitos" <am******@gmail.comwrote in message
news:11*********************@m73g2000cwd.googlegro ups.com...

Scalability Issues - Any Ideas?

Dear All!

I'm working on the design of an ASP.NET 2.0-based web application that
has to scale horizontally (i.e. more web servers in parallel).

The main issue here is what are the coding, architectural and design
"best practices" that will allow the application to scale up. The
development environment is VS 2005. Hosting is done on Windows Server
2003 / IIS 6.0.

Have been looking around for books or articles about this, and couldn't
find anything that is both useful and simple to understand.

Awaiting your fruitful advice...
Thanks!

J.

[amitos]

Thanks Juan. But I'm far more concerned with the ASP.NET issues
themselves. That is, I don't want to get stuck with an application that
won't scale. I'm looking for more info about that, at least at this
early stage of development.
Juan T. Llibre wrote:

What you need to do is setup MSCS
( Microsoft Windows Server 2003 Clustering Services ).

There's two types of clustering services : the cluster itself and NetworkLoad Balancing.
If I'm not mistaken, configuring NIB should cover it for you.

There's an MSDN info center which has lots of info at :
http://msdn.microsoft.com/library/de...clustering.asp

And there's another info center at :
http://www.microsoft.com/windowsserv...g/default.mspx

The Technet info center for clustering is at :
http://technet2.microsoft.com/window.../genclust.mspx

The Technet chapters dedicated to Network Load Balancing should get you up and running.

These two are particluarly helpful :

http://technet2.microsoft.com/Window....mspx?mfr=true
http://technet2.microsoft.com/Window....mspx?mfr=true

Also, looking up Load Balancing in Windows Help and Support (on the StartMenu)
produces a lot of info on the specific steps you need to take to enable NLB.


Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"amitos" <am******@gmail.comwrote in message
news:11*********************@m73g2000cwd.googlegro ups.com...

Scalability Issues - Any Ideas?

Dear All!

I'm working on the design of an ASP.NET 2.0-based web application that
has to scale horizontally (i.e. more web servers in parallel).

The main issue here is what are the coding, architectural and design
"best practices" that will allow the application to scale up. The
development environment is VS 2005. Hosting is done on Windows Server
2003 / IIS 6.0.

Have been looking around for books or articles about this, and couldn't
find anything that is both useful and simple to understand.

Awaiting your fruitful advice...
Thanks!

J.

[Mischa Kroon]

Have been looking around for books or articles about this, and couldn't
find anything that is both useful and simple to understand.

3 Simple rules of thumb:

Eliminate DB access as much as possible.
Cache where it makes sence ( page caching / fragment caching is the most
effective )
Try to cut down on viewstate and session state where you can by turning them
off

Other things that help:
Optimize your database with indexes where needed.
Measure where your bottlenecks are with stress testing tools performance
monitors and by simply turning tracing on.
Using the most lightweigth solution:
Datasets vs datareaders / Datagrids vs repeaters

Lots of articles semi basic to quite indepth:

http://www.google.com/search?q=performance+asp.net

[Juan T. Llibre]

I wish you had said that from the beginning.

;-)

The process is completely transparent and doesn't need anything
special done, except follow your standard programming Best Practices.

http://msdn.microsoft.com/practices/...s/default.aspx

http://msdn.microsoft.com/practices/...s/default.aspx

http://msdn.microsoft.com/practices/...g/default.aspx

Good luck!

Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"amitos" <am******@gmail.comwrote in message
news:11**********************@s13g2000cwa.googlegr oups.com...
Thanks Juan. But I'm far more concerned with the ASP.NET issues
themselves. That is, I don't want to get stuck with an application that
won't scale. I'm looking for more info about that, at least at this
early stage of development.
Juan T. Llibre wrote:

What you need to do is setup MSCS
( Microsoft Windows Server 2003 Clustering Services ).

There's two types of clustering services : the cluster itself and Network Load Balancing.
If I'm not mistaken, configuring NIB should cover it for you.

There's an MSDN info center which has lots of info at :
http://msdn.microsoft.com/library/de...clustering.asp

And there's another info center at :
http://www.microsoft.com/windowsserv...g/default.mspx

The Technet info center for clustering is at :
http://technet2.microsoft.com/window.../genclust.mspx

The Technet chapters dedicated to Network Load Balancing should get you up and running.

These two are particluarly helpful :

http://technet2.microsoft.com/Window....mspx?mfr=true
http://technet2.microsoft.com/Window....mspx?mfr=true

Also, looking up Load Balancing in Windows Help and Support (on the Start Menu)
produces a lot of info on the specific steps you need to take to enable NLB.


Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"amitos" <am******@gmail.comwrote in message
news:11*********************@m73g2000cwd.googlegro ups.com...

Scalability Issues - Any Ideas?

Dear All!

I'm working on the design of an ASP.NET 2.0-based web application that
has to scale horizontally (i.e. more web servers in parallel).

The main issue here is what are the coding, architectural and design
"best practices" that will allow the application to scale up. The
development environment is VS 2005. Hosting is done on Windows Server
2003 / IIS 6.0.

Have been looking around for books or articles about this, and couldn't
find anything that is both useful and simple to understand.

Awaiting your fruitful advice...
Thanks!

J.