Hi,

Up until now I have only developed relativly simple .NET solutions where the
app could run on a single box..

Could anyone direct med to some articles/books/best practices for
developing/deploying scalable clustered .NET solutions...something like 5-7
HTTP front machines...connecting to a couple of buisness
machines...connecting to a datastore or legacy systems...I have never done
this in .NET only in J2EE/UNIX...

FW
HTTP HTTP HTTP HTTP HTTP (this should be ASP.NET in DMZ)
FW
SERVICES SERVICES SERVICES (.NET Assemblies with components..)

DATASTORE

Hope you get the picture..

Regards
/Oscar

I'm guessing you'd be best off writing your own tool, or doing it manually,
but let's say what others say.

--itai

"Oscar Thornell" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> Up until now I have only developed relativly simple .NET solutions where
the
> app could run on a single box..
>
> Could anyone direct med to some articles/books/best practices for
> developing/deploying scalable clustered .NET solutions...something like
5-7
> HTTP front machines...connecting to a couple of buisness
> machines...connecting to a datastore or legacy systems...I have never done
> this in .NET only in J2EE/UNIX...
>
> FW
> HTTP HTTP HTTP HTTP HTTP (this should be ASP.NET in DMZ)
> FW
> SERVICES SERVICES SERVICES (.NET Assemblies with components..)
>
> DATASTORE
>
> Hope you get the picture..
>
> Regards
> /Oscar
>
>

excellent book: Advanced .NET Remoting by Ingo Rammer
Then study the Patterns and Practices section of MSDN at msdn.microsoft.com

that will get you a LOT further.

Good luck,
--- Nick

"Oscar Thornell" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> Up until now I have only developed relativly simple .NET solutions where
the
> app could run on a single box..
>
> Could anyone direct med to some articles/books/best practices for
> developing/deploying scalable clustered .NET solutions...something like
5-7
> HTTP front machines...connecting to a couple of buisness
> machines...connecting to a datastore or legacy systems...I have never done
> this in .NET only in J2EE/UNIX...
>
> FW
> HTTP HTTP HTTP HTTP HTTP (this should be ASP.NET in DMZ)
> FW
> SERVICES SERVICES SERVICES (.NET Assemblies with components..)
>
> DATASTORE
>
> Hope you get the picture..
>
> Regards
> /Oscar
>
>

Ok! I need to design the app ground up to be scalable...using .NET Remoting
to expose/communicate to my buisness layer...

Are there any support/ tools in Win 2003 Server/IIS 6 for this kind of
application...

What is the opinon regarding ASP.NET do we need a framework command/facade
like Struts to decouple the logic from the back-end??

/Oscar

"Nick Malik" <(E-Mail Removed)> wrote in message
newsIsXb.304365$I06.3088502@attbi_s01...
> excellent book: Advanced .NET Remoting by Ingo Rammer
> Then study the Patterns and Practices section of MSDN at
msdn.microsoft.com
>
> that will get you a LOT further.
>
> Good luck,
> --- Nick
>
> "Oscar Thornell" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hi,
> >
> > Up until now I have only developed relativly simple .NET solutions where
> the
> > app could run on a single box..
> >
> > Could anyone direct med to some articles/books/best practices for
> > developing/deploying scalable clustered .NET solutions...something like
> 5-7
> > HTTP front machines...connecting to a couple of buisness
> > machines...connecting to a datastore or legacy systems...I have never
done
> > this in .NET only in J2EE/UNIX...
> >
> > FW
> > HTTP HTTP HTTP HTTP HTTP (this should be ASP.NET in DMZ)
> > FW
> > SERVICES SERVICES SERVICES (.NET Assemblies with components..)
> >
> > DATASTORE
> >
> > Hope you get the picture..
> >
> > Regards
> > /Oscar
> >
> >
>
>