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

Adding a subject example with a mix of wildcards

Browse Source 
Signed-off-by: Matthias Hanel <mh@synadia.com>
This commit is contained in:
Matthias Hanel 2020-02-03 20:24:42 -05:00
parent 3380706b5c
commit 0de28c17df
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
nats-concepts/subjects.md
View File

@ -1,6 +1,6 @@
# Subject-Based Messaging
Fundamentally NATS is about publishing and listening for messages. Both of these depend heavily on _Subjects_ which scope messages into streams or topics. At its simplest, a subject is just a string of characters that form a name the publisher and subscriber can use to find each other.
Fundamentally, NATS is about publishing and listening for messages. Both of these depend heavily on _Subjects_ which scope messages into streams or topics. At its simplest, a subject is just a string of characters that form a name the publisher and subscriber can use to find each other.
![](../.gitbook/assets/subjects1.svg)
@ -38,3 +38,6 @@ The second wildcard is `>` which will match one or more tokens, and can only app
Subject to your security configuration, wildcards can be used for monitoring by creating something sometimes called a _wire tap_. In the simplest case you can create a subscriber for `>`. This application will receive all messages -- again, subject to security settings -- sent on your NATS cluster.
### Mix Wildcards
The wildcard `*` can appear multiple times in the same subject. Both types be used as well. For example, `*.*.*.>` will receive `time.us.east.atlanta` as it is at least 4 tokens long.