N-Tier architecture is just another way of saying distributed application.
A client and a server is an N-tiered architecture, a presentation layer, a
business layer and a data layer is an n-tiered architecture. It can be
implemented on a single or multiple machines. the n-tierdness (if there is
such a word) refers to the factoring out of the seperate units that make up
an application.
I believe that MS are not devoting a whole great deal of effort toward
remoting, and also there are issues to consider such as opening up ports in
the firewall etc., personally I would go for WebServices since these are used
over port 80 which is generally open for internet acccess, and all the client
needs know is the URL.
--
Of all words of tongue and pen, the saddest are: "It might have been"
Bill.Richards @ greyskin .co .uk
http://greyskin.co.uk [quoted text, click to view] "Silent Ocean" wrote:
> Hi
>
> 1. I am in process of designing N-Tier Application using ASP.NET. Can
> anyone guide me the right material or microsoft guidelines document
> which I can used in designing the N-Tier application.
>
> 2. I would also like to know whether to use Web Services or .Net
> Remoting in designing N-Tier application
> 3. General 3 Tier architecture has 3 Tier : Presentation Layer ,
> Business Layer and Database Layer
> How this 3 layers are seperated out in N-Tier architecture.
>
> Help would be very much appreciated.
>
> Thanks
>
> Silent Ocean