Defining reliable SIlverlight 4 architecture

Posted by doteneter on Stack Overflow See other posts from Stack Overflow or by doteneter
Published on 2010-04-11T16:51:21Z Indexed on 2010/04/11 16:53 UTC
Read the original article Hit count: 697

Filed under:
|
|
|

Hello everybody,

It's my first question on SO. I know that there were many topics on Silverlight and architecture but didn't find answers that satisfies me. I'm ASP.NET MVC developer and are used to work on architectures built with the best practices (loose coupling with DI, etc.)

Now I'm faced to the new Silverlight 4 project and would like to be sure I'm doing the best choices as I'm not experienced. Main features required by the applications are as follows :

  • use existing SQL Server Database but with possibility to move to the cloud.
  • using EF4 for the data acess with SQL Server.
  • exitensibility : adding new modules without changing the main host.
  • loose coupling.

I was looking at different webcasts (Taulty, etc.), blogs about Silverlight and came up with the following architecture.

  • EF 4 for data access (as specified with the requirements)
  • WCF RIA Services for mid-tiers controling access to data for queries and enabling end-to-end support for data validation, authentication and roles.
  • MEF Support for enabling modules.
  • Unity 2.0 for DI.

The problem is that I don't know how to define a reliable architecture where all these elements play well together. Should I use a framework instead like Prism or Caliburn? But for now I'm not sure what scenarios they support.

What's the best usages for Unity in Silverlight ? I used to use IoC in ASP.NET MVC for loos coupling and other things like interception for audit logging. It seems that for Silverlight Unity doesn't support Interception. I would like to use it to enable loose coupling and to enable to move to the cloud if needed.

Thanks in advance for your help.

© Stack Overflow or respective owner

Related posts about architecture

Related posts about silverlight-4.0