Visual website building system for e-commerce shopping mall

Abstract

The invention discloses an e-commerce mall visual website building system, which is used for quickly building a mall homepage and an activity page and supporting page acceleration and dynamic resource management in a high-concurrency scene, and comprises a visual editing module, the visual editing module comprises a plurality of preset pendants, a user generates a page through dragging combination, and the page is used for editing the page. A page is quickly constructed by dragging a visual editing module, and the problems of low development efficiency and poor high concurrency performance in the prior art are solved in combination with a memory + Redis multi-level cache and a preheating mechanism. The system supports free combination of at least 48 components, the cache penetration rate is reduced by 80%, the page response time is less than or equal to 2 seconds, and the method is suitable for high-concurrency scenes such as e-commerce, big promotion and the like.

Description

Technical Field

[0001] The present invention relates to the technical field of e-commerce, and particularly to a visual website building system for e-commerce malls. In particular, it relates to a technical solution for quickly generating marketing pages through a drag-and-drop visual editing module and optimizing high-concurrency access by combining a multi-level caching mechanism. Background Art

[0002] The home pages and activity pages of existing e-commerce platforms (B2B / B2C) need to be implemented through manual coding or fixed template configuration. For example, the carousel images and links need to be configured separately in the background, and the floor layout requires developers to customize the code. Each marketing activity (such as holiday promotions) requires a large amount of development and testing time (about 4 - 5 days for development + 2 - 3 days for testing), and the traditional development model is inefficient.

[0003] There are also some systems that only provide limited components and cannot achieve customized pages through drag-and-drop combination, resulting in difficulty in quickly responding to user needs and insufficient flexibility.

[0004] There are also some manufacturers that provide visual editing functions but lack effective caching mechanisms and traffic control strategies, resulting in problems such as cache penetration and service crashes on activity pages under high traffic (for example, the response delay during a flash sale exceeds 5 seconds, and the request success rate is less than 50%), encountering high-concurrency performance bottlenecks. Summary of the Invention

[0005] To solve the above technical problems, the present invention provides a visual website building system for e-commerce malls, including a visual editing module that includes multiple preset widgets, and users can generate pages by dragging and combining them.

[0006] Preferably: The visual editing module supports multi-terminal adaptation for PC and mobile terminals, and a set of configurations can be synchronously published to H5, mini-programs, and APPs.

[0007] Preferably: It also includes a high-concurrency optimization architecture, which includes a front-end traffic limiting module, a multi-level caching module, a CDN static resource distribution module, and a hot spot preheating module.

[0008] Preferably: The front-end traffic limiting module realizes request traffic limiting through the Sentinel middleware.

[0009] Preferably: The multi-level caching module includes a first-level cache and a second-level cache, where the first-level cache is a memory fixed-duration cache, and the second-level cache is a Redis distributed cache;

[0010] First, check the first-level memory cache; if the first-level cache is not hit, query the second-level Redis cache; if the second-level cache is still not hit, obtain data from the read database; after obtaining the data, backfill it to the second-level and first-level caches as needed; for configuration change operations, automatically trigger the invalidation of relevant caches.

[0011] Preferably, the hotspot preheating module is used to preload page configurations and product prices into the cache before the event.

[0012] Preferably, it further includes backend technical components, which include a service governance module, a distributed transaction module, and a data synchronization module.

[0013] Preferably, the service governance module realizes service registration and discovery based on Nacos and performs traffic control through Sentinel.

[0014] Preferably, the distributed transaction module realizes cross-service transaction consistency through Seata.

[0015] Preferably, the data synchronization module listens for MySQL changes through Canal and triggers cache updates.

[0016] Technical effects and advantages of the present invention:

[0017] 1. The development efficiency in the present invention is improved: the page construction time is shortened from 5 days to 0.5 days, and the testing cost is reduced by 90%.

[0018] 2. High concurrency performance in the present invention: The stress test indicators show that the daily UV is 100,000, the PV is 450,000, the TPS is 1000, the page response is ≤2 seconds, and the request success rate is ≥70%. The cache penetration rate is reduced by 80%, and the server load is reduced by 60%.

[0019] 3. The flexibility in the present invention is enhanced: It supports the free combination of 48 components, covering marketing scenarios such as flash sales, group buying, and brand halls. Description of the Drawings

[0020] Figure 1 is the architecture diagram of the e-commerce mall visual website building system provided by the embodiment of the present application;

[0021] Figure 2 is the technical component selection diagram in the e-commerce mall visual website building system provided by the embodiment of the present application;

[0022] Figure 3 is the activity page acceleration description diagram in the e-commerce mall visual website building system provided by the embodiment of the present application. Detailed Embodiments

[0023] The present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. The embodiments of the present invention are given for purposes of illustration and description, and are not exhaustive or limit the present invention to the disclosed form. Many modifications and variations will be obvious to those of ordinary skill in the art. The embodiments are selected and described to better illustrate the principles and practical applications of the present invention, and enable those of ordinary skill in the art to understand the present invention and design various embodiments with various modifications suitable for specific purposes.

[0024] The present invention provides an e-commerce mall visual website building system, including a visual editing module that includes multiple preset widgets, and users can generate pages by dragging and combining them.

[0025] The visual editing module supports multi-terminal adaptation for the PC side and the mobile side, and a set of configurations can be synchronously published to H5, mini-programs, and APPs.

[0026] It also includes a high-concurrency optimization architecture, and the high-concurrency optimization architecture includes a front-end traffic limiting module, a multi-level cache module, a CDN static resource distribution module, and a hot preheating module.

[0027] The front-end traffic limiting module realizes request traffic limiting through the Sentinel middleware.

[0028] The multi-level cache module includes a first-level cache and a second-level cache. The first-level cache is a memory fixed-duration cache, and the second-level cache is a Redis distributed cache;

[0029] First, check the first-level memory cache; if the first-level cache is not hit, query the second-level Redis cache; if the second-level cache is still not hit, obtain data from the read database; after obtaining the data, backfill it to the second-level and first-level caches as needed; for configuration change operations, automatically trigger the invalidation of relevant caches.

[0030] The hot preheating module is used to preload page configurations and commodity prices into the cache before an event.

[0031] It also includes backend technical components, and the backend technical components include a service governance module, a distributed transaction module, and a data synchronization module.

[0032] The service governance module realizes service registration and discovery based on Nacos, and performs traffic control through Sentinel.

[0033] The distributed transaction module realizes cross-service transaction consistency through Seata.

[0034] The data synchronization module listens for MySQL changes through Canal and triggers cache updates.

[0035] Through hierarchical decoupling, service governance, and cluster deployment, this architecture constructs a secure, reliable, and easily maintainable distributed system. Its design fully considers the high-concurrency challenges in the e-commerce scenario, combines cloud-native technologies (Docker, Nacos) and mature middleware (Redis, MySQL cluster), providing a solid technical foundation for business growth. Whether in daily operations or large-traffic promotions, the system can maintain stable and efficient service capabilities.

[0036] Please refer to Figure 1 , in this embodiment, an e-commerce mall visual website building system is provided, including a visual editing module, a multi-level cache module, and a preheating module. The visual editing module includes multiple prefabricated widgets. Users can generate a front-end page by dragging and combining the prefabricated widgets and configure the front-end page to obtain a configured front-end page.

[0037] In the embodiment of the present invention, the above-mentioned prefabricated widgets include, but are not limited to, carousel, seckill component, and group-buying component. The above-mentioned front-end can be the PC side or the mobile side of e-commerce users. Users can manage their e-commerce malls through the PC side or the mobile side, drag and combine the prefabricated widgets to generate a front-end page, which is more efficient than the existing method of manually coding or configuring with a fixed template for the home page or activity page of an e-commerce platform.

[0038] Furthermore, a component library is set in the visual editing module. The component library provides at least 48 kinds of preset widgets (such as carousel, seckill component, group-buying component), and users can generate a page by dragging and combining them.

[0039] Currently, more than 48 widgets have been developed, including the following:

[0040] ejoy-custom-html - Custom code widget

[0041] ejoy-goods-ranklist - Commodity sales ranking list

[0042] ejoy-boot-activity - Home page startup activity widget

[0043] ejoy-activity-kill - Seckill widget

[0044] ejoy-activity-group-buy - Group-buying widget

[0045] ejoy-three-item-list - Three-column commodities

[0046] ejoy-sku-item-list - Two-column / three-column goods list

[0047] ejoy-revision-nav-floor - Top navigation bar of the product

[0048] ejoy-goods-sale - Direct price reduction activity

[0049] ejoy-goods-display - Product display pendant

[0050] background-image - Page background image pendant

[0051] ejoy-revision-nav-widget-floor - Top navigation bar of the pendant

[0052] ejoy-revision-nav-page-widget-floor - Top navigation bar of the paging pendant

[0053] ejoy-activity-goods-sale - Direct price reduction list pendant

[0054] birthdat-gift - Birthday gift offer

[0055] ejoy-rich-text - Rich text pendant

[0056] ejoy-secondary-page-search - Secondary page - Top search bar

[0057] ejoy-secondary-page-simple-graph - Secondary page - Header background image

[0058] ejoy-secondary-page-order-type-entrance - Secondary page - Name navigation classification pendant

[0059] ejoy-secondary-page-hot-sale-products - Secondary page - Best-selling products pendant

[0060] ejoy-secondary-page-brand-selection - Secondary page - Brand selection pendant

[0061] ejoy-secondary-page-list-goods - Secondary page - Product list pendant

[0062] ad-brand-description - Brand description pendant

[0063] brand-palace - Brand museum - Brand list pendant

[0064] ejoy-five-hundred-twenty-activity-Newcomer 520 Event Widget

[0065] ejoy-alone-slide-show-Slideshow - Standalone

[0066] ejoy-activity-kill-six-column-Flash Sale Widget (Six Columns)

[0067] ejoy-activity-nthpieces-N Yuan N Pieces Widget

[0068] ejoy-activity-bargain-Bargaining Widget

[0069] ejoy-activity-group-buy-new-Group Buying Widget (Exclusive to Events)

[0070] ejoy-new-yorker-Popup Widget (For New Customer Exclusive Jumps)

[0071] activityDiscounts2-Discounted Products

[0072] activityHeader-Event Header

[0073] activityGift2-Exclusive Gift

[0074] activityDiscountsGroupKill2-Coupon Center Group Buying and Flash Sale

[0075] ejoy-category-list-Category Page

[0076] remove-back-icon-Remove Back Button

[0077] ejoy-remove-bottom-navigation-Remove Bottom Navigation Menu

[0078] ejoy-category-list-second-Category Page - Second

[0079] newCategoryList-New Category Page

[0080] ejoy-store-sku-item-list-Two / Three Column Product List

[0081] ejoy-store-category-index-Store Events

[0082] homeSwiper - Home page carousel

[0083] homeBtns - Home page buttons

[0084] homeDiscounts - Home page discount dynamics

[0085] homeBrand - Home page brand selection

[0086] homeGood - Recommended good selection

[0087] homeCoupon - Home page coupon center

[0088] It can be understood that the preset widgets are not limited to those described in this application and can be further developed according to actual needs.

[0089] Furthermore, the visual editing module also supports multi - terminal adaptation for the PC side (ElementUI) and the mobile side (UniApp), and a set of configurations are synchronously published to H5, mini - programs, and APPs.

[0090] The above - mentioned backend development components are used for backend response support. When accessing the e - commerce mall page from the front - end, service registration and discovery implemented by the backend based on the Nacos architecture are used, and the Sentinel component is used for traffic control.

[0091] Nacos is a cloud - native application supporting tool open - sourced by Alibaba, mainly applied to scenarios such as service discovery, configuration management, and service management, aiming to simplify service governance work in microservice architectures. Nacos is particularly suitable for building and managing microservice architectures of modern cloud - native applications.

[0092] Sentinel is a high - availability traffic protection component for distributed service architectures. It mainly takes traffic as the entry point and helps developers ensure the stability of microservices from multiple dimensions such as flow limiting, traffic shaping, circuit breaker degradation, system load protection, and hot - spot protection.

[0093] It includes a front - end flow - limiting module that realizes request flow limiting through the Sentinel middleware and returns a friendly prompt page after the trigger threshold.

[0094] Set up a multi - level cache module: including a first - level cache module and a second - level cache module.

[0095] Specifically, the first - level cache module uses in - memory fixed - duration caching (TTL = 5 minutes) and supports manual cleaning.

[0096] The second - level cache module uses Redis distributed caching and automatically invalidates when the configuration changes.

[0097] It also includes a CDN static resource distribution module that distributes page static resources (such as images, CSS) to edge nodes.

[0098] It also includes a hot spot preheating module that preloads page configurations and product prices into the cache before an event to avoid cache penetration. The preloading function for hot event pages, the pre-caching mechanism for product prices, intelligent preheating based on access prediction, and support for monitoring and alarming of the preheating progress.

[0099] In a specific embodiment, in the scenarios of 60% browsing requests, 10% search requests, 10% registration and login, and 20% shopping orders, the following technical indicators can be achieved in the stress testing environment:

[0100] 1. The daily UV count reaches 100,000

[0101] 2. The daily PV count reaches 450,000

[0102] 3. The daily order volume is 500,000

[0103] 4. The concurrent connection count is 6000 (SLB concurrent count, not the stress testing thread concurrent count)

[0104] 5. TPS (requests per second) is 1000 (for receiving coupons)

[0105] In the stress testing environment with the above indicators, the page response speed does not exceed 2s, and the request success rate is not less than 70%.

[0106] It can be seen that for the front-end mall, under normal circumstances in the production environment (the ping website return time should reach the standard within 30ms).

[0107] In H5 and mini-program applications, the server TTFB < 500ms; the DOM loading completion time < 800ms.

[0108] In the APP (excluding the embedded H5), the APP cold start time < 1s; the APP page switching time < 500ms; the APP fluency > 30fps.

[0109] In the back-end console system, the average response speed for daily functional operations needs to be within 3s, and the response time for regular product searches and member searches is within 2s.

[0110] Refer to Figure 2 As shown, in this embodiment, the overall system development framework includes front-end development components, back-end development components, and technical components.

[0111] In front-end development, multi-terminal adaptation, including mobile terminal adaptation solutions, can improve development efficiency, reduce development costs, and improve user experience and product quality.

[0112] Specifically, the UniApp framework (cross-platform framework) is adopted, and a set of codes can generate mini-programs, APPs, and H5 pages simultaneously, saving time and effort.

[0113] It also includes content development components, which are used to improve the reusability of the code, ensure the maintainability of the code, optimize the development efficiency, improve the reliability of the system, and reduce the complexity of the system.

[0114] Specifically, the Vue framework is adopted. The flexibility and componentization of Vue facilitate the development and maintenance of dynamic content.

[0115] It also includes a PC-side adaptation solution, which uses Vue.js (front-end framework) and ElementUI (UI visualization editing module) to quickly build a beautiful management background.

[0116] It also includes the development of the back-end management page. The Spring MVC / Extjs components are adopted, and the function of dynamically loading permission menus is realized by combining Extjs with SpringMVC. The permission menus are formed by dynamically loading data from the background and are used for the development of the back-end management page.

[0117] The back-end development components include a development scaffolding. The SpringCloud is used to build the development scaffolding (the microservice full set), which is used to disassemble complex businesses and enable each functional module (such as orders and users) to be developed, deployed, and extended independently.

[0118] Furthermore, the development scaffolding has built-in templates and tools to avoid reinventing the wheel and improve the development efficiency.

[0119] It also includes an authentication and authorization module. A Web application with multi-layer authentication and authorization using the Spring Security framework is adopted, which provides rich authentication and authorization functions and flexible configuration. The JWT framework is used for identity verification in API calls, and the identity verification and authorization mechanism in the construction of online services is used to manage user login permissions to ensure that only legitimate users can access specific functions.

[0120] It also includes a client-side load balancing algorithm, which adopts mainstream open-source frameworks and platforms such as K8s Ingress or SLB or Dubbo to automatically distribute user requests to different servers to avoid overloading a certain machine.

[0121] It also includes a declarative service call client, which adopts the Dubbo Consumer configuration and uses the Dubbo server to process the client's declarative service calls. It is a high-performance remote call framework that makes it as simple as calling local methods between microservices.

[0122] It also includes an API gateway component. Spring Cloud Gateway is used to build functions such as routing, filtering, and load balancing in the microservices architecture, providing a unified entry to handle routing, rate limiting, and authentication, and managing all requests like a "front desk".

[0123] It also includes a remote call framework, which is a core tool for realizing communication between services in a distributed system.

[0124] Specifically, the Dubbo framework is adopted, which is based on the high-performance TCP long connection of Netty and is suitable for high-concurrency and low-latency scenarios

[0125] It also includes an API configuration center, which provides rich APIs and uses K8s secrets to configure sensitive information of applications.

[0126] It also includes a data persistence layer framework for ensuring the permanent storage and management of data. Specifically, the MyBatis framework is adopted, which is a flexible data persistence layer framework that facilitates writing SQL and managing database interactions.

[0127] The technical components include service registration and discovery and a configuration center. The Nacos management platform is adopted, which integrates functions such as service registration and discovery, dynamic configuration management, dynamic DNS service, and service and metadata management.

[0128] It also includes a performance diagnosis component. Specifically, Alibaba Cloud Monitoring is adopted to monitor metrics such as CPU and memory in real time and automatically alarm in case of anomalies.

[0129] It also includes distributed tasks. Specifically, the Xx-job lightweight distributed task scheduling framework is adopted, which is mainly used to manage and schedule various types of tasks, including timed tasks, sharding tasks, process tasks, etc. Its design goal is to be developed quickly, easy to learn, lightweight, and easy to expand.

[0130] It also includes a data fault tolerance protection module. Sentinel is a high-availability traffic protection component for distributed service architectures, which is used for traffic control and circuit breaking to prevent the system from being overwhelmed by sudden traffic (such as automatically limiting traffic during flash sales).

[0131] It also includes a service full-link tracing framework. SkyWalking is adopted as an open-source observable platform, which is used to collect, analyze, aggregate, and visualize data from services and cloud-native infrastructure for full-link tracing to quickly locate performance bottlenecks.

[0132] It also includes a distributed transaction framework. Seata is adopted as an open-source distributed transaction solution, which is used to provide high-performance and easy-to-use distributed transaction services in the microservices architecture to solve data consistency problems in scenarios such as cross-service transfers and placing orders.

[0133] It also includes a data change monitoring framework that uses Canal to synchronize data from MySQL to other databases in real time, monitors changes in the MySQL database (such as order status updates), and synchronizes them to other systems in real time (such as updating the cache).

[0134] It also includes a logging component that uses SIf4j as a simple facade or abstraction for various logging frameworks, allowing end users to insert the required logging framework during deployment, unifying the log format, and facilitating problem troubleshooting (such as quickly locating logs when users report errors).

[0135] This architecture is like an all-in-one toolbox: Vue and UniApp are used for multi-terminal adaptation in the front end; SpringCloud and Dubbo are used to build high-performance microservices in the back end; security, load balancing, and monitoring are all available to ensure system stability; details such as databases, caches, and task scheduling are also covered.

[0136] Whether developing an e-commerce platform, an OA system, or an Internet of Things application, it can be quickly implemented based on this architecture and easily handle high concurrency and complex business scenarios.

[0137] Please refer to Figure 3 As shown, in this embodiment, the technical architecture in an e-commerce mall visual site-building system is as follows. This architecture is a high-performance distributed system based on microservices, designed for high-concurrency, highly available e-commerce or service platforms, and capable of supporting multi-terminal access, massive data processing, and elastic expansion.

[0138] The following is a detailed description of each layer:

[0139] 1. User access and security protection

[0140] Multi-terminal support: The system covers the PC side, mini-programs, APPs, back-end management users, and merchant users to ensure consistent access across all channels.

[0141] Security and load balancing: WAF (Web Application Firewall): Protects against network attacks such as SQL injection and XSS to ensure application security;

[0142] SLB (Load Balancing): Optimizes resource utilization through traffic distribution, avoids single-point overload, and supports horizontal expansion;

[0143] Firewall: Further isolates the internal and external networks and restricts illegal access.

[0144] 2. Static resources and storage

[0145] CDN (Content Delivery Network): Accelerates global access to static resources such as images, CSS / JS, etc., reducing latency;

[0146] OSS (Object Storage): Provides highly reliable and scalable file storage services, supporting massive amounts of unstructured data (such as product images, log files).

[0147] 3. Application Service Layer

[0148] Core services (such as user sites, merchant backends, scheduling services) run in isolated Docker containers, enabling rapid deployment, version rollback, and resource isolation.

[0149] Service Registration and Discovery (Nacos): Dynamically manages microservice instances, supports graceful online and offline operations, avoids service interruptions, and dynamically manages microservice online and offline operations to avoid the embarrassment of "service not found".

[0150] Traffic Control (Sentinel): Through circuit breaker, degradation, and flow control strategies, it prevents the avalanche effect and enhances the resilience of the system.

[0151] Horizontal Scaling: Microservices such as Service1 and Service2 can be independently scaled up or down to handle business peaks (such as large promotional activities).

[0152] 4. Data Layer

[0153] Stores hot data (such as user sessions, product inventories), significantly reducing the pressure on the database, and the response time can reach the millisecond level.

[0154] Master-Slave Architecture: The master database (Mysql1) processes write requests, and multiple slave databases (Mysql2, Mysql3) share the read load, improving throughput.

[0155] High Availability: When the master database fails, it automatically switches to a slave database to ensure data persistence and service continuity.

[0156] Database Sharding: Supports the storage of tens of millions of product / user data, avoiding the performance bottleneck of a single table.

[0157] 5. Core Advantages and Business Support

[0158] Elastic Scaling: The combination of microservices and containerization enables rapid expansion of instances or nodes on demand.

[0159] Disaster Recovery Capability: Multi-node deployment, Sentinel circuit breaker, and database cluster ensure that local failures do not affect the overall situation.

[0160] Supports tens of millions of concurrent user accesses and processes millions of orders per day.

[0161] Static resource CDN acceleration, dynamic requests optimized by microservices, and overall response is efficient and stable.

[0162] Through hierarchical decoupling, service governance, and clustered deployment, this architecture constructs a secure, reliable, and easily maintainable distributed system. Its design fully considers the high-concurrency challenges in the e-commerce scenario, combines cloud-native technologies (Docker, Nacos) and mature middleware (Redis, MySQL cluster), providing a solid technical foundation for business growth. Whether it is daily operation or large-traffic promotions, the system can maintain stable and efficient service capabilities.

[0163] Refer to Figure 3 As shown, in this embodiment, an activity page acceleration method for an e-commerce mall visual website building system is provided, and the specific steps are as follows:

[0164] The front-end traffic limiting component is implemented using Alibaba Cloud Application High Availability Middleware, configuring a dynamic traffic threshold. When the concurrent requests exceed the threshold, it automatically triggers traffic limiting and returns a customized traffic limiting prompt page, including waiting time estimation and retry suggestions;

[0165] The traffic limiting strategy is dynamically adjusted based on the real-time system load;

[0166] The CDN static resource distribution network constructs a distributed content distribution system, realizes the local access of static resources through edge computing nodes, adopts an intelligent cache refresh strategy to ensure resource timeliness, and supports resource preloading and intelligent prefetching;

[0167] The multi-level cache system, the first-level cache component, uses the local server memory for storage. For the pages configured by CMS, first perform a first-level fixed-duration memory cache, which supports manual cleaning by the administrator and is applicable to the configuration data with high-frequency access;

[0168] The second-level cache component, the CMS page uses Redis for the second-level cache. After the page configuration item is modified, the second-level cache is automatically cleared. It is built based on a distributed Redis cluster, adopts the LRU (Least Recently Used) elimination strategy, and the cache invalidation is automatically triggered when the configuration changes, supporting batch operations and pipeline optimization;

[0169] Read the database. If neither the first-level cache nor the second-level cache exists, query the page configuration from the read database to implement database reading when the cache is not hit. Adopt a read-write separation architecture, configure a dedicated read database, and implement a query result cache backfill mechanism, supporting SQL optimization and index optimization.

[0170] Specifically, the working process of the multi-level cache system includes:

[0171] After receiving a user request, first check the first-level memory cache;

[0172] If the first-level cache is not hit, query the second-level Redis cache;

[0173] If the secondary cache still misses, obtain data from the read database;

[0174] After obtaining the data, backfill it into the secondary and primary caches as needed;

[0175] For configuration change operations, automatically trigger the invalidation of relevant caches.

[0176] Furthermore, the implementation method of the intelligent preheating system includes:

[0177] Analyze historical data to predict hot content;

[0178] Proactively load data into the cache before the access peak;

[0179] Establish a preheating task queue and a priority mechanism;

[0180] Implement monitoring of the preheating process and exception handling.

[0181] Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art and related fields without creative efforts shall fall within the scope of protection of the present invention. Structures, devices, and operation methods not specifically described and explained in the present invention, unless otherwise specified and limited, are implemented according to conventional means in the art.

Claims

1. An e-commerce mall visual website building system, characterized in that, It includes a visual editing module which includes a variety of pre-set widgets, and users can generate pages by dragging and combining them.

2. The e-commerce mall visual website building system according to claim 1, wherein The visual editing module supports multi-terminal adaptation for both PC and mobile terminals, and a set of configurations can be synchronously published to H5, mini-programs, and APPs.

3. The e-commerce mall visual website building system according to claim 1 or 2, characterized in that It also includes a high-concurrency optimization architecture which includes a front-end traffic limiting module, a multi-level caching module, a CDN static resource distribution module, and a hot preheating module.

4. The e-commerce mall visual website building system according to claim 3, characterized in that, The front-end traffic limiting module realizes request traffic limiting through the Sentinel middleware.

5. The e-commerce mall visual website building system according to claim 3, characterized in that The multi-level caching module includes a first-level cache and a second-level cache. Among them, the first-level cache is a memory fixed-duration cache, and the second-level cache is a Redis distributed cache; First, check the first-level memory cache; if the first-level cache is not hit, query the second-level Redis cache; if the second-level cache is still not hit, obtain data from the read database; after obtaining the data, backfill it to the second-level and first-level caches as needed; for configuration change operations, automatically trigger the invalidation of relevant caches.

6. The e-commerce mall visual website building system according to claim 3, characterized in that, The hot preheating module is used to pre-load page configurations and commodity prices into the cache before an event.

7. The e-commerce mall visual website building system according to claim 1, characterized in that, It also includes back-end technical components which include a service governance module, a distributed transaction module, and a data synchronization module.

8. The e-commerce mall visual website building system according to claim 7, characterized in that The service governance module realizes service registration and discovery based on Nacos, and performs traffic control through Sentinel.

9. The e-commerce mall visual website building system according to claim 7, wherein The distributed transaction module realizes cross-service transaction consistency through Seata.

10. The e-commerce mall visual website building system according to claim 7, characterized in that, The data synchronization module listens for MySQL changes through Canal and triggers cache updates.

Images