Introduction
SpringBlade is a comprehensive project in which the SpringCloud distributed microservice architecture and the SpringBoot monolithic microservice architecture coexist, upgraded and optimized from commercial-level projects. It uses Java8 API to reconstruct the business code and fully complies with the Alibaba coding standards. It adopts core technologies such as Spring Boot 2, Spring Cloud Hoxton, Mybatis, and provides two front-end frameworks based on React and Vue to quickly build an enterprise-level SaaS multi-tenant microservice platform.
Features:
1. Adopt the front-end and back-end separation model, and the front-end open source two frameworks: Sword (based on React, Ant Design), Saber (based on Vue, Element-UI)
2. The backend adopts SpringCloud family bucket, and at the same time, it has made a high degree of packaging of its basic components, and a separate open source framework: BladeTool
3. BladeTool has been pushed to the Maven central repository and can be imported directly, which reduces the bloat of the project and can also focus more on business development
4. Integrate Sentinel to protect the stability of the service from multiple dimensions such as flow control, fuse degradation, and system load.
5. Nacos is selected for registration center and configuration center to strengthen the linkage between various modules while slimming the project.
6. Use Traefik for reverse proxy, monitor background changes and automatically apply new configuration files.
7. Minimalism encapsulates the multi-tenant bottom layer, and uses less code in exchange for a more scalable SaaS multi-tenant system.
8. Learning from OAuth2, a multi-terminal authentication system is implemented, and the token permissions of the control subsystems are isolated from each other.
9. Learn from Security, encapsulate the Secure module, and use JWT for Token authentication, which can expand and integrate Redis and other fine-grained control schemes.
10. After two years of stable production, it has experienced the technical architecture from Camden -> Hoxton and the deployment architecture from fat jar -> docker -> k8s + jenkins
11. Project subcontracting is clear, and the development mode of microservices is standardized, so that the division of labor between packages is clear.
Download link
http://www.bytepan.com/Yuc3u4kEcPr
image
