How 201206030/novel works
Project type and purpose
• This is a full-stack, front-back separated monolithic Java system (“novel”) for a learning-oriented novel portal.
• It provides three logical “sub-systems”:
• Novel Portal (front-end for readers)
• Author Backend (management for writers)
• Platform/Admin Backend (management for admins)
• It uses Spring Boot 3 + MyBatis-Plus + Spring AI on the back end, Vue 3 + Element-Plus on the front end, and integrates MySQL (with ShardingSphere), Redis/Caffeine caching, RabbitMQ messaging, Elasticsearch search, XXL-JOB scheduling, JWT auth, AOP, interceptors/filters, plus monitoring and CI/CD tools.
File structure
• src/main/java/io/github/xxyopen/novel
• controller (HTTP API endpoints, separated into front, author, admin… )
• service (business logic interfaces) & service/impl
• manager (cross-DAO orchestration, third-party wrappers, caching, messaging)
• dao (MyBatis mappers + entity classes)
• dto (request/response objects)
• core (cross-cutting → annotation, aspect, auth, config, filter, interceptor, json, task, wrapper, common)
• src/main/resources
• application.yml (feature toggles for ES, RabbitMQ, XXL-JOB, ShardingSphere)
• mapper XMLs for MyBatis
• shardingsphere-jdbc.yml, logback, swagger metadata
• config classes wire up: Spring Boot, security (JWT), CORS, AOP, caching, Redis, RabbitMQ, ES, ShardingSphere, OpenAPI, XXL-JOB.
README
• Confirms tech stack and feature list: novel recommendation, search, ranking, reading, commenting, subscription/payments, news, user/author/admin centers.
• Mentions optional components (Elasticsearch, RabbitMQ, XXL-JOB) toggled via config.
• Sketches high-level package structure.