How crmeb/crmeb_java works
Project Type and Purpose
• This is a full-stack, modular e-commerce platform (“CRMEB Java版”) comprising:
• A PC management console (“admin”) built with Vue + Element UI
• A mobile storefront (“app”) built with Uni-app (H5, WeChat mini-program, etc.)
• A Java backend split into multiple modules:
– crmeb-admin (admin REST API)
– crmeb-front (customer-facing REST API)
– crmeb-service (business-logic & data-access services)
– crmeb-common (shared models, utils, configs)
– crmeb-image (static image repo)
• Data storage: MySQL + Redis + external services (OSS/Qiniu, SMS provider, WeChat).
• Purpose: Provide a configurable, extensible online mall with features like orders, products, marketing (bargain, seckill, coupon), role-based security, report/export, and a drag-and-drop form generator.
File Structure Analysis
• Top-level directories:
• admin/ — Web admin front-end project
• app/ — Mobile storefront front-end project
• crmeb/ — Backend Maven multi-module: admin/front/service/common/image
• 接口文档/ — Generated Swagger API docs
• Backend modules follow layered MVC:
• controller → service → dao (MyBatis mappers) → database
• Shared code in crmeb-common (models, constants, utils, Redis config, token)
• crmeb-service holds business services and MyBatis XML mappers under resources/mapper
• Config files & scripts: Spring Boot YAMLs, Maven POMs, shell start/stop scripts.
Key Insights from README
• Tech stack: Spring Boot 2.2.6, MyBatis-Plus, Redis, Vue2, ElementUI, Uni-app
• Clear separation: “admin” (PC), “app” (mobile), “crmeb” (API)
• Features: RESTful APIs, Redis queues, Spring Security with role/permission control, ECharts for analytics, drag-drop form generator.
a. Main Components
• Frontends:
• Admin UI (Vue+Element)
• Mobile UI (Uni-app)
• Backend Services:
• Admin API (crmeb-admin module)
• Front API (crmeb-front module)
• Business Layer:
• Service layer (crmeb-service)
• Data Access layer (MyBatis DAOs & mappers)
• Shared Module:
• Common models/configs (crmeb-common)
• Persistence:
• MySQL
• Redis (cache, queues, session, rate-limit)
• External Services:
• Object Storage (OSS/Qiniu)
• SMS gateway
• WeChat API (push messages, OAuth)
• Static Resources:
• crmeb-image repository
b. Relationships & Interactions
• Admin UI & Mobile UI → via HTTP(S) → Admin API & Front API
• APIs delegate to Service layer → DAOs → MySQL
• Services push tasks to Redis queues → background TaskExecutor
• Common utilities (authentication, JWT filter, CORS, Swagger) applied across API modules
• External calls for file uploads, SMS, payment, WeChat through REST templates
c. Architectural Patterns & Principles
• Layered MVC: Controllers → Services → DAOs
• Modularization: separate API for admin vs. front
• Shared library for cross-cutting concerns (crmeb-common)
• Asynchronous tasks (Spring @Scheduled & Redis queue)
• Role-based access control (Spring Security)
d. Key Technologies
• Java: Spring Boot, MyBatis-Plus, Redis, Maven
• Frontend: Vue2, Element UI, Uni-app
• Build/Deploy: NPM, Node, shell scripts
• Data: MySQL, Redis
• Cloud: OSS/Qiniu, WeChat SDK