fatchan
NATS
fatchan | NATS | |
---|---|---|
2 | 108 | |
73 | 14,990 | |
- | 1.3% | |
0.0 | 9.8 | |
almost 11 years ago | about 6 hours ago | |
Go | 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.
fatchan
-
communicate across network using go channels
For funzies I implemented this back in the old days: fatchan
- Question about unsafe channels across multiple programs [horrible idea]
NATS
-
HN-text: an easy-to-use, text-first Hacker News terminal client
That sounds awesome. I have actually been working on something similar myself. I have been building a distributed NATS[0] cluster to funnel data down from the internet and index it locally. I also have a local Ollama box wired up to try to do some NLP on it.
I started with Benthos to pull in, but since the recent license changes[1] I am rethinking that :(
If you would like to collaborate feel free to shoot me an email!
[0] https://nats.io/
[1] https://news.ycombinator.com/item?id=40537911
- Hello World, Simple Event Broker
-
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/
What are some alternatives?
netchan - Go channels "multiplexed" on top of TCP-like connections.
celery - Distributed Task Queue (development branch)
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
redpanda - Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM!
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
Apache ActiveMQ - Mirror of Apache ActiveMQ
nsq - A realtime distributed messaging platform
Apache Kafka - Mirror of Apache Kafka
mosquitto - Eclipse Mosquitto - An open source MQTT broker
kubemq-community - KubeMQ is a Kubernetes native message queue broker
nanomsg - nanomsg library
BeanstalkD - Beanstalk is a simple, fast work queue.