Skip to content

Fix formatting and wording in queues walkthrough #908

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jjpinto wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix formatting and wording in queues walkthrough #908

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions nats-concepts/core-nats/queue-groups/queues_walkthrough.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ NATS supports a form of load balancing using [queue groups](queue.md). Subscribe

## Walkthrough prerequisites

If you have not already done so, you need to [install](/nats-concepts/what-is-nats/walkthrough_setup.md) the `nats` CLI Tool and optionally the nats-server on your machine.
If you have not already done so, you need to [install](/nats-concepts/what-is-nats/walkthrough_setup.md) the `nats` CLI tool and optionally the nats-server on your machine.

### 1. Start the first member of the queue group

Expand All @@ -14,15 +14,15 @@ The `nats reply` instances don't just subscribe to the subject but also automati
nats reply foo "service instance A Reply# {{Count}}"
```

### 2. Start a second member of the queue-group
### 2. Start a second member of the queue group

In a new window

```bash
nats reply foo "service instance B Reply# {{Count}}"
```

### 3. Start a third member of the queue-group
### 3. Start a third member of the queue group

In a new window

Expand All @@ -38,7 +38,7 @@ nats request foo "Simple request"

### 5. Verify message publication and receipt

You should see that only one of the my-queue group subscribers receives the message and replies it, and you can also see which one of the available queue-group subscribers processed the request from the reply message received (i.e. service instance A, B or C)
You should see that only one of the my-queue group subscribers receives the message and replies to it, and you can also see which one of the available queue group subscribers processed the request from the reply message received (i.e. service instance A, B or C)

### 6. Publish another message

Expand All @@ -48,11 +48,11 @@ nats request foo "Another simple request"

You should see that a different queue group subscriber receives the message this time, chosen at random among the 3 queue group members.

You can also send any number of requests back-to-back. From the received messages, you'll see the distribution of those requests amongst the members of the queue-group. For example: `nats request foo --count 10 "Request {{Count}}"`
You can also send any number of requests back-to-back. From the received messages, you'll see the distribution of those requests amongst the members of the queue group. For example: `nats request foo --count 10 "Request {{Count}}"`

### 7. Stop/start queue-group members
### 7. Stop/start queue group members

You can at any time start yet another service instance, or kill one and see how the queue-group automatically takes care of adding/removing those instances from the group.
You can at any time start yet another service instance, or stop one and see how the queue group automatically takes care of adding/removing those instances from the group.


## See Also
Expand Down