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

Update reqreply.md

Browse Source
This commit is contained in:
Ginger Collison 2019-06-07 08:45:30 -05:00 committed by GitHub
parent 9c59a64cb8
commit 66e4523adf
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
developer/concepts/reqreply.md
View File

@ -4,7 +4,7 @@ Request-Reply is a common pattern in modern distributed systems. A request is se
The increased complexity of modern systems requires features such as location transparency, scale up and scale down, observability and more. Many technologies need additional components, sidecars and proxies to accomplish the complete feature set.
NATS supports this pattern with its core communication mechanism, publish and subscribe. A request is published on a given subject with a reply subject, and responders listen on that subject and send responses to the reply subject. Reply subjects
are usually a subject called an _INBOX that will be directed back to the requestor dynamically, regardless of location of either party.
are usually a subject called an \_INBOX that will be directed back to the requestor dynamically, regardless of location of either party.
NATS allows multiple responders to run and form dynamic queue groups for transparent scale up. The ability for NATS applications to drain before exiting allows scale down with no requests being dropped. And since NATS is based on publish-subscribe, observability is as simple as running another application that can view requests and responses to measure latency, watch for anomalies, direct scalability and more.