Applied Architecture with MVC, WCF, EF

I am working on a web application, and later we plan to develop and distribute our mobile applications. I am not very experienced, but only based on my understanding planning this architecture:

  • The interface of the MVC web project, which will directly contact WCF services.
  • Server-side validation will be performed in the MVC model using data annotations, then the data will be transferred to the WCF level. Security using a client membership provider will also be implemented in MVC.
  • The WCF layer will work as a business layer. Where necessary, it will communicate with the DAL, which is a class library.
  • DAL using EF will communicate with SQL Server *

Questions please

  • Is this architecture good?
  • Is it good to use WCF as a layer of business layer and services?
  • on which layer should we implement which pattens?
  • for data verification and security - is this the right place for MVC?

thank

Edit 5. Is this good when testing? or for better testing, should I make some changes?

+5
source share
1 answer

What you are describing is a fairly modern and good Microsoft stack.

ASP.net MVC is a good web interface for you. If you are going with asp.net MVC, you should also look at asp.net webapi (new) for the business layer.

http://www.asp.net/web-api

http://weblogs.asp.net/scottgu/archive/2012/02/23/asp-net-web-api-part-1.aspx

SQL Server EF . - T-SQL, sql.

, - (MVC) - (web-api), - , , /. , html/javascript ajax web-api. "" (config) web-api. / , - .

( ) web-api. , brower/javascript, - - MVC.

web-api , . - . - ( -api), ( ) .

+4

All Articles