What is the future of the backend?
The back-end is called the back-end because it has a hidden meaning: high concurrency, massive data and distributed.
Compared with the front end, the biggest difference lies in legacy data and scalability.
Many beginners may take the following route: syntax oriented programming - > function oriented programming - > performance oriented programming - > future oriented programming - > reuse oriented programming
In terms of syntax and function, the meaning of the front and back ends is not very different. In many traditional industries, the front and back ends are written together, and the salary will not be high. Most of the second and third tier cities are like this. Typical industries are software, office, finance, medical treatment, real estate, etc. They attach great importance to the business knowledge of developers, do not have high technical requirements, do everything with SQL statements, and jQuery plays all over the world.
When it comes to performance, the difference between the front and rear ends comes out.
The performance optimization of the front end is directly proportional to the number of user accesses, that is, the size of static files, CDNs and the number of connections. Most of the others are similar to the performance optimization of a single user. The first screen optimization is not the front end to some extent. In fact, the front and back ends are not divided by language at all, but by whether the code is executed on the user side or on the server side.
The back-end technology stack changes greatly with the growth of users.
Caching, consistent hashing, distributed, sub database, NoSQL, search, indexing, SQL, microservices, message queues, WebSockets, logs, monitoring, etc. are all used at this stage. The cloud service in the topic does reduce the installation, operation and maintenance of these infrastructures, but it does not involve design and architecture. Cloud service just provides better tools. At this point, it makes the back end more focused.
Therefore, the growth path of the back end here is very long. It takes a long time to understand and absorb every point. It's normal to feel that you don't understand anything after 5 ~ 7 years.
This is also the main reason why I have always looked down on the whole dish engineer. The back end has never been Java, let alone Java syntax. Many people who have learned some Java syntax and feel like they are God after reading the JDK source code actually don't know the greatness of heaven and earth.
For example, if you play go and fully understand the process of making chess pieces and chessboards, can you play go well? No, you still have to spend a long time learning rules and patterns.
So what is the fourth phase of future oriented programming?
In the past, waterfall development process was completely powerless in the face of demand changes. The more complex the system, the stronger the sense of powerlessness.
For example, you take care of a baby. No problem. Taking care of two babies is crazy. Taking care of 10000 babies?
Therefore, agile development appears at this point in time to solve problems, require continuous delivery and embrace change.
Embracing change is a very key value. In those years, it was recognized that requirements always change. From accepting this setting, the requirements for engineers are obvious, that is, to what extent does the system architecture you have made support demand changes?
I didn't finish it. I released it carelessly. Forget it. I'll write it later. Why is the back-end more difficult than the front-end when programming for the future.
You can also go to the official website of the academy to find the official group for discussion and exchange at any time~
"We believe that everyone can become an engineer. From now on, find a senior brother to introduce you and stop being confused on the way to learning. Here is the skill tree. It Academy: http://www.jnshu.com , beginners switch to the gathering place of the Internet industry. "Welcome to add it exchange group 565734203 to discuss and exchange with you