One of my websites (building the website architecture)

Preface

I have been traveling in the blog garden for about a year. I have read a lot of blog posts from bloggers in the blog garden every day, and I have benefited a lot from them. Because I am working on a. Net website, it is also good for websites. I also saw many open-source websites and open-source architectures of the great gods. Of course, too many of them did not understand them, and I knew exactly how many pounds I had. Sometimes I often write a few simple demos, but I have never done it before. I have been thinking about it over the past few days. If I want to create a website myself, I will surely get more fun and knowledge from it. Let's not talk about what kind of website we are doing. We have spent some time thinking about a simple architecture of our website. Because I still know little about it, the design capability is limited. Of course, I have to do my best. At the same time, I hope that a large number of bloggers and experts will offer support, let's talk about it. Okay, I won't talk about it anymore.

Website architecture

Development Environment 64-bit win7
The launch environment sets up a website in IIS, And the WCF Service is published as a Windows system service (which can be started with the computer, or manually enabled)
Development Tool vs2010 + database SQL Server 2008 +CodeManager SVN
Mainly uses ASP. net mvc 3.0 and WCF to implement website functions.

Direct

 

Next, let's take a look at the website architecture for the time being:

Mysoftware. basemodel ==>>> all object class structure definitions

Mysoftware. basecommon ==>>> common class library methods (string processing, various data conversion, etc)

Mysoftware. dataaccess ==>>> database access layer

Mysoftware. datacommon ==>>> Database Service Layer

Mysoftware. datawcf ==>>> WCF Service Interface and WCF Service Implementation Layer

Mysoftware. myfrmwcf ==>>> winfrom form hosts the WCF Service

Mysoftware. myservices ==>>> Windows System Service (publish WCF as a system service)

Mysoftware. simplemvc ==>>> mvc ui Layer

Mysoftware. simplemvccommon ==>> data processing logic layer

Mysoftware. simplemvc. Tests ==>> unit test project

Mysoftwre. projectextension ==>> Project Extension (Reserved)

The top two are public projects, and the following are the reference main lines of projects in turn.

Mysoftware. simplemvc to be referencedMysoftware. basemodel, mysoftware. basecommon, Mysoftware. simplemvccommon

Mysoftware. simplemvccommon needs to add services that reference mysoftware. datawcf.

Mysoftware. datawcf must reference mysoftware. datacommon

Mysoftware. datacommon to be referencedMysoftware. basemodel, mysoftware. basecommon, Mysoftware. dataaccess

Mysoftware. myfrmwcf must reference mysoftware. datawcf. To run the bearer service.

Summary

This is the initial architecture. I want to deploy my website in a distributed manner.ProgramAnd the WCF Service Program. Of course, the simplest thing is that website programs, WCF programs, and databases can all be deployed on one server. In this way, the significance of the distributed architecture is lost. You can deploy many website programs on many servers, and deploy a lot of WCF programs separately. In this way, you can share a lot of pressure (usually deployed on one server ), performance has been greatly improved. Of course, we also need to consider the cost, environment, and other reasons.

Next, I want to know what to do, how to do, and how to do the website content. A simple plan should not be too blind.