taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

Syntax & grammar updates

Browse Source
This commit is contained in:
Ginger Collison 2021-04-30 10:18:03 -05:00 committed by GitHub
parent 9f3d076c7b
commit 7a831e12c4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
nats-server/configuration/subject_mapping/subject_mapping.md
View File

@ -19,7 +19,7 @@ mappings = {
# In this example bar.a.b would be mapped to baz.b.a. # In this example bar.a.b would be mapped to baz.b.a.
bar.*.*: baz.$2.$1 bar.*.*: baz.$2.$1
# You can scope mappings to to a particular cluster # You can scope mappings to a particular cluster
foo.cluster.scoped : [ foo.cluster.scoped : [
{ destination: bar.cluster.scoped, weight:100%, cluster: us-west-1 } { destination: bar.cluster.scoped, weight:100%, cluster: us-west-1 }
] ]
@ -62,7 +62,7 @@ With this mapping:
Messages that were originally published to `bar.a.b` are remapped in the server to `baz.b.a`. Messages that were originally published to `bar.a.b` are remapped in the server to `baz.b.a`.
Messages arriving at the server on `bar.one.two` would be mapped to `baz.two.one`, and so forth. Messages arriving at the server on `bar.one.two` would be mapped to `baz.two.one`, and so forth.
## Weighted Mappings for A/B Testing or Canary Releases. ## Weighted Mappings for A/B Testing or Canary Releases
Traffic can be split by percentage from one subject to multiple subjects. Here's an example Traffic can be split by percentage from one subject to multiple subjects. Here's an example
for canary deployments, starting with version 1 of your service. for canary deployments, starting with version 1 of your service.
@ -110,7 +110,7 @@ Now shutdown the version 1 instances of your service.
## Traffic Shaping in Testing ## Traffic Shaping in Testing
Traffic shaping is useful in testing. You might have a service that runs in QA Traffic shaping is useful in testing. You might have a service that runs in QA
that simulates failure scenarios which could receive 20% of the traffic to test that simulates failure scenarios which could receive 20% of the traffic to test
the service requestor. the service requestor.
@ -142,4 +142,4 @@ and the unaccounted for 2% would simulate message loss.
{ destination: myservice.requests.v3.fail, weight: 8% } { destination: myservice.requests.v3.fail, weight: 8% }
# the remaining 2% is "lost" # the remaining 2% is "lost"
] ]
``` ```