|
-
Apr 29th, 2010, 03:09 AM
#1
Thread Starter
Hyperactive Member
Architecture Planning (Azure, MVC)
Hi,
I’m supposed to be designing solution architecture for an upcoming project (clearly the most advance I ever did and guaranteed to drive me nuts over the coming months). I'm trying not to let my knowledge shape the design, and rather create a solid, maintainable design and fill the gaps in my knowledge later.
Was hoping to hear what others think and help me shape this.
In a nutshell it will be an asp.net mvc application running on the azure platform (so I’ll be using azure table services for data storage and blob services for file services).
Been nutting out Entity Framework 4 (don’t know NHibernate at all) over the past few days and figured I’ll use that in the data access layer (c# class library) to map my domain model (another c# class library) to the data storage (still no idea how azure storage work, but will get to that).
My WCF skills are shaky, but I’m thinking of exposing data via services, though right now I cannot think of that being that useful….
* Front End: XHTML, CSS, JavaScript (jQuery & jQueryTools), AJAX
* Web Client: Asp.Net MVC 2
* Domain Model: C# Class library with POCO , interfaces and implementations (will be using Castle Windsor as IoC)
* Data Access Layer: Entity Framework mapping my domain model and data storage
* Azure Storage: … where that book of mine
Any advice, thoughts and critic will be welcome.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|