How wnhyang/coolguard works
Project type and purpose
• This is a modular, multi-module backend platform implementing a rules-based risk-control decision engine.
• Core modules:
• coolguard-system – user/auth management and API endpoints
• coolguard-admin – administrative console service for configuring rules/strategies
• coolguard-decision – the rule-engine microservice handling sync/async decisions
• coolguard-monitor – metrics/log collection service
• coolguard-common – shared library of utilities, contexts, error handling, MyBatis/Redis/Kafka configs
• It uses Spring Boot 3, MyBatis-Plus, Redis, Kafka, Elasticsearch, MySQL, LiteFlow, SaToken, MapStruct.
File structure
• Top-level pom.xml orchestrates submodules via Maven.
• “coolguard-dependencies” defines dependency management (BOM).
• Each submodule is a Spring Boot application with its own Dockerfile (admin) or SpringBootApplication entrypoint.
• “shell/docker” and “sql” contain deployment scripts and initial DB schemas.
• Patterns: layered MVC in each service (controller → service → mapper → entity), async tasks (LiteFlow), Kafka consumer/producer, common configs.
README for insights
• Describes rule-engine features (metrics, rules, strategies, versioning, event center, exemptions, integrations, monitoring).
• Lists tech stack and middleware: MySQL, Redis, Kafka, Elasticsearch.