Shulou(Shulou.com)06/01 Report--

This article mainly explains "what is the nginx reverse proxy load balancing strategy". Interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Next let the editor to take you to learn "what is the nginx reverse proxy load balancing strategy"!

1. The difference between forward proxy and reverse proxy

A forward proxy is a proxy server (intermediate server) located between the client and the target server. In order to obtain content from the original server, the client sends a request to the proxy server and specifies the target server, and then the agent transfers the content to the target server and returns the obtained content to the client. In the case of a forward proxy, the client must make some special settings before it can be used.

The reverse proxy is just the opposite. To the client, the reverse proxy is like the target server. And the client does not need to make any settings. The client sends a request to the reverse proxy, and then the reverse proxy determines where the request goes and transfers the request to the client, so that the content is just like himself. At one time, the client does not perceive the services behind the reverse proxy. Therefore, the client does not need to make any settings, just regard the reverse proxy server as the real server.

2. Nginx reverse proxy load balancing strategy

Ip_hash: for IPV4, use the first 3 bytes to calculate the hash value; for IPV6, use all bytes to calculate the hash value.

3. MySQL index

MySQL index

4. MVCC mechanism of innodb transaction

MySQL transaction isolation level and MVCC

5. The function of redo log and undo log in MySQL

How many log types do we need to remember in MySQL?

6. MySQL execution plan (explain statement)

Detailed explanation of Explain of MySQL

7. Advantages and disadvantages of micro-service

Advantages:

Independent scalability, each micro-service can be expanded horizontally or vertically independently and rapidly according to the actual business growth.

With independent upgradeability, each micro-service can be upgraded and updated independently, without relying on other services, and can be continuously released with continuous integration tools, so developers can quickly complete the service upgrade release process independently.

Easy to maintain, the code of each microservice is only focused on accomplishing the work of a single business area, so the number of microservice project code will be reduced to the size that IDE can load quickly, which can improve the readability of the code, which in turn can improve the productivity of developers.

Language-independent, developers can choose the language and framework they are most familiar with to complete their micro-service projects (of course, generally according to the actual technology stack needs of each company), so that in the face of the selection of new technologies or frameworks, micro-services can better respond quickly.

Failure and resource isolation, when there is bad resource operation behavior in the system, such as memory leakage, database connection is not closed, will only affect a single microservice.

To optimize cross-team communication, if we want to fully practice the design style of micro-service architecture, the R & D team will certainly be divided according to the new principles, from the previous division of skills and functions to the division of business (a single micro-service). In this way, the team will have R & D personnel with skills in all directions, and the communication efficiency is better than that of the organizational structure divided by skills.

Based on the system architecture design based on "cloud" and the design style of micro-service architecture, we can build a system that is highly friendly to "cloud". It can be easily combined with common container tools such as Docker to build a continuous release system to interface with IaaS and PaaS platforms, so that it can be easily deployed on various "clouds", such as public cloud, private cloud and hybrid cloud.

Disadvantages:

Increased system complexity

The difficulty of operation and maintenance is increased.

Local calls become RPC calls, and some operations can be time-consuming

Distributed transactions may be introduced

8. Distributed transaction

For the first time, someone made "distributed transaction" so simple and clear.

9. What are the components of spring cloud

Spring Cloud Netflix: core component, which can integrate multiple Netflix OSS open source suites, including the following components: Eureka: service governance component, including service registration and discovery Hystrix: fault tolerant management component, fuse Ribbon: client load balancing service invocation component Feign: declarative service invocation component based on Ribbon and Hystrix Zuul: gateway component Provide intelligent routing, access filtering and other functions Archaius: externalized configuration components Spring Cloud Config: configuration management tools to achieve external storage of application configuration, support for client configuration information refresh, encryption / decryption configuration content and so on. Spring Cloud Bus: events, message buses, used to propagate state changes or events in the cluster, and to trigger subsequent processing Spring Cloud Security: spring security-based security toolkit to add security control Spring Cloud Consul to our applications: encapsulates Consul operations, Consul is a service discovery and configuration tool (similar to Eureka) that integrates seamlessly with Docker containers

10. Eureka principle

Eureka boutique source code

11. How to implement distributed locks in Redis

The most powerful implementation of Redlock:Redis distributed Lock

12. Dynamic agent

Great! Finally, someone has made it clear that dynamic agents, CGlib and AOP are all clear!

13. How to achieve single sign-on

Single sign-on principle and simple implementation

14. Is MD5 an encryption algorithm?

MD5 is an information digest algorithm, not an encryption algorithm.

The encryption algorithm is reversible, that is to say, the ciphertext obtained by encrypting plaintext can be restored by decryption.

The information summary algorithm is irreversible, because in the process of calculating the summary, the information of the plaintext is compressed and only part of the features of the plaintext are retained, but according to these features, there is no way to restore the plaintext. This is the difference between information digest algorithm and encryption algorithm.

If you compare your body to plaintext, then your fingerprint is a summary of your information, fingerprints are part of your body characteristics, and fingerprints alone cannot restore your whole body.

At this point, I believe you have a deeper understanding of "what is the nginx reverse proxy load balancing strategy". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.