Skip to content

Commit 1434c4b

Browse files
Edits
1 parent 2e377de commit 1434c4b

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

modules/ROOT/pages/create-instance-task-flex.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ include::partial$task-configure-proxy.adoc[tags=last-steps]
4646

4747
Flex Gateway version 1.5.x or later supports API instances that expose multiple upstream services through a single consumer endpoint.
4848

49-
Flex Gateway manages request traffic by using different routes that can each direct traffic to multiple upstream services. Flex Gateway directs traffic to the routes by using the route order and the individual route's rules.
49+
Flex Gateway manages request traffic by using different routes that can each direct traffic to multiple upstream services. Flex Gateway directs traffic to the routes by using the route order and the individual route's rules. Additionally, you can a weighted percentage to each upstream service within a route to manage the amount of traffic directed to each upstream.
5050

5151
In the following diagram, different routes manage requests to flight information databases and to a customer service application. Route one has two upstream services defined, which direct 70% of requests to a stable database and 30% of requests to a beta database.
5252

@@ -67,7 +67,7 @@ You can direct requests to different routes by using route rules.
6767

6868
To view and edit route rules, click *Route Rules*.
6969

70-
All rules are optional. If a rule does not have a value, that rule is ignored. For example, not specifying a host means that the route can service any host if the request meets the other route rules. Not defining any rule means that the route can service every request.
70+
All rules are optional. If a rule does not have a value, that rule is ignored. For example, not specifying a host means that the route can service any host if the request meets the other route rules. Not defining any rule means that the route can service every request.
7171

7272
Different routes can support the same upstream services. If you cannot capture all requests for a particular set of upstream services in a single route rule set, you can define multiple routes with different rules for full coverage.
7373

0 commit comments

Comments
 (0)