From 4fc4a9bd35175c4a3a7457dd65cc51690d8ae9d3 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Fri, 4 Oct 2019 11:24:37 -0500 Subject: [PATCH] Update intro.md --- developer/concepts/intro.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developer/concepts/intro.md b/developer/concepts/intro.md index 34fc1e1..d1beff5 100644 --- a/developer/concepts/intro.md +++ b/developer/concepts/intro.md @@ -4,6 +4,6 @@ NATS messaging enables the exchange of data that is segmented into messages amon NATS makes it easy for programs to communicate across different environments, languages, cloud providers and on-premise systems. Clients connect to the NATS system, usually via a single URL, and then subscribe or publish messages to subjects. With this simple design, NATS lets programs share common message-handling code, isolate resources and interdependencies, and scale by easily handling an increase in message volume, whether those are service requests or stream data. -![NATS Intro](/assets/images/intro.svg) +![](/assets/images/intro.svg) 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. By default, NATS is a fire-and-forget messaging system. If you need higher levels of service, you can use [NATS Streaming](/nats_streaming/intro.md) or build additional reliability into your client applications with proven and scalable reference designs.