Original: Taste of Little Sister (wechat official ID: XjjDog), welcome to share, please reserve the source.

This is a typical Xjjdog article, more bullshit than technology, so give it a thumbs up.

Nginx is very easy to use, almost every company uses it, its main functions are reverse proxy, load balancing, static and static separation, and the most important is reverse proxy.

Its main architecture diagram is as follows:The client cannot directly access the server at the back end, because the server resources are so high that the client does not have permissions. In this case, a proxy is required to forward the request from the client and return the result to the client.

Why not just let the client access the server? This involves the issue of resource isolation. There are some real intentions of the server that the client does not want to know, such as some sensitive resources protected by security. In other words, through the proxy, the client can only see what the server wants to see.

For clients, functionality is always emasculated! Even tampered with!

Let’s replace the elements in the diagram, and something wonderful happens.

We replace client with poor ordinary code farmers and Server with the leader of OX X. We can see 6 green arrows, with howling mountain wind, mercilessly pointing at proxy.

Proxy becomes a key resource. This proxy requirement is not simple, need five evils three lack, on the mandate of heaven, called nine you. Nginx engineers deserve to be called nGINx engineers.

An NGINx engineer does not have to have a mind of his own, but he must remember every word of the leader and understand his true intentions. When transmitting the ideas of leaders, he also knows the importance and filtering, and can broadcast the ideas of leaders quickly and accurately.

Refuse to accept not line, this is really not ordinary people can do.

Who can be an Nginx engineer?

In the slave society, no matter how hard a slave worked or how outstanding his ability was, he never got ahead. On the contrary, the overseers with whips were more likely to win the admiration of their masters, and to be thought of while drinking and eating meat.

Even more wonderful, if the work of the overseers and slaves were switched. A slave may be competent for the work of a supervisor, but a supervisor can never be competent for the work of a slave.

Why is that? It can be summarized as follows:

  1. The supervisor knows more inside sources and is more likely to favor the master
  2. Supervisor’s work attribute is management, can operate the space is large
  3. Overseers are closer to the center of power and tend to be heard more often

You might say, well, it’s the nature of society, and certainly not today. You’re half right. That’s the problem. Because of the evolution of each company, programmers in different companies, the feelings and treatment, is also very large. You may even get the mentality of the dad in the picture.

Supervisors are generally not at the front line, far from production, and can only understand a little about client’s ideas. The correctness of this little bit of transmission to the server is even harder to guarantee. Moreover, the supervisor spends a lot of energy on understanding the leader’s intention and summarizing excel, and the time spent on really meaningful things is pitiful. So what to do? I had to take the client’s work as my own.

As a result, programmers writing code may find themselves doing a lot of work, which is processed and forwarded by the proxy to the boss.

Proxy does the right thing, 996 client also needs to adjust the code late at night, proxy only needs to swipe TikTok on the side. Working intensity is different, working hours do not measure the value of comparison naturally.

We can also look at three conduction scenarios for proxy.

Scenario 1:

Server: To strengthen staff culture construction. Proxy: go to group construction on Saturdays and weekends, and AA client: WCNMCopy the code

Scenario 2:

Server: Companies should be frugal. Proxy: No toilet paper or boiling water from tomorrowCopy the code

Scenario 3:

Server: Xx Wang is a model of the company. Proxy: Turn on Wolf culture, Ming qi996
client: WCNM
Copy the code

As you can see, the proxy qualities of this layer are particularly important. If you happen to run into a parallel proxy, you can imagine the extent of your misery. But if you meet a nice proxy, cherish him, because all the pressure, need to be transmitted by him.

What does the average Nginx engineer do?

In order to make the donkey pull the mill, people think of four tactics: blindfolded, covering the mouth, covering the ears, and whipping.

In the same way, for proxy to work, it can prevent you from seeing certain things; When you want to speak out, use violence to silence you. When you want to hear what a leader really wants, plug your ears. When you slacken, use a whip to get your work done.

Many companies have a multi-layer proxy topology due to the large number of employees and complex structure. This kind of company is very wonderful. A proxy can serve as a client of another proxy. In many cases, the number of servers is even more than the number of clients.

I feel sorry for these proxies, they work so hard. However, due to the working characteristics of proxy, it only needs complete forwarding to complete the work, without thinking — naturally, it has a black and shiny hair. Add in the fact that nginx engineers can easily break the 35-year old spell, and it’s still a highly desirable career.

Do you want to be an Nginx engineer?

Xjjdog is a public account that doesn’t allow programmers to get sidetracked. Focus on infrastructure and Linux. Ten years architecture, ten billion daily flow, and you discuss the world of high concurrency, give you a different taste