Introduce load balancer

[yillkid]

The possible steps to implement load balancing with swarm nodes can be enumerated as follows:

1. Both public and private IP swarm node support because the swarm node may deploy on IoT devices that have private IP only.
2. First available process in the queue list has the highest priority because of swarm node deploy on a wide variety of devices, we should set the higher level device on the top.
3. No head-of-line blocking problem.

Reference:

• Request load balancing (passenger)

[jkrvivian]

Could you explain more about point 2 ?

• What is "available process in the queue list" ? I thought it is a queue holding requests(by picture demonstration), or did I misunderstand?
• What does "the higher level device" do? Is it to manage swarm nodes?

Thanks :smiley:

[yillkid]

Available process in the queue list means First available process in the list has highest priority refer the chapter of Passenger library documentation for detail. And according to the this, we should put higher level swarm node in the In front of the list of requests handler.

[yillkid]

Passenger seems lack of the reverse proxy, the limitation as below:

1. Can't proxy request to different applications (just multi-processing for one application).
2. No any extension interface to implement proxy API command to private IP applications.