Hello,


I am starting to plan a portal site that will eventually (hopefully)
increase exponetianlly in the amount of traffic to the site. I am
planning to do this in a 3-tier/4-tier layout, I'm just wondering of
any design considerations before I embark.


One thing I was thinking of is originally all tiers will reside on one
physical system, eventually the tiers will be seperated. Initially do I

want to create web services for each of the tiers? Or would I do that
when I am moving the tiers to additional systems. I guess my main
concern here is, how do I design the app so I can easily switch a layer

from non-webservice to a webservice without too many headaches. Maybe I

am thinking too much about the problem, but I am trying to get a full
lay of the land before I begin.


Any advice would be appreciated.


Thank you


DKode

Hi DKode,

It would be hard to really zero in on a set of measures that you can take to
be 'the' set. The bottom line is to reduce coupling between logical layers
in your application, and there are several patterns you can use to ensure
the same. I would urge you to look at the MSDN patterns and practices site
to understand these patterns. Since you are developing a web application,
you might want to look at patterns & practives for web applications
(http://msdn.microsoft.com/practices/...s/default.aspx)

--
HTH,
Manoj G
MVP, Visual Developer
http://msmvps.com/manoj

<dkode8 (AT) gmail (DOT) com> wrote