LoadRunner the spring Cloud app with the registration center Gateway

Initial situation:

3 Registry 3 Gateway routes Zuul, 3 service providers

Test Service Provider Interface:

Test Service Provider Interface 10.166.10.117:8085/testgettps?param=1

Remark (important) LoadRunner How to test the cluster

Scenario 1

10.166.10.117 can be a service caller who exists in and current Eureka and Zuul clusters,

LoadRunner invokes service callers 117 (117 calls the service application within the cluster via Feignclient),

To achieve the performance test of the cluster, if you think 1 callers have bottlenecks, you can use two callers. (LoadRunner can be configured)

Scenario 2

117 can also be a routing gateway address, plus the corresponding port, followed by the micro-service node, + service name

Another example

10.166.15.29:16096/invoice-core-service-provider/invoice-core/getauthorization

In this case, there is a single node in the joint (not highly reliable).

Scenario 3

117 is an nginx address, by forwarding to multiple gateway routing addresses and then referring to Scenario 2

all 3 Scenarios Configure the Gateway's routing support for the microservices