Springcloud-based MicroServices architecture combat case

QuickStart

Based on the implementation of the Springcloud architecture system, the simple shopping process is implemented to meet the basic functions: registration, Login, product list display, product details display, order creation, detail view, order payment, inventory update and so on. The current iteration of the second version, service registration, discovery, monitoring and distributed configuration, and other basic services have been completed, the shopping process can be completed by swagger the increased API sequence. Follow-up will be continuously updated in maintenance.

Source Address: Https://github.com/backkoms/simplemall

Each business service uses a separate MySQL database and initially considers the following components:

2. Service registration, Discovery: Eureka

4. Configuration management: Spring config, spring security

6. Cluster fault tolerance: Hystrix (to be implemented)

8. API Gateway: Zuul (to be implemented)

10. Service Load: Feign+ribbon

12. API Document output: Swagger2

14. Code Simplification: Lombok

16. Message Queuing: RABBITMQ

18. Distributed locks: Redis (to be implemented)

20. Link Tracking: Spring cloud Sletuh->zipkin

22. Security certification: OAUTH2/JWT (to be implemented)

24. Service Monitoring: Spring-boot-admin

introduction of each module /thead>

module name	port	introduction
admin-server	service monitoring center, monitoring all service modules
conf-server	distributed configuration Center, Combine SPRING-SECURITY/RABBITMQ with
eureka-server	service registry, providing service registration, discovery capabilities
sleuth-server	A distributed tracking solution implemented by Springcloud, compatible with Zipkin
zuul-server	api Gateway module
account-service	User services, provide registration, login, address and other services
product-service	goods service, offering list of goods, details, Services such as inventory updates
payment-service	payment services, payment records
order-service	order service, providing order creation, details, status changes
msg-service	message processing service
Front-app	8088	Front-end services, combined with SWAGGER2 to provide API management

Get started quickly

• 1. Start Admin-server,eureka-server,conf-server three basic services first

• 2. Start Payment/order/product/account basic business service in turn

• 3, finally start the Front-app service, open the browser, enter the http://localhost:8088/swagger-ui.html, according to the process API can be used in turn function

• 4, follow-up time to provide the page, based on Vue2+bootstrap, the process of string up

Release Versionv2.1

Release date:2017-08-29

1, the introduction of SWAGGER2, complete API Interface document management to complete the overall business data flow2, through the API interface to complete the overall business data3, based on the introduction of Spring-cloud-config Configuration Center, combined with security to enhance safety configuration, while introducing BUS-AMQP (RABBITMQ) Efficient update configuration content [Configuration center data combined with SC-CLOUD-REPO engineering use] 4, the introduction of feign, to meet the client call service side service5, the introduction of ribbon, can meet the client load balancing call back-end servicesv1.0

Release DATE:2017-08-17

1, the completion of basic services and business sub-module services, Business sub-module can operate normally2, complete the operation of Springbootadmin business module monitoring, and Eureka service operation, to meet the basic services of the business registration, Discovery function3, through the Front-app end, with the help of feign components to initiate a simple test run login/signup and other functions. The next version, based on this version, will continue to improve the complete shopping implementation, including simple pages, API management/invocation and so on.

Springcloud-based MicroServices architecture combat case