nats-streaming-server | NATS Streaming System Server | Websocket library

 by   nats-io Go Version: v0.25.3 License: Apache-2.0

kandi X-RAY | nats-streaming-server Summary

kandi X-RAY | nats-streaming-server Summary

nats-streaming-server is a Go library typically used in Networking, Websocket applications. nats-streaming-server has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

NATS Streaming is an extremely performant, lightweight reliable streaming platform built on NATS.

            kandi-support Support

              nats-streaming-server has a medium active ecosystem.
              It has 2455 star(s) with 288 fork(s). There are 84 watchers for this library.
              It had no major release in the last 12 months.
              There are 55 open issues and 574 have been closed. On average issues are closed in 90 days. There are 1 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of nats-streaming-server is v0.25.3

            kandi-Quality Quality

              nats-streaming-server has 0 bugs and 0 code smells.

            kandi-Security Security

              nats-streaming-server has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              nats-streaming-server code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              nats-streaming-server is licensed under the Apache-2.0 License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              nats-streaming-server releases are available to install and integrate.
              It has 53272 lines of code, 1738 functions and 73 files.
              It has high code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of nats-streaming-server
            Get all kandi verified functions for this library.

            nats-streaming-server Key Features

            No Key Features are available at this moment for nats-streaming-server.

            nats-streaming-server Examples and Code Snippets

            No Code Snippets are available at this moment for nats-streaming-server.

            Community Discussions


            Testing NATS-streaming in Kubernetes with minimal effort
            Asked 2021-May-10 at 08:52

            I wanted to test a very basic application for NATS-streaming on Kubernetes. To do so, I followed the commands from the official NATS-docs.

            It basically comes down to running



            Answered 2021-May-10 at 08:52


            What message persistence guarantee NATS streaming provides in cluster and FT modes?
            Asked 2020-Nov-18 at 15:48

            I'm looking for a streaming server with the message persistence guarantee, i.e. where the messages published by producers are guaranteed to be durably stored before the server acknowledges publishing to the producer.

            My use case requires that we reduce the possibility of losing any produced messages. Producers are able to replay messages if required but they need to be sure that the ACKed message is durably persisted and will be delivered by the streaming server to the consumers.

            NATS Streaming server seems to do something along those lines, but the docs for clustering and fault tolerance don't make it very clear what persistence guarantee is provided in each case. The doc on producer integration confirms that the server will actively ACK the published messages, either synchronously or via callback, but it does not make it clear if the ACK means that the message was durably stored at this point or not yet.

            The doc on store configuration, specifically SQL options briefly mentions that the ACK from the server means a durable storage guarantee, but it's not clear still how exactly that applies in cases of Clustering and Fault Tolerance and different persistence backends (files or SQL).



            Answered 2020-Nov-18 at 15:48

            NATS Streaming will have persisted the message before sending the publisher ACK back. The store implementations (filestore/SQL) may use some caching, but regardless, the writes are sync'ed (unless disabled) before the ACK is sent back.

            However, in cluster mode, the filestore sync'ing is disabled because we rely on the fact that the data is replicated to each node of the cluster and so you would need multiple failures at once to lose the message. (note that there is an option for file store implementation to perform auto-sync at regular interval: see auto_sync here


            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install nats-streaming-server

            You can download it from GitHub.


            Official documentation
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
          • HTTPS


          • CLI

            gh repo clone nats-io/nats-streaming-server

          • sshUrl


          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Explore Related Topics

            Consider Popular Websocket Libraries


            by netty


            by websockets


            by gorilla


            by joewalnes


            by koel

            Try Top Libraries by nats-io


            by nats-ioGo


            by nats-ioGo


            by nats-ioJavaScript


            by nats-ioRuby


            by nats-ioRust