3-tier architecture v. 3-server architecture

Posted by kawai on Stack Overflow See other posts from Stack Overflow or by kawai
Published on 2010-04-11T17:00:03Z Indexed on 2010/04/11 17:03 UTC
Read the original article Hit count: 904

Filed under:
|
|
|
|

I'm building a traditional .NET MVC site, so I've got a natural 3-tier software architecture setup (presentation in the form of Views, business layer in the controller, and data layer in the models and data access layer).

When I've deployed such sites, it usually goes either on one server (where the web site and db live), or two servers (a web server and a separate db server).

How does one go about a 3-server architecture (WEB, APP, and DB)? Would the web server just have the presentation (e.g. the physical View/aspx pages), the app server would hold the config file and bin folder, and the db server would remain as is?

My question is essentially, can you simply move the /bin and all app logic onto a separate server from the presentation views? If so, how do you configure the servers to know where to look? If there's a good primer somewhere or someone can give me the lowdown, I'd be forever indebted.

© Stack Overflow or respective owner

Related posts about c#

Related posts about .NET