Is it necessary to use nginx after using dubbo?

Dubbo's load balancing is at the service level, while nginx's load balancing is still at the http request level.

dubbo has the functions of server registration, discovery, routing, and load balancing. (Recommended learning: nginx tutorial)

Among all the service management components that implement these functions, I personally feel that dubbo is still a little cumbersome because it is formulated according to the j2EE category. service governance framework.

Dubbo does more like a DNS in service discovery (personal feeling). A consumer needs to know where such a service is, dubbo tells him, and then he calls it himself.

While nginx has the above functions, it also has two main functions:

1, maintain as many connections as possible.

2. Pass the specific service requirements of each connection to the real worker.

nginx is located between the user's browser and their own server. It is usually used to manage some resources, that is, to put different types of resources on different servers. nginx to manage it.

dubbo is a business bridge between your own server and your own server. It puts different services on different servers respectively, that is, distribution development, and then conduct unified and integrated management of its registered services.

The above is the detailed content of Is it necessary to use nginx after using dubbo?. For more information, please follow other related articles on the PHP Chinese website!