#The best time to plant a tree is ten years ago, followed by now
Many programmers can't find a direction in learning at first, but I think after a period of novice period, most of these problems will become less obvious, and the direction of work will gradually become clear.
But it didn't take long for the information that I could understand began to exceed the ability to learn every day, such as buying books that I didn't read, collecting posts that I didn't read, and articles that I didn't follow after I marked them, not to mention the accumulation of more and more articles. Every day, I am faced with various technology sharing or new things in Weibo.
Most people have limited time for learning every day, and how to improve learning efficiency at this stage has become the focus of the solution.
Talking about your experience in improving learning efficiency is actually very simple: systematic learning.
I used to like to read some blogs or some articles that "look" relatively easy to understand. I would mark any technical article I swiped on Weibo and WeChat every day, and I could read it in a few minutes. But after a period of time, although I read a lot of things, I still have a state of spinning around in place, and I have not felt any actual improvement.
In the end, I couldn't help it, and I nibbled it hard with the thick book, and suddenly I felt a sense of enlightenment: what I learned when I was reading is a complete knowledge network, and each knowledge point is related to and different from other content. This kind of comprehensive understanding is much higher than an independent article.
After repeating the painful learning-combing process several times, it is often more effective to read some independent articles or materials, because the corresponding knowledge can be found in the system, and sometimes even a page of a book only needs to read a sentence If you break through that layer of window paper, you can master new knowledge. Many programmers can't find a direction in learning at first, but I think after a period of novice period, most of these problems will become less obvious, and the direction of work will gradually become clear.
But it didn't take long for the information that I could understand began to exceed the ability to learn every day, such as buying books that I didn't read, collecting posts that I didn't read, and articles that I didn't follow after I marked them, not to mention the accumulation of more and more articles. Every day, I am faced with various technology sharing or new things in Weibo.
Most people have limited time for learning every day, and how to improve learning efficiency at this stage has become the focus of the solution.
Talking about your experience in improving learning efficiency is actually very simple: systematic learning.
I used to like to read some blogs or some articles that "look" relatively easy to understand. I would mark any technical article I swiped on Weibo and WeChat every day, and I could read it in a few minutes. But after a period of time, although I read a lot of things, I still have a state of spinning around in place, and I have not felt any actual improvement.
In the end, I couldn't help it, and I nibbled it hard with the thick book, and suddenly I felt a sense of enlightenment: what I learned when I was reading is a complete knowledge network, and each knowledge point is related to and different from other content. This kind of comprehensive understanding is not as high as an independent article.
After repeating the painful learning-combing process several times, it is often more effective to read some independent articles or materials, because the corresponding knowledge can be found in the system, and sometimes even a page of a book only needs to read a sentence If you break through that layer of window paper, you can master new knowledge. So I suggest that you read articles and blogs, not just one article. The best results are achieved through transparent and continuous learning.
Microservices are the development standard of the current Java industry, Spring Boot and Spring Cloud are hot topics, and more and more requirements for microservices appear in the recruitment information of enterprises. I was first left behind by others. However, in the interviews of many first-line Internet companies, microservices have become the focus of interviews and must be asked! Especially for Java developers who are more than 3 years old!
Domestic developers are struggling with the use of Dubbo and Spring Cloud. Many functional components of Spring Cloud have been discontinued, and the environment construction is complicated. In recent years, the Spring Cloud Alibaba component launched by Alibaba has made it easier to get started, with a low learning curve, and it can be better. It is integrated with the Spring Cloud ecosystem, and the powerful alliance has further increased Spring Cloud's dominant position in the development of microservices in the Java field. But unfortunately, there are few detailed, comprehensive and practical notes on this topic on the market. Especially for beginners, the cost of learning is still very high.
Here, I will share with you some organized microservice architecture study notes, including Spring Cloud, Spring Cloud Alibaba study notes! Due to the number of words, in order not to affect reading, the entire table of contents and content screenshots are shown here
Spring Cloud study notes manual directory and content
It is divided into 4 modules:
- Service registration Eureka and service call Ribbon
- Service call Feign and service fuse Hystrix
- Microservice Gateway
- Spring Cloud Stream and Spring Cloud Config and Apollo, an open source configuration center
The first module directory and content
- Microservices Basics
- Overview of SpringCloud
- Case Construction
- Service Registration Eureka Basics
- Service Registration Eureka Advanced
- Eureka Alternatives Consul
- Getting Started with Service Invocation Ribbon
- Service Call Ribbon Advanced
Content display
The second module directory and content
- Getting Started with Feign Service Calls
- Service Call Feign Advanced
- Service Registration and Discovery Summary
- The high concurrency problem of microservice architecture
- Getting Started with Service Melting Hystrix
- Service Circuit Breaker Hytrix Advanced
- Alternatives to service fuse Hystrix
Content display
The third module directory and content
- Microservice Gateway Overview
- Microservice Gateway Zuul
- Microservice Gateway GateWay
- Overview of Link Tracing for Microservices
Content display
The fourth module directory and content
- Spring Cloud Stream
- Spring Cloud Confg
- Open source configuration center Apollo
Spring Cloud Alibaba study notes manual catalog and content
- Chapter 1 Introduction to Microservices
- Chapter 2 Construction of Microservice Environment
- Chapter 3 Nacos Discovery – Service Governance
- Chapter 4 Sentinel – Service Fault Tolerance
- Chapter 5 Gateway – Service Gateway
- Chapter 6 Sleuth - Link Tracing
- Chapter 7 Rocketm – Message Driven
- Chapter 8 SMS – Short Message Service
- Chapter 9 Nacos Config – Service Configuration
- Chapter 10 Seata – Distributed Transactions
Content display
Summarize
What makes you stronger than others is not how many years of CRUD work you have done, but the more in-depth skills you have mastered than others. Don't always stay on the surface of CRUD, understand and master the underlying principles and be familiar with the source code implementation, and form your own abstract thinking ability, and use it flexibly is an important direction for you to break through the bottleneck and stand out!
When you are on Douyin and playing games, others are here to learn, grow, and improve. The biggest gap between people is actually thinking. You may not believe that good people are always together.