Java project source code - Spring cloud + vue + oAuth2.0 build enterprise level micro service project

preface:

spring cloud + vue + oAuth2.0 family bucket actual combat, front and rear end separated simulation mall, complete shopping process and back-end operation platform, which can quickly build enterprise level micro service projects. Support wechat login and other three-party login.

Spring Cloud combat project

Project introduction

Function point:
There are various monitoring indicators and operation and maintenance indicators for the simulation mall, the complete shopping process, the support of the back-end operation platform for the front-end business, and the operation and maintenance of the project. Technical points:
The core technology is realized in two buckets of springcloud+vue, which is taken from open source and used for open source. Therefore, open source can be used instead of charging framework. Only Alibaba cloud SMS service is charged in the overall technology stack, which is a forward-looking framework of java. It can solve the problems of micro service architecture for small and medium-sized enterprises and help enterprises build websites quickly. Due to the high server cost and the principle of minimizing development cost, this project is composed of 10 back-end projects and 3 front-end projects. It truly realizes the solution of stateless unified authority authentication based on RBAC, jwt and oauth2, realizes the unified management of exceptions and logs, and realizes the solution of MQ landing to ensure 100% arrival. Core framework: springcloud Edgware
Security framework: Spring Security Spring Cloud Oauth2
Distributed task scheduling: elastic job
Persistence layer framework: MyBatis, generic Mapper4, Mybatis_ PageHelper
Database connection pool: Alibaba Druid
Log management: Logback front-end framework: Vue and related components
Three party services: email service, Alibaba cloud SMS service, qiniu cloud file service, nail robot service, and Gaode map API

Description of platform directory structure

├─paascloud-master----------------------------Parent project, public dependency
│  │
│  ├─paascloud-eureka--------------------------Microservice registry
│  │
│  ├─paascloud-discovery-----------------------Microservice configuration center
│  │
│  ├─paascloud-monitor-------------------------Microservice monitoring center
│  │
│  ├─paascloud-zipkin--------------------------Microservice log collection center
│  │
│  ├─paascloud-gateway--------------------------Microservice gateway Center
│  │
│  ├─paascloud-provider
│  │  │
│  │  ├─paascloud-provider-mdc------------------Data service center
│  │  │
│  │  ├─paascloud-provider-omc------------------Order service center
│  │  │
│  │  ├─paascloud-provider-opc------------------Docking Service Center
│  │  │
│  │  ├─paascloud-provider-tpc------------------Mission Service Center
│  │  │
│  │  └─paascloud-provider-uac------------------User service center
│  │
│  ├─paascloud-provider-api
│  │  │
│  │  ├─paascloud-provider-mdc-api------------------Data service center API
│  │  │
│  │  ├─paascloud-provider-omc-api------------------Order service center API
│  │  │
│  │  ├─paascloud-provider-opc-api------------------Docking Service Center API
│  │  │
│  │  ├─paascloud-provider-tpc-api------------------Mission Service Center API
│  │  │
│  │  ├─paascloud-provider-sdk-api------------------Reliable message service API
│  │  │
│  │  └─paascloud-provider-uac-api------------------User service center API
│  │
│  ├─paascloud-common
│  │  │
│  │  ├─paascloud-common-base------------------public POJO Basic package
│  │  │
│  │  ├─paascloud-common-config------------------Common configuration package
│  │  │
│  │  ├─paascloud-common-core------------------Microservice core dependency package
│  │  │
│  │  ├─paascloud-common-util------------------Public Toolkit
│  │  │
│  │  ├─paascloud-common-zk------------------zookeeper to configure
│  │  │
│  │  ├─paascloud-security-app------------------Public stateless security authentication
│  │  │
│  │  ├─paascloud-security-core------------------Security service core package
│  │  │
│  │  └─paascloud-security-feign------------------be based on auth2 of feign to configure
│  │
│  ├─paascloud-generator
│  │  │
│  │  ├─paascloud-generator-mdc------------------Data service center Mybatis Generator
│  │  │
│  │  ├─paascloud-generator-omc------------------Data service center Mybatis Generator
│  │  │
│  │  ├─paascloud-generator-opc------------------Data service center Mybatis Generator
│  │  │
│  │  ├─paascloud-generator-tpc------------------Data service center Mybatis Generator
│  │  │
│  │  └─paascloud-generator-uac------------------Data service center Mybatis Generator

Special instructions

Here is an explanation. Since the splitting of microservices is subject to the server, I have merged microservices here, such as OAuth2 The authentication service center and the user center are merged,
Unified one service The service center and user authentication center are merged, and the payment center and order center are merged. In fact, this is also a last resort,
Only the business micro service centers are merged, and the registration center, monitoring center and service discovery center in the architecture are not merged.