Architecture of small e-commerce websites

Ext: Architecture of the small e-commerce website

Another year end, this year, from the traditional software industry into the e-commerce enterprises, is a career change it. At first, I feel that the e-commerce site has no technical content, and there is no threshold, are some of the existing things piled up like piles of wood. However, after really entering the industry, it is not that. Remember someone said that good architecture is evolved. E-commerce website architecture is the same, now a good e-commerce website, it seems very complex, very cool, in fact, from a very small structure, but also from nothing technical content began. The evolutionary process of architecture is the process of pursuing the ultimate in the technical team.

Today to summarize the structure of the small e-commerce website, a set of e-commerce system in the initial framework, often using a more typical lamp architecture, front end plus apache/php, back end is MySQL. This is a more popular kind of. There is, however, a set of. NET technical architectures that may be rarely mentioned. Unfortunately, I am an e-commerce company based on a. NET platform. So, today is also to summarize the e-commerce architecture of the. NET Platform.

　　1. Technical framework

General, the initial e-commerce website, basic on several business subsystems, website front desk, merchant front desk, system management backstage, App,m station and so on. Business volume, also not very big. So, MVC + cache + database. Basically, it's done.

In fact, in terms of development efficiency alone, the technical architecture of. NET MVC will not be slower than lamp development. Therefore, some enterprises, in order to quickly launch their own e-commerce platform, will also adopt the. NET architecture.

　　2. Infrastructure

　　

Infrastructure level. This is a very simple infrastructure.

1. Front-end sites and M-stations, taking into account the volume of traffic and the availability of the system, are basically distributed deployments. Request distribution through a proxy server.

2. Other business subsystems, such as the merchant Front desk, and the management system, are basically standalone or master-slave deployments.

3. Each DB, Redis service and file and picture service, search engine SOLR service, etc., adopt master-slave deployment.

　　3. Detailed architecture

　　

The whole system architecture, there is a more important component, that is the monitoring system. For example: traffic monitoring, hardware monitoring, system performance monitoring, there is a page to monitor, set up a piece of the page to monitor and so on. It is an important means to improve the availability of the entire platform, multi-platform, multiple dimensions of monitoring, to ensure the availability of the system, in the event of anomalies, especially in the hardware or performance anomalies, monitoring system can immediately issue a warning, so as to prevent the unexpected.

In summary, a good system architecture should be considered in terms of extensibility, security, performance, and reliability. Rome is not built in a day, the structure is suitable for the line, you can first and then excellent. Through the process of gradual evolution, the system is gradually becoming more and more perfect.

Architecture of small e-commerce websites