<b_naick@yahoo.ca> wrote in message
news:f9530352-0aed-4550-8fba-7e6aba28194e@n58g2000hsf.googlegroups.com...
> Would like some input on site architecture. We're in a situation where
> we need to host/integrate multiple applications within a single site.
> For example: the URL of the main site needs to be http://www.mysite.com.
> The site contains 3 key features : call them feature1, feature2 and
> feature3. Each feature needs to be accessible via
> http://www.mysite.com/featureN.
>
> Each feature will be developed by different development partners. The
> goal is to make the entire site behave as one - single login, same
> look/feel etc. Given the "shared" nature of the development, we wnat
> to make sure that each feature runs in "isolation" and doenst
> interfere with the other apps. This is desired to prevent a bad app
> causing the entire hosting env to slow down. We'll also need the
> ability to deploy/undeploy each application independently.
>
> What site architectual options are available to support this?
>
> Thanks in advance.
>

<NoSpamMgbwo...@comcast.netNoSpamM> wrote:
> You can develop as separate applications and have them work together, as
> long as you are not sharing session variables. Provided each web applicati=
on
> uses the same keys, you can keep the same session, especially in a situati=
on
> like this. If you are sharing application variables, you have a bigger
> issue.
>
> The two areas you generally get bit when doing what you are doing are the
> config file and the database. As separate apps, you take care of the first=

> issue. Database schema is still a place of clashing.
>
> One way to reduce clashes is to host the source repository and force your
> vendors to get source from there. You can restrict vendors from seeing
> another vendors trees. This option is the safest, as you can test, on chec=
k
> in, whether or not everything is working. Cruise Control .NET, for example=
,
> can be set up to automatically test on check in.
>
> One way to reduce issues with the application(s) is have the applications
> built around libraries, with the UI as a thin skin on top of the
> functionality. This is the way applications should be written anyway (both=

> Silverlight and the new MVC framework force this separation of concerns).
> The issue here is if two companies build the same objects, so you need som=
e
> coordination, or you will have to refactor once done.
>
> --
> Gregory A. Beamer
> MVP, MCP: +I, SE, SD, DBA
>
> Subscribe to my bloghttp://gregorybeamer.spaces.live.com/lists/feed.rss
>
> or just read it:http://gregorybeamer.spaces.live.com/
>
> *************************************************
> | Think outside the box!
> |
> *************************************************<b_na...@yahoo.ca> wrote =
in message
>
> news:f9530352-0aed-4550-8fba-7e6aba28194e@n58g2000hsf.googlegroups.com...
>
>
>
> > Would like some input on site architecture. We're in a situation where
> > we need to host/integrate multiple applications within a single site.
> > For example: the URL of the main site needs to behttp://www.mysite.com.
> > The site contains 3 key features : call them feature1, feature2 and
> > feature3. Each feature needs to be accessible via
> >http://www.mysite.com/featureN.
>
> > Each feature will be developed by different development partners. The
> > goal is to make the entire site behave as one - single login, same
> > look/feel etc. Given the "shared" nature of the development, we wnat
> > to make sure that each feature runs in "isolation" =A0and doenst
> > interfere with the other apps. This is desired to prevent a bad app
> > causing the entire hosting env to slow down. We'll also need the
> > ability to deploy/undeploy each application independently.
>
> > What site architectual options are available to support this?
>
> > Thanks in advance.- Hide quoted text -
>
> - Show quoted text -