#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 in a book only needs to read a sentence If you break the window paper, you can master new knowledge. Many programmers can't find the 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. Every day, I will mark any technical articles I swipe on Weibo and WeChat, and I can basically read them 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 was a complete knowledge network, and each knowledge point and other content were interconnected and differentiated. 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 in a book only needs to read a sentence If you break the 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.
Recently, a friend said that the company's business volume increased at the end of the year, and many microservice modules were split out. The energy spent on microservice management, resource scheduling, and scheduling strategies increased exponentially. Seeing that the cloud native architecture of microservices + k8s seems to be able to solve these problems, so I want to ask. I sorted out the answers to him, hoping to help more friends who have problems in this regard.
We all know that microservices and cloud-native architecture are hot technologies in the current Internet industry. While microservices are convenient, there are naturally some problems, and the emergence of k8s perfectly solves these problems. **Nowadays, more and more enterprises migrate their services to the k8s platform, and the cloud native technology with k8s as the core has gradually become the standard of enterprise architecture. **It is no exaggeration to say that for those who have mastered it, you will gain high salary, right to speak, sense of achievement and irreplaceability at the same time.
Of course, it is not easy to fully understand:
- There are many development tools, the source code of components is obscure, and the technical details involved in the business are also very complicated.
- The online self-study materials are numerous and complex, the official website is large and general, abstract and difficult to understand
- Lack of actual combat, it is still difficult to systematically solve the problem of actual application release and deployment
Today, Brother Gou has collected **Alibaba's second-generation microservice framework Spring CloudAlibaba, K8S, jenkens and other study notes and brain map notes. I hope it will be helpful to friends who are still learning microservice architecture!
K8S (Kubernates) study manual
As the "cornerstone" of cloud native, Kubernetes is the most important and unavoidable topic in the cloud native wave. Many domestic manufacturers have run their core business systems on Kubernetes (such as Taobao Double Eleven, Jingdong 618, etc.). At the same time, countless small and medium-sized enterprises are also exploring business containerization and cloud-native transformation. For technicians, mastering Kubernetes is not only a plus for improving workplace competitiveness, but also a must for advanced senior architects.
Content display
Alibaba's second-generation microservice framework Spring CloudAlibaba core learning manual
With the further expansion of the business scale, the further surge in traffic, and the further growth in the number of microservices, Eureka, the registration center used by the old microservice system, is overwhelmed. At the same time, the Spring Cloud system has evolved to the second generation, and the first generation of Eureka registered The center is no longer suitable for the current business logic and scale, and it is currently officially placed in maintenance mode by Spring Cloud and will no longer be developed. With the birth of Spring CloudAlibaba, many developers suffer from lack of systematic study notes in their studies. This study manual hopes to help those in need. The main contents are as follows:
- Chapter 1 Introduction to Microservices
- Chapter 2 Microservice Environment Construction
- Chapter 3 Nacos Discovery – Service Governance
- Chapter 4 Sentinel – Service Fault Tolerance
- Chapter 5 Gateway – Service Gateway
- Chapter 6 Sleuth – Link Tracing
- Chapter 7 Rocketmq – Message Driven
- Chapter 8 SMS – Short Message Service
- Chapter 9 Nacos Config – Service Configuration
- Chapter 10 Seata – Distributed Transactions
Content display
Spring CloudAlibaba brain map study notes
Jenkins study manual
Jenkins is an open source continuous integration tool that helps developers integrate code continuously and complete automated delivery pipelines. It has a wide range of uses and powerful functions, and there are many external plug-ins. In the process of implementing DevOps pipelines, Jenkins is the most widely used tool. This note describes Jenkins in detail from basic to proficient, as follows:
Content display
Summarize
Microservices are the most popular application architecture at the moment. Together with Container Cloud and DevOps, they are called the Three Musketeers of the New Era. They help us resolve the product iteration pressure caused by rapid business development, and allow us to freely choose the technology stack that is most suitable for our team. Allow the system to carry the access of a large number of Internet users.
As a developer, whether you are working or interviewing, microservices and containers have become popular technologies. If you still do not have good study notes and ideas because you want to learn, this study manual notes and the following thinking study route notes can Great help!