Best pratice design for a client with MVC RRS feed

  • Question

  • User1493112920 posted

    Hi !

    Just wondering about the best pratice design for a client with MVC.

    If you have a stand alone server with the following struture: Servicelayer->BusinessLayer->DataLayer

    The client is using WCF for data transfer and calling the the WCF methods that is in the ServiceLayer on the server.

    What is the best practice design for the client in this case. I dont want to manipulate data in the CLIENT. Is it enough with one layer ?   like RepositoryNameOrSometing that calling the ServiceLayer methods in server. Like this:    RepositoryNameOrSometing ->Controller->View  .    It not feels like it neassary with two layers like  Repository -> Service ->Controller->View . Because I already have it on the server. 

    Kind regards. 

    Monday, August 1, 2016 8:54 AM

All replies

  • User-821857111 posted

    The "best practice" depends on a lot of things that we can't know from your post. And it varies from one application to another. There is no formal pattern that all applications should fit. You need to understand the role that each "layer" plays and then decide for yourself whether they are appropriate to your current application.

    Tuesday, August 2, 2016 7:23 AM