How jasonwang82/mall works
Project type and purpose
• This is a full-stack, modular e-commerce system (“mall”) implemented as a multi-module Maven project.
• It consists of backend micro-services (mall-admin, mall-portal, mall-search, plus supporting modules mall-common, mall-security, mall-mbg) and two separate frontend applications (mall-admin-web for the back office and mall-app-web for the mobile/portal).
• The goal is to provide typical e-commerce workflows: administration, storefront browsing, ordering, search, messaging, caching, logging and analytics.
File structure
• Top-level modules:
• mall-common: shared utilities and API result objects
• mall-mbg: MyBatis code generator
• mall-security: Spring Security extension library
• mall-admin: back-office REST API
• mall-portal: storefront REST API
• mall-search: Elasticsearch-based search service
• mall-demo: test/demo code
• document/docker and sh scripts for Docker Compose and container orchestration.
• document/elk shows Logstash config for centralized logging.
• External resources: SQL schema, Postman collections, PDM and mind-map designs.
Insights from README
• System is Spring Boot + MyBatis; uses Docker for containerization.
• Core infrastructure: MySQL, Redis, RabbitMQ, Elasticsearch, MongoDB, MinIO/OSS, Nginx, ELK stack.
• Frontend frameworks: Vue.js (admin & portal), uni-app for mobile.
• Typical deployment via Nginx (static asset hosting and reverse proxy), Docker Compose for services.
Diagramming recommendations
• Client (blue),
• Edge/router (orange),
• Services (green),
• Data stores (red),
• Messaging (purple),
• Logging/monitoring (grey).
• User → Nginx → Service
• Service → Data store
• Service ↔ RabbitMQ → Service
• Service → Logstash → Elasticsearch → Kibana