How flysail/mall works
Main Components Overview
Frontend Layer:
• mall-admin-web (Vue.js based admin interface)
• mall-app-web (Customer-facing web interface)
Backend Services Layer:
• mall-admin (Admin management APIs)
• mall-portal (Customer-facing APIs)
• mall-search (Elasticsearch-based product search)
• mall-security (Security and authentication)
• mall-common (Shared utilities)
• mall-mbg (MyBatis code generation)
Infrastructure Layer:
• MySQL (Primary database)
• Redis (Caching)
• Elasticsearch (Search engine)
• RabbitMQ (Message queue)
• MongoDB (NoSQL storage)
• MinIO/OSS (Object storage)
Component Relationships
a) Frontend-Backend Integration:
• mall-admin-web → mall-admin (REST APIs)
• mall-app-web → mall-portal (REST APIs)
b) Service Dependencies:
• mall-admin → mall-security (Authentication)
• mall-portal → mall-security (Authentication)
• mall-admin → mall-common (Shared utilities)
• mall-portal → mall-common (Shared utilities)
• All services → mall-mbg (Database access)
c) Infrastructure Integration:
• Services → MySQL (Data persistence)
• Services → Redis (Caching)
• mall-search → Elasticsearch (Product search)
• mall-portal → RabbitMQ (Order processing queue)
Key Architectural Patterns
Patterns with distinct sections:
a) Security Layer:
• JWT Authentication
• Dynamic Security
• Role-based Access Control
b) Data Access Layer:
• MyBatis ORM
• Generated Mappers
• DAO Pattern
c) Service Layer:
• Business Logic
• Service Implementations
• DTOs
Cross-Cutting Concerns
As vertical layers:
• Logging (ELK Stack)
• Monitoring
• Caching
• Security
• Docker Containerization
Additional Elements
Symbols for:
• Load balancers
• API gateways
• Cache layers
• Message queues
• Database clusters
Annotations for:
• Technology versions
• Communication protocols
• Security boundaries
• Scalability points
Deployment View
A separate section showing:
• Docker containers
• Nginx reverse proxy
• Service discovery
• Load balancing
Remember to show both synchronous (REST) and asynchronous (Message Queue) communication patterns, and indicate where caching and security boundaries exist.