mosquitto
NATS
Our great sponsors
mosquitto | NATS | |
---|---|---|
49 | 106 | |
8,388 | 14,766 | |
2.2% | 2.4% | |
6.5 | 9.8 | |
3 days ago | about 24 hours ago | |
C | Go | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mosquitto
-
SObjectizer Tales - Epilogue
mosquitto_transport, an experiment of writing SObjectizer-based wrapper around mosquitto library;
-
Beginner IoT project: LED Web trigger
References: Felipe Flop’s website https://www.filipeflop.com/blog/controle-monitoramento-iot-nodemcu-e-mqtt/ accessed on 01/27/2018. Eclipse server for MQTT Broker https://iot.eclipse.org/ accessed on 01/27/2018. Mosquitto https://mosquitto.org/ accessed on 01/27/2018. Cloud MQTT https://www.cloudmqtt.com/ accessed on 01/27/2018. DuckDNS https://www.duckdns.org/ accessed on 01/27/2018. Proftpd http://www.proftpd.org/ accessed on 01/27/2018. Filezilla https://filezilla-project.org/ accessed on 01/27/2018. Fritzing https://fritzing.org/ accessed on 05/25/2022. Appendices:
-
Synchronize 25 ESP8266 to start playback of an audio file at the same time
This is a perfect use case for MQTT, e.g. this library for ESP boards. Create a broker on the network (e.g. a Raspberry Pi running Mosquitto, and have all the ESP boards subscribe to a topic. When you want to play a sound, publish a message to the topic, and all of the ESPs should see it very quickly. You don't need to synchronize clocks any more because it's simply based on the timing of publishing a message.
-
Forward Compatibility for Mosquitto MQTT Broker with Docker Compose v2
While working on a personal project Komponist, I was due to update Mosquitto MQTT Broker due to a CVE and found some interesting changes that will impact me in the future when it comes to configuring the Broker. This post provides a solution to make the Broker compatible with future versions using new and less visited concepts in Docker Compose v2, namely:
-
An AsyncAPI Example: Building Your First Event-driven API
Optional: Mosquitto, an open-source message broker that implements the MQTT protocol; this tutorial uses the public test server
-
A Modern High-Performance Open Source Message Queuing System
I think he means implementation of MQTT protocol, like https://mosquitto.org/
- virtualisation.oci-containers - how can I move away from DockerHub for my image and move to building my own image from Dockerfile on owners repo?
- 7 Best MQTT Client Tools Worth Trying in 2023
- Smart switch contingency?!
-
Need help using Tasmota with Reed sensors on multiple doors
Could MQTT work for you? You'd need a broker like Mosquitto, and then any of a number of MQTT clients.
NATS
-
Implementing OTel Trace Context Propagation Through Message Brokers with Go
Several message brokers, such as NATS and database queues, are not supported by OpenTelemetry (OTel) SDKs. This article will guide you on how to use context propagation explicitly with these message queues.
-
NATS: First Impressions
https://nats.io/ (Tracker removed)
> Connective Technology for Adaptive Edge & Distributed Systems
> An Introduction to NATS - The first screencast
I guess I don't need to know what it is
-
Interview with Sebastian Holstein, Founder of Qaze
During our interview, we referred to NATS quite a few times! If you want to learn more about it, Sebastian suggests this tutorial series.
-
Sequential and parallel execution of long-running shell commands
Pueue dumps the state of the queue to the disk as JSON every time the state changes, so when you have a lot of queued jobs this results in considerable disk io. I actually changed it to compress the state file via zstd which helped quite a bit but then eventually just moved on to running NATS [1] locally.
[1] https://nats.io/
-
Revolutionizing Real-Time Alerts with AI, NATs and Streamlit
Imagine you have an AI-powered personal alerting chat assistant that interacts using up-to-date data. Whether it's a big move in the stock market that affects your investments, any significant change on your shared SharePoint documents, or discounts on Amazon you were waiting for, the application is designed to keep you informed and alert you about any significant changes based on the criteria you set in advance using your natural language. In this post, we will learn how to build a full-stack event-driven weather alert chat application in Python using pretty cool tools: Streamlit, NATS, and OpenAI. The app can collect real-time weather information, understand your criteria for alerts using AI, and deliver these alerts to the user interface.
-
New scalable, fault-tolerant, and efficient open-source MQTT broker
Why wasn't NATS[1] used ?
Written in Go, single-binary deployment... there's a lot to love about NATS !
[1]https://nats.io/
-
Scripting with NATS.io support
require nats.io
-
Introducing “Database Performance at Scale”: A Free, Open Source Book
About cost, see [1]. Also, S3 prices have been increasing and there's been a bunch of alternative offers for object store from other companies. I think people in here (HN) comment often about increasing costs of AWS offerings.
Distributed systems and consensus are inherently hard problem, but there are a lot of implementations that you can study (like Etcd that you mention, or NATS [2], which I've been playing with and looks super cool so far :-p) if you want to understand the internals, on top of many books and papers released.
Again, I never said it was "easy" to build distributed systems, I just don't think there's any esoteric knowledge to what S3 provides.
--
1: https://en.wikipedia.org/wiki/Economies_of_scale
2: https://nats.io/
- NATS: Connective Technology for Adaptive Edge and Distributed Systems
-
Is it an antipattern to use the response channel as identifier
I am in a project were nats.io is used. Someone thought, it would be a great idea to link data in an event with data in a response using the response channel name.
What are some alternatives?
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
Aedes - Barebone MQTT broker that can run on any stream server, the node way
celery - Distributed Task Queue (development branch)
zigbee2mqtt - Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
redpanda - Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM!
hivemq-community-edition - HiveMQ CE is a Java-based open source MQTT broker that fully supports MQTT 3.x and MQTT 5. It is the foundation of the HiveMQ Enterprise Connectivity and Messaging Platform
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
vernemq - A distributed MQTT message broker based on Erlang/OTP. Built for high quality & Industrial use cases. The VerneMQ mission is active & the project maintained. Thank you for your support!
Apache ActiveMQ - Mirror of Apache ActiveMQ
Node RED - Low-code programming for event-driven applications
nsq - A realtime distributed messaging platform