Building a County Cultural Heritage & Creative Marketplace with Spring Boot and Vue.js
This article outlines the design and implementation of a three‑day graduation demo system that digitizes county cultural heritage, offers searchable displays, a creative product marketplace, user authentication, and monitoring, using a Spring Boot back‑end, Vue.js front‑end, MySQL, Redis, Docker, and CI/CD pipelines.
Background
The project was commissioned as a small graduation demo system with a three‑day timeline, aiming to explore a low‑cost solution for showcasing county cultural heritage and supporting creative product transactions.
Requirement Description
Increasing demand for protecting and revitalizing county cultural heritage is limited by offline displays and fragmented creative distribution channels. The system must therefore provide:
User registration and secure login for visitors and creators.
Category‑based display of heritage items (e.g., ancient architecture, intangible cultural skills).
Keyword search and advanced filtering for heritage information.
Listing of creative products with category view, price sorting, and sales ranking.
Publication of popular‑science articles on heritage protection and activation.
Merchant shop management, including product publishing, inventory updates, and status control.
User reviews and rating for heritage items and creative products.
Personal center for order management, favorites, and account settings.
Technical Architecture Design
The system follows a front‑end/back‑end separation. The front‑end is built with Vue.js to deliver a responsive UI, while the back‑end uses Spring Boot to expose RESTful APIs. Data is stored in a relational MySQL database; Redis caches high‑frequency data. Object storage (OSS) holds multimedia resources, though for the demo it can be replaced by local file storage, and Redis can be omitted to reduce overhead.
User Authentication Module
Stateless authentication is implemented with JWT (JSON Web Token). Spring Security handles password hashing using BCrypt, and RBAC (role‑based access control) restricts sensitive endpoints. Encryption steps can be simplified for the demo.
Monitoring and Deployment
Prometheus and Grafana constitute the monitoring platform, while ELK aggregates and analyses system logs. Docker containerizes the services, Jenkins provides a CI/CD pipeline, and a blue‑green deployment strategy ensures seamless upgrades. Critical business data is backed up daily to object storage.
Functional Pages
User Side
Images illustrate the user interface for registration, heritage browsing, product listings, article reading, and personal center features.
Admin Side
Images show the administrative dashboard for managing heritage data, product inventory, shop information, and system settings.
The system integrates digitized county cultural resources into a complete ecosystem that connects cultural dissemination with industrial conversion, offering a reusable framework for similar heritage platforms.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Coder Trainee
Experienced in Java and Python, we share and learn together. For submissions or collaborations, DM us.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
