Architecture and technology of e-commerce website
3.1 Framework and Technology
This system mainly uses the .net framework and C# language as the main development tools, and the front-end uses the QUI front-end framework. Technical plug-ins include Redis cluster cache, RabbitMQ message, and MySql database. In fact, in an e-commerce system, most of the data can be cached, and very little data cannot be cached. This type of data includes data related to money, keys, and business-critical core data. In short, if you find that most of the data in the system cannot be cached, it means that there is something wrong with the architecture itself. How to solve the problems of consistency and real-time? The way to ensure consistency and real-time performance is: once the database is updated, the original cache must be updated, as shown in Figure 3.1:
Figure 3.1 System architecture diagram
Let’s talk about our caching solution: Our current caching system: Redis (master-slave) + RabbitMQ + cache cleaning service. The overall code design architecture is as follows, as shown in Figure 3.2:
Figure 3.2 System Diagram
3.2 Data structure
1) System resource monitoring, monitoring various network parameters and related resources of each server (CPU, memory, disk read and write, network, access requests, etc.), to ensure the safe operation of the server system, and provide an abnormal notification mechanism to allow system administrators to quickly Locate/solve various problems that exist. Currently more popular should be Zabbix.
2) Server monitoring The monitoring of the server is mainly to monitor whether the request response of each server, network node, gateway and other network equipment is normal. Through the timing service, regularly ping each network node device to confirm whether each network device is normal. If any network device is abnormal, a message will be issued to remind.
3) Service monitoring Service monitoring refers to whether various services of the platform system such as various web services, image services, search engine services, and cache services are running normally. You can use the timing service to request related services at regular intervals to ensure the normal operation of various services on the platform.
4) Application exception monitoring At present, the exception records of all systems on our platform are recorded in the database. Statistically analyze abnormal records within a period of time through timing services. If system abnormalities are found in related important modules, such as frequent abnormalities in the payment and order modules, the relevant personnel will be notified immediately to ensure the normal operation of the service.
5) Application performance monitoring intercepts and records the program performance (SQL performance, or program execution efficiency) at the API interface and relevant positions of each application. Relevant important modules provide performance warnings to detect problems in advance. At the same time, relevant monitoring information is collected and displayed to developers to facilitate subsequent performance analysis. The overall architecture diagram is shown in Figure 3.3.
Figure 3.3 Architectural icon for monitoring
3.3 Design the transaction process to meet the needs of users, the simpler the process, the better.
B2C business models include: Comprehensive shopping mall: Like traditional shopping malls, it has a huge shopping group, but online shopping malls are more popular.
Department store: This kind of store has its own warehouse and stocks a series of products for faster logistics and customer service. This kind of store will even have its own brand.
Vertical store: There are more similarities in the products of this kind of mall, either satisfying a certain group of people, or satisfying a certain need, or a certain platform (such as electrical appliances).
Functions for store sellers: 1) Provide supply and demand information services for online transactions between enterprises; 2) Provide additional information services; 3) Provide services supporting transactions; 4) Provide customer management functions.
The flowchart is shown in Figure 3.4:
Figure 3.4 Transaction flow chart
3.4 Main function introduction The online sales system is mainly divided into home page, retail product display, wholesale product display, member center, join us, and store background management.
The design of the page starts with an introduction
1. Concise and generous,
2. To improve user experience, the operation should not be too cumbersome while ensuring the most basic functions.
3. Shopping is divided into two sections, one is retail and the other is wholesale
4. There must be a homepage of the company, just like the homepage I gave you (the content inside) can be added.
5. When introducing the product, there must be a business hour of the merchant to which the product belongs
6. The payment method can be Alipay
7. Tourists can directly purchase goods on this website, no registration member is required, but such customers cannot comment on merchants and products. Only members can comment on purchased products. Interface classification:
Front-end external display:
1. Homepage: Head: Company log, login and registration entrance, navigation bar (required) Middle: product display (free design) Bottom: contact number, address, management login entrance.
2. Commodity display: free design of the middle block
3. Product details: free design of the middle block
4. Shopping cart
5. Place an order and pay
6. Member login and registration
7. Member Center: Inquiry of orders with history, editing of member information
8. Comment background management interface:
1. Company information management
2. Merchant check-in management
3. Merchants commodity management
4. Merchant order management
5. Member account management
6. Login to the management platform.
System administrator:
1. Navigation menu management. (of the main navigation menu of the admin front end)
2. Company information configuration. Fill in the company address and basic company information
3. Member management Manage member account information
4. Store management Fill in the store information to register the store
5. Commodity management: Commodity type management: Classify the commodities that need to be sold to facilitate sales. Commodity specification management: Commodities have specifications such as size, color, etc., here add specifications to commodities Commodity information management: Subject information of commodities (such as pictures, names, Prices, remarks, etc. are all maintained here) Commodity inventory management: how many commodities are in stock are maintained here.
6. Order management: order management -> here is where each store checks the orders of its own store products. Order Details Management -> Order Details Management. Order evaluation -> order evaluation management.