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

Merge pull request #76 from nats-io/sys

Browse Source 
Move sys_accounts to configuration, add subs=detail to monitoring
This commit is contained in:
Ginger Collison
2020-03-24 13:29:13 -05:00
committed by GitHub
parent 5117a37f6c fd8984dc38
commit e59525da15
11 changed files with 91 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
developing-with-nats/events/slow.md
View File

@@ -1,6 +1,6 @@
# Slow Consumers
NATS is designed to move messages through the server quickly. As a result, NATS depends on the applications to consider and respond to changing message rates. The server will do a bit of impedance matching, but if a client is too slow the server will eventually cut them off by closing the connection. These cut off connections are called _slow consumers_.
NATS is designed to move messages through the server quickly. As a result, NATS depends on the applications to consider and respond to changing message rates. The server will do a bit of impedance matching, but if a client is too slow the server will eventually cut them off by closing the connection. These cut off connections are called [_slow consumers_](../../nats-server/nats_admin/slow_consumers.md).
One way some of the libraries deal with bursty message traffic is to buffer incoming messages for a subscription. So if an application can handle 10 messages per second and sometimes receives 20 messages per second, the library may hold the extra 10 to give the application time to catch up. To the server, the application will appear to be handling the messages and consider the connection healthy. Most client libraries will notify the application that there is a SlowConsumer error and discard messages.