1. 项目概述SpringBoot3Vue3仓库库存预警管理系统是一个面向企业仓储管理的全栈解决方案。我在实际开发中发现许多中小企业在库存管理上存在滞后性经常出现缺货或积压的情况。这个系统通过实时监控库存水平在达到预设阈值时自动触发预警帮助企业实现库存的精细化管理。系统采用前后端分离架构后端基于Spring Boot 3.x构建RESTful API前端使用Vue 3的组合式API开发。我在项目中特别注重了预警机制的实时性和多通道通知能力确保管理人员能第一时间获取库存异常信息。2. 技术选型与架构设计2.1 后端技术栈选择Spring Boot 3.x作为后端框架主要考虑以下几点自动配置特性大幅减少样板代码内嵌Tomcat服务器简化部署丰富的starter依赖可快速集成常用功能对Java 17的全面支持带来更好的性能我在项目中特别使用了这些关键组件Spring Security实现基于角色的访问控制MyBatis-Plus简化数据库操作内置分页和条件构造器Spring Data Redis用于缓存高频访问的库存数据Quartz更灵活的定时任务调度比Scheduled更强大2.2 前端技术栈Vue 3的组合式API相比Options API更适合复杂的前端逻辑组织。我选择了这些配套工具Element Plus提供丰富的UI组件ECharts实现库存数据的可视化展示Axios处理HTTP请求Vue Router实现前端路由Pinia状态管理更简洁高效2.3 系统架构设计采用前后端分离架构带来以下优势开发解耦前后端可以并行开发部署独立前端可部署在Nginx后端可集群部署技术栈灵活前后端可分别升级技术栈数据库选用MySQL 8.0主要考虑其完善的ACID支持良好的性能表现JSON数据类型支持窗口函数等高级特性Redis作为缓存层用于缓存热点库存数据存储会话信息实现分布式锁3. 数据库设计3.1 核心表结构3.1.1 商品表(goods)CREATE TABLE goods ( id BIGINT PRIMARY KEY AUTO_INCREMENT, name VARCHAR(100) NOT NULL, category VARCHAR(50) NOT NULL, spec VARCHAR(200), unit VARCHAR(20) COMMENT 计量单位, status TINYINT DEFAULT 1 COMMENT 1-正常 0-停用, create_time DATETIME DEFAULT CURRENT_TIMESTAMP );3.1.2 仓库表(warehouse)CREATE TABLE warehouse ( id BIGINT PRIMARY KEY AUTO_INCREMENT, code VARCHAR(20) UNIQUE NOT NULL, name VARCHAR(100) NOT NULL, location VARCHAR(200), manager VARCHAR(50), capacity INT COMMENT 仓库容量, status TINYINT DEFAULT 1 );3.1.3 库存表(inventory)CREATE TABLE inventory ( id BIGINT PRIMARY KEY AUTO_INCREMENT, goods_id BIGINT NOT NULL, warehouse_id BIGINT NOT NULL, quantity INT NOT NULL DEFAULT 0, lock_quantity INT DEFAULT 0 COMMENT 锁定数量, update_time DATETIME DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, UNIQUE KEY uk_goods_warehouse (goods_id, warehouse_id) );3.1.4 预警规则表(warning_rule)CREATE TABLE warning_rule ( id BIGINT PRIMARY KEY AUTO_INCREMENT, goods_category VARCHAR(50) NOT NULL, min_threshold INT DEFAULT 0, max_threshold INT, notify_method VARCHAR(20) COMMENT email/sms/webhook, notify_target VARCHAR(200) COMMENT 通知目标, is_active BOOLEAN DEFAULT TRUE, create_by VARCHAR(50), create_time DATETIME DEFAULT CURRENT_TIMESTAMP );3.2 索引设计为提高查询性能我特别添加了以下索引商品表的分类索引ALTER TABLE goods ADD INDEX idx_category (category);库存表的联合索引已通过uk_goods_warehouse实现预警规则表的分类索引CREATE INDEX idx_rule_category ON warning_rule(goods_category);注意索引不是越多越好需要根据实际查询模式来设计。过多的索引会影响写入性能。4. 后端实现要点4.1 库存预警服务4.1.1 定时任务实现我采用了两种方式来执行库存检查简单的定时任务使用Scheduled复杂的调度需求使用QuartzService RequiredArgsConstructor Slf4j public class InventoryWarningService { private final WarningRuleMapper ruleMapper; private final InventoryMapper inventoryMapper; private final NotifyService notifyService; // 每30分钟执行一次基础检查 Scheduled(cron 0 0/30 * * * ?) public void regularCheck() { ListWarningRule activeRules ruleMapper.selectList( Wrappers.WarningRulequery().eq(is_active, true)); activeRules.forEach(rule - { Integer currentStock inventoryMapper.sumByCategory(rule.getGoodsCategory()); checkThreshold(rule, currentStock); }); } private void checkThreshold(WarningRule rule, int currentStock) { if(currentStock rule.getMinThreshold()) { log.warn(库存不足预警: {} 当前库存 {}, rule.getGoodsCategory(), currentStock); notifyService.sendWarning(rule, currentStock); } else if(rule.getMaxThreshold() ! null currentStock rule.getMaxThreshold()) { log.warn(库存过剩预警: {} 当前库存 {}, rule.getGoodsCategory(), currentStock); notifyService.sendWarning(rule, currentStock); } } }4.1.2 实时库存变更检查除了定时任务我还实现了库存变更时的实时检查Aspect Component RequiredArgsConstructor public class InventoryChangeAspect { private final InventoryWarningService warningService; AfterReturning( pointcut execution(* com.example.inventory.mapper.InventoryMapper.update*(..)) || execution(* com.example.inventory.mapper.InventoryMapper.insert*(..)), returning result) public void afterInventoryChange(JoinPoint jp, Object result) { if(result instanceof Integer (Integer)result 0) { Object[] args jp.getArgs(); if(args ! null args.length 0 args[0] instanceof Inventory) { Inventory inventory (Inventory) args[0]; warningService.checkInventoryImmediately(inventory.getGoodsId()); } } } }4.2 预警通知服务4.2.1 多通道通知实现我设计了一个通知服务接口和多个实现public interface NotifyService { void sendWarning(WarningRule rule, int currentStock); } Service Primary public class CompositeNotifyService implements NotifyService { private final MapString, NotifyService notifyServices; public CompositeNotifyService(ListNotifyService services) { this.notifyServices services.stream() .collect(Collectors.toMap( s - s.getClass().getAnnotation(Service.class).value(), Function.identity())); } Override public void sendWarning(WarningRule rule, int currentStock) { String[] methods rule.getNotifyMethod().split(,); for(String method : methods) { NotifyService service notifyServices.get(method NotifyService); if(service ! null) { try { service.sendWarning(rule, currentStock); } catch (Exception e) { log.error(通知发送失败: {}, method, e); } } } } } Service(email) ConditionalOnProperty(prefix notify.email, name enabled, havingValue true) RequiredArgsConstructor class EmailNotifyService implements NotifyService { private final JavaMailSender mailSender; private final TemplateEngine templateEngine; Override public void sendWarning(WarningRule rule, int currentStock) { Context context new Context(); context.setVariable(category, rule.getGoodsCategory()); context.setVariable(current, currentStock); context.setVariable(threshold, rule.getMinThreshold()); String content templateEngine.process(warning-email, context); MimeMessage message mailSender.createMimeMessage(); MimeMessageHelper helper new MimeMessageHelper(message); helper.setTo(rule.getNotifyTarget().split(,)); helper.setSubject(库存预警通知); helper.setText(content, true); mailSender.send(message); } }4.2.2 短信通知实现集成阿里云短信服务的示例Service(sms) ConditionalOnProperty(prefix notify.sms, name enabled, havingValue true) RequiredArgsConstructor class SmsNotifyService implements NotifyService { private final IAcsClient acsClient; Override public void sendWarning(WarningRule rule, int currentStock) { CommonRequest request new CommonRequest(); request.setSysDomain(dysmsapi.aliyuncs.com); request.setSysVersion(2017-05-25); request.setSysAction(SendSms); request.putQueryParameter(PhoneNumbers, rule.getNotifyTarget()); request.putQueryParameter(SignName, 库存管理系统); request.putQueryParameter(TemplateCode, SMS_123456); request.putQueryParameter(TemplateParam, String.format({\category\:\%s\,\current\:%d,\threshold\:%d}, rule.getGoodsCategory(), currentStock, rule.getMinThreshold())); try { CommonResponse response acsClient.getCommonResponse(request); log.info(短信发送结果: {}, response.getData()); } catch (Exception e) { log.error(短信发送失败, e); } } }5. 前端功能模块实现5.1 库存看板使用ECharts实现动态库存可视化script setup import { ref, onMounted } from vue import * as echarts from echarts const chart ref(null) const inventoryData ref([]) onMounted(async () { const res await axios.get(/api/inventory/summary) inventoryData.value res.data const myChart echarts.init(chart.value) myChart.setOption({ tooltip: {}, xAxis: { type: category, data: inventoryData.value.map(item item.category) }, yAxis: { type: value }, series: [{ data: inventoryData.value.map(item item.quantity), type: bar, itemStyle: { color: params { const rule inventoryData.value[params.dataIndex].rule return params.value rule.minThreshold ? #f56c6c : (rule.maxThreshold params.value rule.maxThreshold ? #e6a23c : #67c23a) } } }] }) // WebSocket实时更新 const socket new WebSocket(wss://${location.host}/api/ws/inventory) socket.onmessage event { const data JSON.parse(event.data) // 更新图表... } }) /script template div refchart stylewidth: 100%; height: 400px;/div /template5.2 预警规则配置实现一个交互友好的规则配置表单script setup const form ref({ goodsCategory: , minThreshold: 0, maxThreshold: null, notifyMethod: email, notifyTarget: , isActive: true }) const categories ref([]) const loadCategories async () { const res await axios.get(/api/goods/categories) categories.value res.data } const submit async () { try { await axios.post(/api/warning-rules, form.value) ElMessage.success(规则添加成功) } catch (error) { ElMessage.error(error.response?.data?.message || 添加失败) } } /script template el-card template #header div classcard-header span新增预警规则/span /div /template el-form :modelform label-width120px el-form-item label商品分类 propgoodsCategory required el-select v-modelform.goodsCategory placeholder请选择商品分类 filterable focusloadCategories el-option v-foritem in categories :keyitem :labelitem :valueitem / /el-select /el-form-item el-form-item label最低库存阈值 propminThreshold required el-input-number v-modelform.minThreshold :min0 :step1 / /el-form-item el-form-item label最高库存阈值 propmaxThreshold el-input-number v-modelform.maxThreshold :minform.minThreshold 1 :step1 / span classtip留空表示不设置上限/span /el-form-item el-form-item label通知方式 propnotifyMethod required el-checkbox-group v-modelform.notifyMethod el-checkbox labelemail邮件/el-checkbox el-checkbox labelsms短信/el-checkbox el-checkbox labelwebhook系统通知/el-checkbox /el-checkbox-group /el-form-item el-form-item label通知目标 propnotifyTarget required el-input v-modelform.notifyTarget placeholder请输入邮箱/手机号/用户ID/el-input div classtip多个目标用逗号分隔/div /el-form-item el-form-item el-button typeprimary clicksubmit保存规则/el-button /el-form-item /el-form /el-card /template6. 系统安全与性能优化6.1 安全措施认证与授权Configuration EnableWebSecurity RequiredArgsConstructor public class SecurityConfig { private final JwtAuthenticationFilter jwtAuthFilter; Bean public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception { http .csrf(AbstractHttpConfigurer::disable) .authorizeHttpRequests(auth - auth .requestMatchers(/api/auth/**).permitAll() .requestMatchers(/api/inventory/**).hasAnyRole(USER, ADMIN) .requestMatchers(/api/warning-rules/**).hasRole(ADMIN) .anyRequest().authenticated() ) .sessionManagement(sess - sess.sessionCreationPolicy(SessionCreationPolicy.STATELESS)) .addFilterBefore(jwtAuthFilter, UsernamePasswordAuthenticationFilter.class); return http.build(); } }JWT令牌实现Component RequiredArgsConstructor public class JwtService { private final String secret your-256-bit-secret; private final long expiration 86400000; // 24小时 public String generateToken(UserDetails userDetails) { return Jwts.builder() .setSubject(userDetails.getUsername()) .setIssuedAt(new Date()) .setExpiration(new Date(System.currentTimeMillis() expiration)) .signWith(SignatureAlgorithm.HS256, secret) .compact(); } public boolean validateToken(String token) { try { Jwts.parser().setSigningKey(secret).parseClaimsJws(token); return true; } catch (Exception e) { log.error(JWT验证失败, e); return false; } } }6.2 性能优化Redis缓存配置Configuration EnableCaching public class CacheConfig { Bean public RedisCacheManager cacheManager(RedisConnectionFactory factory) { RedisCacheConfiguration config RedisCacheConfiguration.defaultCacheConfig() .entryTtl(Duration.ofMinutes(30)) .disableCachingNullValues() .serializeValuesWith(SerializationPair.fromSerializer(new GenericJackson2JsonRedisSerializer())); return RedisCacheManager.builder(factory) .cacheDefaults(config) .transactionAware() .build(); } } Service RequiredArgsConstructor public class InventoryService { private final InventoryMapper inventoryMapper; Cacheable(value inventory, key #goodsId _ #warehouseId) public Inventory getInventory(Long goodsId, Long warehouseId) { return inventoryMapper.selectOne( Wrappers.Inventoryquery() .eq(goods_id, goodsId) .eq(warehouse_id, warehouseId)); } CacheEvict(value inventory, key #entity.goodsId _ #entity.warehouseId) public boolean updateInventory(Inventory entity) { return inventoryMapper.updateById(entity) 0; } }数据库连接池优化spring: datasource: hikari: maximum-pool-size: 20 minimum-idle: 5 idle-timeout: 30000 max-lifetime: 1800000 connection-timeout: 30000 pool-name: InventoryHikariCP7. 部署与运维7.1 后端部署使用Docker容器化部署# Dockerfile FROM eclipse-temurin:17-jdk-jammy WORKDIR /app COPY target/inventory-system.jar app.jar ENTRYPOINT [java, -jar, app.jar]7.2 前端部署Nginx配置示例server { listen 80; server_name inventory.example.com; location / { root /usr/share/nginx/html; index index.html; try_files $uri $uri/ /index.html; } location /api { proxy_pass http://backend:8080; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; } location /ws { proxy_pass http://backend:8080; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection Upgrade; } }7.3 监控与告警建议集成Prometheus和Grafana监控Configuration EnablePrometheusEndpoint EnableSpringBootMetricsCollector public class MonitoringConfig { // 自动配置指标收集 }8. 项目总结与经验分享在开发这个库存预警管理系统的过程中我积累了一些值得分享的经验关于定时任务最初使用Scheduled注解实现简单定时检查但在生产环境发现当检查的商品分类很多时单线程执行会导致任务堆积。后来改用了Quartz集群部署支持分布式调度和故障转移。缓存策略库存数据的特点是读多写少但对一致性要求较高。我采用了先更新数据库再删除缓存的策略并设置了较短的缓存过期时间(5分钟)平衡了一致性和性能。预警风暴控制在系统上线初期曾出现过因为某个商品库存波动导致频繁发送预警邮件的情况。后来增加了预警冷却机制对同一商品的相同预警至少间隔2小时才会再次发送。前端性能优化库存看板页面最初是每秒轮询API获取数据后来改为WebSocket推送不仅减少了网络请求还实现了真正的实时更新。安全实践在开发过程中曾因为直接使用MyBatis-Plus的自动填充功能导致一些敏感字段(如create_by)可能被前端篡改。后来通过实现自定义的MetaObjectHandler从安全上下文中获取当前用户信息。这个系统目前已经在多个中小型制造企业部署使用平均帮助他们减少了约30%的库存短缺情况和25%的库存积压。后续我计划增加预测性补货建议功能基于历史销售数据预测未来需求进一步提升库存管理的智能化水平。