Assionshop open-source B2C e-commerce system-Overview

Today is a special day, and I have taken another step in the rental price in Beijing. On this day, I plan to start an open-source project, an EC system in the B2C industry.

 

I. Positioning

I want to do more than just a mall. It should be said that it is a perfect system that can meet the needs of small and medium-sized enterprises to establish e-commerce. Some of the modules include (but are not limited to) the following:

1. Front-end mall

1.1. display frame module of products on the front-end website, including the sales promotion strategy of the entire product, including classification, search, and various activities.

1.2. The shopping process at the front-end, including shopping cart, order, and payment. Customers in total may include general retail customers, major customers, and group buying customers.

1.3. Maintenance of the front-end user center, including personal information and business behavior information.

2. Background ecerp System

1.1. maintenance module for front-end display rack information, that is, the website management module. Corresponding operation role: website O & M personnel

1.2. The product management module manages the product categories, commodities, and other basic information. Corresponding operation roles: website O & M personnel and procurement personnel.

1.3. activity management module, including coupon system. The corresponding operation role is: website O & M personnel

1.4. The procurement module manages the inventory of goods and controls the shortage of goods in a system. The role of the corresponding operation is: purchaser

1.4. The sales order processing module processes orders. The corresponding operation roles are: Customer Service personnel, financial personnel, supervisor personnel, and so on.

1.4. The finance module handles the sales receipts and payment orders of the financial personnel. The corresponding operation role is: Financial Personnel

1.5. The after-sales module manages after-sales services and returns and exchanges goods. The corresponding operation roles are: Customer Service staff, after-sales staff, and logistics staff.

1.6. The logistics module handles the shipment, exchange, return, and other orders. Corresponding operation role: logistics personnel

1.7. The Warehouse Management module manages the warehouse. The corresponding operation role is the system administrator.

3. Miscellaneous

Of course, the system still needs permission support. There are many other things that can be iterated through incremental means.

 

Ii. Development Model

The best development mode is the "no" mode, which is suitable for you. However, there must be a basic idea. The system will adopt two DDD models, the first is domain driven design ),

The second is domain driven development. Of course, DDD is just an idea. We don't have to stick to it. Everyone has their own ideas.

You can.

I am not very familiar with this concept. I personally feel that there is really no need to understand the "too deep". I personally feel that the development model of a general small company is "not formal, very agile", because

Without a formal development methodology, it has always been an iterative process. There are no documents, oral communication, increments, and iterations.

 

Iii. Architecture

The architecture is just a preliminary idea. I will post it for your reference first.

 

 

 

I will briefly describe the above solution diagram one by one:

Assionshop. adminweb is a webform project, which is the UI Layer of the ecerp system we mentioned earlier. To do so, webform has some advantages.

The cache layer of the assionshop. Caching System is independent of the cache, because it plays an important role in the project. It supports object life and can abstract multiple cache architectures,

For example, Asp.net process cache and key-value-based distributed cache products.

Some common framework-level modules of the assionshop. Common system may include a series of supporting objects such as character processing, AOP, IOC, Orm, and log.

Assionshop. dbmap database ing layer. The Nhibernate framework can be used to solve the negative anti-DDoS problem of o-r. Why not directly in repositories? No.

Assionshop. Domain domain layer, which is the core business logic object of the system. It is not lazy to other task layers and is in the semi-congested mode. Persistence is not achieved by itself, and storage is responsible for persistence.

Assionshop. DTO: traditional data objects, including traditional data objects and corresponding adapters. Note: it is possible that DTO directly span the UI and repositories/dbmap, such as system reports.

Assionshop. repositories warehousing, responsible for domain factory production and lifecycle control, internal call cache and database to complete the persistence of domain objects.

Assionservices should be applicationservice rather than domainservice. It calls domain and repositories for lightweight assembly and provides APIs for the ui or SOA,

I put transaction control on this layer, and adopted MSDTC Distributed transactions. Services are reasonable for transaction boundaries.

Assionshop. Web Front-end mall web project. It is initially planned to use Asp.net MVC, like adminweb, to call services and reference DTO objects.

 

The above are the preliminary ideas and positioning of the project. There are many shortcomings that will be handled step by step. The next chapter begins with the case model.