Java back-end top-down approach-start here

(1) Write in front

Why do I suddenly want to write this series of blogs on the java backend? It may be considered a whim. However, I am not writing these articles as a technologist or professional computer scientist, I am as an ordinary learner to record the bits and pieces of my learning process.

Friends who have gone to university may feel this way. For a certain point of knowledge, the school’s distinguished professor failed to teach you for two hours. As a result, it took less than half an hour for your roommate to fully understand it. This knowledge point. Is the professor's professional level not as good as your roommate? That's certainly not the case. However, a high-level person does not mean that the level of teaching must be high. A high-level person may be full of professional terminology. The PPT is also full of papers by various scholars. They think they speak very well. But in the eyes of ordinary students, it is very likely that they are listening to the heavenly scriptures, and they can only study by themselves slowly after class. Our department once had a mid-term exam for a professional course, with more than 100 students in a class, and most of them failed. Therefore, I have been in university for almost two years. I haven't learned anything else, but my self-study ability has improved a lot. Therefore, I have thought more than once that it is a very good choice to have a partner who learns together, pointing and learning from each other.

A characteristic of the computer technology community is to use professional terms to explain professional terms, which discourages many newcomers. There is another source-only theory. If you ask a question: how should spring learn? I bet that at least one-third of them will let you read the source code. Of course, there are generally two kinds of people, one is the real boss (I admire), and the other is the pretend boss (I despise). Of course, it’s not that the source code is not important. Now that the computer industry is so involuntary, the source code per person in the development post is not very strange. But if you let someone who is new to spring read the source code, you might as well kill him directly. In my opinion, reading the source code should be done after having a relatively proficient grasp of the basic use of the framework. The purpose is to learn the implementation principle of the framework and understand what the architecture of the top-level project should be. This should be an improvement. Part, not the entry part. Just like practicing qigong, beginners follow the master to learn some fancy, and then slowly practice internal skills, and finally they can bring forth new ideas and self-reliance. Isn’t it worth learning at first? I don’t think so.

I personally have a habit of learning, which is the so-called "task-driven learning". Assign yourself a task (such as doing a project), and then gradually realize the details one by one by checking information and reading documents. I think this way of learning is efficient (of course this is for me, I don’t know for others), but some details may not be particularly thorough. I spent almost two weeks, from java helloworld to javaweb, multi-threading, SSM, springboot, and now looking at jvm, I don’t think I learned very fast (because I have other classes to take ), there must be friends who learn faster and more solidly than me. However, I still want to write down some of the problems that I encountered during my study, for my own reference, and to let friends who have just entered this door avoid detours.

(2) What's in this series

The name of this series is "Java back-end top-down method", what is top-down? My understanding is to grasp a main line when learning, and expand step by step along the execution flow of the application. After the main line is completed, slowly go to the branch line and slowly fill in the missing details in the main line. Qi. It can also be called breadth first and depth first.

As for what's in this series, in fact, this is not much different from other java back-end series, and none of the necessary things can run. This is how I planned, first talk about some "old" technologies of java Web (Servlet, Tomcat, JDBC, etc. must be very familiar), and then touch advanced frameworks such as spring, mybatis, springMVC, database And the database connection pool is also needed, and finally learn springboot to see how to quickly build a spring project. After reading these, we can look at docker virtualization, and then build a cluster for load balancing. That's almost it. The following is a not-so-complete series of catalogs. We slowly improve, and slowly write articles and publish them:

Regarding the above catalog, I will release it from time to time, this catalog will also be adjusted, additions, deletions, and changes are possible. It has been busy recently, and the update may be slower, but it will not stop.

(3) Write at the back

Because this series is done by myself, time and energy are limited, so I may quote other blogs, books, papers and other materials. I will cite the source of these citations (if you can’t find the original address, don’t indicate it). Infringement of copyright, please contact me to delete. In addition, since I am also a beginner, there may be many mistakes or improper expressions. I hope you can give me your advice. For convenience, I will make repairs in the original text, and the place of repair may not be specifically noted. Therefore, all content in this series is declined to be reprinted, and the reprinted articles cannot be completely followed up with the subsequent revisions of this series. In order to ensure the quality of the articles, please look for CSDN, and the rest of the platforms are pirated.

There is a lot of nonsense. Finally, I wish you all become big cows as soon as possible, welcome like-minded friends to leave a message below or directly send me a private message to contact me.

April 24, 2020