mirror of
https://github.com/taigrr/nats.docs
synced 2025-01-18 04:03:23 -08:00
incorporating comments
This commit is contained in:
parent
2b9b05ce2d
commit
4b0ec2f7a7
@ -6,5 +6,5 @@ NATS makes it easy for programs to communicate across different environments, la
|
|||||||
|
|
||||||

|

|
||||||
|
|
||||||
NATS core offers an **at most once** quality of service. If a subscriber is not listening on the subject \(no subject match\), or is not active when the message is sent, the message is not received. This is the same level of guarantee that TCP/IP provides. NATS is a fire-and-forget messaging system. It does not store messages on disk. If you need higher levels of service, you can use [NATS Streaming](../nats-streaming-concepts/intro.md) or build additional reliability into your client applications with proven and scalable reference designs such as [acks](acks.md) and [sequence numbers](seq_num.md).
|
NATS core offers an **at most once** quality of service. If a subscriber is not listening on the subject \(no subject match\), or is not active when the message is sent, the message is not received. This is the same level of guarantee that TCP/IP provides. Core NATS is a fire-and-forget messaging system, will only hold messages in memory and will never write messages directly to disk. If you need higher levels of service, you can use [NATS Streaming](../nats-streaming-concepts/intro.md) or build additional reliability into your client applications with proven and scalable reference designs such as [acks](acks.md) and [sequence numbers](seq_num.md).
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user