Some recommended plans for Spring Cloud development

1. Provide a unified parent Pom dependency

Role: Unified version with the introduction of necessary dependencies

2, provide a template model.

Role: Developers do not have to relate to specific base startup items

3. Provide a unified base configuration model

Role: Developers are not too concerned with the necessary configuration

4. Provide testing and Production configuration Center

Role: Developers do not have to consider formal and test environment switching issues. You can also make dynamic configuration changes. You will cry when you have a service that deploys n containers that do not apply to Docker.

5. Provide an instance of introducing a database and referencing multiple databases

Recommended unified use of Spring Data Jap
Reason:

Only need to introduce the corresponding database driver, the same syntax. Simplifies development and facilitates unified management. Follow-up maintenance, etc.

6. Unified use of feign to make calls between services

Reason:

This method of invocation looks more like the traditional development calling interface class. At the same time, you don't have to worry too much about what Http calls.

With a few appeals, basic developers can switch from traditional development mode to cloud mode without feeling.

Spring Boot + Cloud actually simplifies our development and improves efficiency. Let's focus more on the implementation of specific business functions.

Real developers, don't feel the difficulty of switching from traditional mode to Cloud micro-service mode. When applied, you will find that everything has become simple and clear. If it is still the same, it can only be said that the planning of the people did not pass.

The biggest difficulty of traditional service transformation Micro-service is the localization, planning and segmentation of micro-service. The postgraduate is to do planning and positioning of the people.

Some recommended plans for Spring Cloud development