Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Learn from me Spring Cloud (Finchley version)-01-the beginning

2025-02-21 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >

Share

Shulou(Shulou.com)06/03 Report--

Introduction to the preface course

Recently, a lot of children's shoes in the official account (itmuch_com) to promote the Spring Cloud series of tutorials, so there is this series. The following are some instructions / plans / answers:

Q: why is it based on Finchley instead of Greenwich?

A: for now, Finchley is closer to production, while Greenwich has not yet been released-although it is already RC, there are many uncertainties, such as whether Resilience4j will successfully hatch in the Greenwich version (probably not), not a single line of spring-cloud-netflix-concurrency-limits documents, etc. (it may not be possible that the project will be killed directly. There are many other undetermined points that led the author to choose Finchley as the basic version of the blog. In the future, after the official release of Greenwich, consider upgrading to Greenwich, or supplement it in an extra form.

Q: how is the series of courses planned?

A: it is divided into main stories and non-stories. The main story is Eureka, Ribbon, Feign, Hystrix, Zuul, Spring Cloud Config, Spring Cloud Gateway, Spring Cloud Sleuth, Spring Cloud Stream;, Spring Cloud Consul, Spring Cloud R4j, Nacos, Sentinel;, continuous integration, continuous release, code quality control. This is the plan for the time being.

Q: what can I get from this course?

Answer: after learning, you can more in-depth understanding of the Spring Cloud components of the use of routines, can avoid N how common pit (such as Feign configuration pit, Ribbon configuration pit, father-son context pit, the status of UNKONWN pit, you may not know what I am talking about, it does not matter, later encountered and then come to check the documentation on the line), understand the working principles of various components and the relationship between components.

Q: is there a charge?

A: it's free. Geek time asked me twice for manuscripts, and I did consider charging. Money is a good thing, I am not a saint, but I still give up, there are many ways to make money, open source is what I love. I just want everyone not to be so ugly / ugly when making suggestions. (why do you say that? you can go back to my comments below the Spring Cloud open source video. Too TM ugly)

Q: how can I learn this tutorial?

A: I will [bold] the text you need to pay attention to, mark important knowledge points [important], mark [TIPS] where you can broaden your horizons, mark [WARNING] where you need to focus, and never forget [expand reading]-this will be an important way to expand your knowledge and technical horizons. Remember, never just learn knowledge, knowledge is endless, for software, knowledge may also change. What you should improve is your learning ability and broaden your technical horizons. With the popularity of micro-services / Cloud Native, the future is bound to be integration capabilities > individual technical capabilities.

Q: update frequency? Not an eunuch, is it?

A: so far, 21 articles have been completed and 3 shifts are scheduled every week, but they are not updated on a fixed day of the week. As for whether or not an eunuch, I can only try not to, I do not write full-time open source documents. Work is very busy, usually have to 10 o'clock to get to the dormitory to start their own life; unusual times, there is no life. In short, the more people I watch, the more passionate I will be!

Q: is your TM self-answer as annoying as a mental illness?

Answer: my TM is old, can't you talk a little more nonsense?

Finally, originality is not easy! If the course is helpful to you, don't be stingy, please forward it! Forget coffee, please. Coffee makes me sleepless ^ _ ^

Let me put an end to the nonsense! Let's roll!

Introduction to Spring Cloud

Although Spring Cloud has the word "Cloud", it is not a cloud computing solution, but a toolset built on top of Spring Boot and used to quickly build common patterns for distributed systems.

Applications developed using Spring Cloud are ideal for deployment on Docker or PaaS (such as Cloud Foundry), so they are also called cloud native applications (Cloud Native Application). Cloud Cloud Native can be simply understood as a software architecture for cloud environment. When it comes to cloud natives, we have to mention the Twelve elements Application Manifesto (12-factor Apps), which is the methodology and best practice of cloud native architecture.

Expand reading

"Cloud Native Application" eBook: https://pivotal.io/platform-as-a-service/migrating-to-cloud-native-application-architectures-ebook Twelve elements Application Manifesto (12-factor Apps) Chinese version: https://12factor.net/zh_cn/ Core function Distributed/versioned configuration distributed / versioned configuration Management Service registration and discovery Service registered with Service Discovery Routing routing Service-to-service calls end-to-end invocation Load balancing Load balancing Circuit Breakers Circuit Breaker Global locks Global Lock Leadership election and cluster state Election and Cluster State Management brief introduction to Distributed messaging distributed message version

We know that most Spring projects are named in the form of "major version number. Minor version number. Incremental version number. Milestone version number", such as Spring Framework stable version 4.3.5.RELEASE, milestone version 5.0.0.M4 and so on. Among them, the major version number indicates a major reconfiguration of the project; the minor version number indicates the addition and change of new features; the incremental version number generally indicates bug repair; and the milestone version number indicates the milestone of a certain version number.

However, Spring Cloud does not manage versions in this way. Let's take a closer look at the version of Spring Cloud.

Let's take a look at the version of Spring Cloud, as shown in the figure.

As can be seen from the picture, Spring Cloud is named after the English word SRX. So what do English words and SR mean respectively?

Spring Cloud is a comprehensive project that contains many subprojects. Because the subproject also maintains its own version number, Spring Cloud uses this version naming method to avoid confusion with the version of the subproject. Among them, the English word is called "release train", Angel, Brixton, Camden and so on are the names of London subway stations. They are issued in alphabetical order and can be understood as the evolution of the main version. SR stands for "Service Release", which generally means Bug fix; before the SR version is released, a Release version, such as Camden RELEASE, is released.

After the above explanation, I believe you can understand the version of Spring Cloud very well. For example, Camden SR3 represents the third Bug fix version of the Camden version.

TIPS

The release record of the Spring Cloud version can be found in:, from which we can clearly see the release time and sequence of the Spring Cloud version. Spring Cloud version evolution plan: from which we can learn about the version evolution plan of Spring Cloud, such as when and what version is planned to be released. In fact, there are many projects in Spring that use similar naming methods. For example, Spring Data, Spring Cloud Stream, etc. List of sub-items

After understanding the version of Spring Cloud, let's take a look at the subprojects and versions included in each version of Spring Cloud. Different versions of Spring Cloud have different subprojects:

ComponentEdgware.SR5Finchley.SR2Finchley.BUILD-SNAPSHOTspring-cloud-aws1.2.3.RELEASE2.0.1.RELEASE2.0.1.BUILD-SNAPSHOTspring-cloud-bus1.3.3.RELEASE2.0.0.RELEASE2.0.1.BUILD-SNAPSHOTspring-cloud-cli1.4.1.RELEASE2.0.0.RELEASE2.0.1.BUILD-SNAPSHOTspring-cloud-commons1.3.5.RELEASE2.0.2.RELEASE2.0.2.BUILD-SNAPSHOTspring-cloud-contract1.2.6.RELEASE2.0.2. RELEASE2.0.2.BUILD-SNAPSHOTspring-cloud-config1.4.5.RELEASE2.0.2.RELEASE2.0.2.BUILD-SNAPSHOTspring-cloud-netflix1.4.6.RELEASE2.0.2.RELEASE2.0.2.BUILD-SNAPSHOTspring-cloud-security1.2.3.RELEASE2.0.1.RELEASE2.0.1.BUILD-SNAPSHOTspring-cloud-cloudfoundry1.1.2.RELEASE2.0.1.RELEASE2.0.1.BUILD-SNAPSHOTspring-cloud-consul1.3.5.RELEASE2.0.1. RELEASE2.0.2.BUILD-SNAPSHOTspring-cloud-sleuth1.3.5.RELEASE2.0.2.RELEASE2.0.2.BUILD-SNAPSHOTspring-cloud-streamDitmars.SR4Elmhurst.SR1Elmhurst.BUILD-SNAPSHOTspring-cloud-zookeeper1.2.2.RELEASE2.0.0.RELEASE2.0.1.BUILD-SNAPSHOTspring-boot1.5.16.RELEASE2.0.6.RELEASE2.0.7.BUILD-SNAPSHOTspring-cloud-task1.2.3.RELEASE2.0.0.RELEASE2.0.1.BUILD-SNAPSHOTspring-cloud-vault1. 1.2.RELEASE2.0.2.RELEASE2.0.2.BUILD-SNAPSHOTspring-cloud-gateway1.0.2.RELEASE2.0.2.RELEASE2.0.2.BUILD-SNAPSHOTspring-cloud-openfeign2.0.2.RELEASE2.0.2.BUILD-SNAPSHOTspring-cloud-function1.0.1.RELEASE1.0.0.RELEASE1.0.1.BUILD-SNAPSHOTSpring Cloud/Spring Boot compatibility [important] Spring Cloud version Spring Boot version Greenwich2.1.xFinchley2.0.xEdgware1.5.xDalston1.5.x

You can check version compatibility at https://spring.io/projects/spring-cloud#overview.

Original: http://www.itmuch.com/spring-cloud/finchley-1/, reproduced, please state the source.

Practical information sharing

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Internet Technology

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report