An Architectural decision with WCF RRS feed

  • Question

  • Hi,

    We are re architecting our internal ERP system in VS2010. At present we decided to use 100% browser based applications (Intranet). Here is my current setup

    Here are my n-layers
    1. Database (SQL 2008)
    2. ORM (EF 4)
    3. Repository pattern (Generic)
    4. Service Layer (All business logic here)
    5. Presentation layer (MVC)

    Based on above I have 2 option for physical tier setup (n- tier)

    Option A
    1. Database Server (Just a store SQL 2008)
    2. IIS 7 Server (Domain + MVC) which is (MVC > Service Layer > Repository > ORM)
    3. Client Browser

    Option B
    1. Database Server (Just a store SQL 2008)
    2. IIS 7 Server (MVC Just presentation logics)
    3. IIS 7 WCF Server (Model) which is (Web Service > Service Layer > Repository > ORM)
    4. Client (Browser, Blackberry etc)

    In OPTION-A MVC communicate in the same tier (IIS 7) to get database info. Basically no WCF, were as in OPTION-B MVC communicate with WCF Web Service (which is in another tier) to get database info.

    Performance, Extensibility and Security wise which option is more appropriate in the above scenario?


    • Moved by Bin-ze Zhao Thursday, February 11, 2010 10:38 AM architecture related question do not post here (From:Windows Communication Foundation)
    Saturday, February 6, 2010 5:36 PM


  • Hello,

    This should have been asked in the ASP.Net MVC forum on forums.asp.net.


    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
    My Blog: Unlock PowerShell
    My Book: Windows PowerShell 2.0 Bible
    My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

    • Edited by Just Karl Tuesday, January 28, 2014 9:08 PM
    • Proposed as answer by Just Karl Thursday, January 30, 2014 6:56 PM
    • Marked as answer by Just Karl Tuesday, February 11, 2014 11:18 PM
    Tuesday, January 28, 2014 9:07 PM