---
title: Architecture Instructions（架构说明） (1)
description: 文本抽取：知识库/02-商城交易私域场景/ECshopex开源资料/Architecture Instructions（架构说明） (1)
updated: 2026-11-04
tags: [原始文档, 抽取, 知识库]
source: 知识库/02-商城交易私域场景/ECshopex开源资料/Architecture Instructions（架构说明） (1)
source_type: txt
source_hash: 6707519c5fc6
extracted_at: 2026-11-04
quality: ok
---

---
source: 知识库/02-商城交易私域场景/ECshopex开源资料/Architecture Instructions（架构说明） (1).docx
type: docx
size_kb: 15
category: 02-商城交易私域场景
quality: ok
---

## Architecture Instructions

Software Architecture

Back-end Development Language: PHP 7.2

Back-end Framework: use Lumen Open Source Framework to develop, introduce dingo as interface management, and replace the System ORM by adopting Doctrine ORM, which is more conform in large-scale projects.

Front-end Development Language: HTML5/CSS3/ES6/Mini Program Framework

Front-end Framework: VueJS, Taro, Wepy

Database: Support MySQL databases

Queue: Support Redis/RabbitMQ/database and other schemes.  Redis is used by default

Cache: Support Redis/filesystem/memcached. Redis is used by default

CDN/OSS: Support Alibaba Cloud/Qiniu Cloud

Search: ES

Log Collection: ELK/Sentry

Data Processing Capability

Support MySQL read-write separation mode, support Alibaba Cloud PolarDB.

In a 5-machine cluster, a comprehensive scenario supports 2000 concurrency per second, and the capacity is expanded according to actual business requirements.

Without optimization, the database is configured with 4 cores and 8G, and individual orders are stress tested at 27 orders per second, which can be optimized by adjusting the web machine, cache, and database configuration according to the actual business.

The use of a multi-level caching mechanism can effectively ensure that the API response time is within 2 seconds.

The system has authority control according to terminals, shops, stores, etc.

Stability

The system supports cluster mode deployment, which can be deployed according to different roles such as web/schedule/worker.

Supports Alibaba Cloud K8S deployment, and can realize automatic expansion of POD through HPA.

Using event mechanism, time-consuming business logic can be processed asynchronously to ensure real-time business stability.

Using a multi-level caching mechanism, nginx+memcache/php+redis mode. When the redis database is down, it can be replaced by nginx cache to ensure high system availability.

Continuous Integration

The system adopts PHP development and supports secondary development.

In ONex, except for the authorization part, the other parts are all source code.

With a complete development environment (docker-compose) and test environment build scripts, engineer can quickly build the environment.

Adopt a continuous integration solution based on GitLab-CI/K8S/Helm/Helmfile