Meta tags:

Headings (most frequently used words):

-

Text of the page (most frequently used words):
nats (23), the (21), and (15), you (13), documentation (10), for (7), this (7), page (6), your (6), jetstream (6), with (6), https (5), data (5), that (5), concepts (5), goal (5), docs (4), are (4), using (4), delivery (4), can (4), need (4), gitbook (4), available (3), services (3), language (3), once (3), request (3), security (3), additional (3), slack (3), query (3), question (3), ask (3), answer (3), llms (2), txt (2), markdown (2), readme (2), secure (2), high (2), open (2), source (2), messaging (2), feel (2), should (2), between (2), what (2), platform (2), messages (2), most (2), patterns (2), supported (2), persistence (2), key (2), value (2), versioning (2), object (2), jwt (2), zero (2), trust (2), configuration (2), trying (2), core (2), store (2), when (2), directly (2), more (2), learn (2), from (2), not (2), get (2), current (2), parameter (2), optional (2), complete, index, see, versions, pages, appending, urls, welcome, official, simple, performance, layer, cloud, native, applications, iot, microservices, architectures, backbone, communication, doesn, matter, protocol, best, way, connect, 000, foot, view, publish, subscribe, millions, per, second, supports, fan, out, reply, every, major, via, least, exactly, work, queues, stream, processing, replication, retention, deduplication, higher, order, structures, watchers, ttl, storage, tls, based, clustering, availability, fault, tolerance, auto, discovery, protocols, tcp, mqtt, websockets, all, single, binary, easy, deploy, manage, external, dependencies, just, drop, add, file, point, other, servers, ready, fact, even, embed, application, users, guided, tour, general, recommend, solve, problems, first, share, state, take, look, obj_store, lower, level, access, streams, move, advanced, about, deployment, strategies, service_infrastructure, adaptive_edge_deployment, deployments, running, service, securing_nats, auth_intro, contribute, please, let, know, mailto, info, have, updates, suggestions, these, also, create, pull, edit, github, link, each, questions, free, chat, thank, entire, team, maintainers, interest, agent, instructions, published, designed, both, humans, agents, read, navigate, reason, over, technical, content, effectively, com, querying, information, dynamically, asking, perform, http, url, immediate, specific, self, contained, written, natural, describes, broader, end, ultimately, accomplish, behalf, user, uses, tailor, towards, useful, response, will, contain, direct, relevant, excerpts, sources, use, mechanism, explicitly, present, clarification, context, want, retrieve, related, sections,

Text of the page (random words):
for the complete documentation index see llms txt https docs nats io llms txt markdown versions of documentation pages are available by appending md to page urls this page is available as markdown https docs nats io readme md welcome the official nats https nats io documentation nats is a simple secure and high performance open source data layer for cloud native applications iot messaging and microservices architectures we feel that it should be the backbone of your communication between services it doesn t matter what language protocol or platform you are using nats is the best way to connect your services 10 000 foot view publish and subscribe to messages at millions of messages per second at most once delivery supports fan in out delivery patterns request reply every major language is supported persistence via jetstream at least once delivery or exactly once delivery work queues stream processing data replication data retention data deduplication higher order data structures key value with watchers versioning and ttl object storage with versioning security tls jwt based zero trust security clustering high availability fault tolerance auto discovery protocols supported tcp mqtt websockets all of this in a single binary that is easy to deploy and manage no external dependencies just drop it in and add a configuration file to point to other nats servers and you are ready to go in fact you can even embed nats in your application for go users guided tour 1 in general we recommend trying to solve your problems first using core nats nats concepts core nats md 2 if you need to share state between services take a look at the kv nats concepts jetstream key value store md or object store nats concepts jetstream obj_store md in jetstream 3 when you need lower level access to persistence streams move on to using jetstream nats concepts jetstream md directly for more advanced messaging patterns 4 learn about deployment strategies nats concepts service_infrastructure adaptive_edge_deployment md 5 secure your deployments with zero trust security running a nats service configuration securing_nats auth_intro jwt md contribute nats is open source as is this documentation please let us know mailto info nats io if you have updates and or suggestions for these docs you can also create a pull request using the edit on github link on each page additional questions feel free to chat with us on slack slack nats io https slack nats io thank you from the entire nats team of maintainers for your interest in nats agent instructions this documentation is published with gitbook gitbook is the documentation platform designed so that both humans and ai agents can read navigate and reason over technical content effectively learn more at gitbook com querying this documentation if you need additional information that is not directly available in this page you can query the documentation dynamically by asking a question perform an http get request on the current page url with the ask query parameter and the optional goal query parameter get https docs nats io readme md ask goal ask is the immediate question it should be specific self contained and written in natural language goal is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user gitbook uses it to tailor the answer towards what is most useful for that goal the response will contain a direct answer to the question and relevant excerpts and sources from the documentation use this mechanism when the answer is not explicitly present in the current page you need clarification or additional context or you want to retrieve related documentation sections