exhibitor
NATS
exhibitor | NATS | |
---|---|---|
6 | 106 | |
8 | 14,846 | |
- | 1.7% | |
6.8 | 9.8 | |
almost 1 year ago | 4 days ago | |
TypeScript | Go | |
MIT License | 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.
exhibitor
-
Ask HN: Most interesting tech you built for just yourself?
TL;DR: A React front-end component workshop, a simple version of Storybook.
So around 5 months ago, I needed a tool to preview front-end (React) components whilst I create them for a personal project of mine. There were two options: Storybook or Ladle.
Storybook is the tool everybody knows. I've used it before quite a lot. It's very big, full-fat, supports loads of use-cases, etc.
Ladle comes out of Uber. It's very small, lean, and doesn't support that much. After trying it out for a while, it just gives me a feeling like it's a 20% project to learn some new tech.
So I realised that I wanted something kind of in the middle. Something that's a bit more customizable than Ladle, but something much simpler and less intrusive than Storybook.
This led me to create Exhibitor (https://github.com/samhuk/exhibitor) (https://demo.exhibitor.dev).
I worked on it on-and-off for a couple months, and it ended up being something that I'm quite proud of. It's not perfect, and supports only a fraction of what Storybook does, however for a tool made by 1 engineer vs the 20+ for Storybook, I'm quite happy about it!
-
Show HN: Exhibitor – Snappy and delightful React component workshop
Exhibitor, a snappy & delightful React component workshop, is GA. My aim is for Exhibitor to be an extremely fast, easy to use, and delightful tool for creating front-end component libraries.
It's been around 2 months since my last mention and quite a tonne has changed.
Wiki: https://github.com/samhuk/exhibitor/wiki
-
Show HN: DriftDB is an open source WebSocket back end for real-time apps
Looks interesting. Coincidentally, I've just completed the bulk of work on a distributed Websocket network system to synchronize certain bits of state between multiple clients for my own kind of Storybook tool [0]. How interesting!
This kind of tool is exactly what I would have needed, instead of the approach I've taken which is a bit kludgy, grass-roots, novice-like, etc.
Good work :)
[0] https://github.com/samhuk/exhibitor/pull/22
-
Ask HN: What have you created that deserves a second chance on HN?
I was a bit deflated when my submission about https://github.com/samhuk/exhibitor fell through the HN floor-boards.
Think Storybook but simpler, faster, better Typescript support, and uses esbuild by default.
...Is the aim. I'm the sole lead dev working on it at the moment up against the ~10-20 strong team who built most of Storybook, so it's a long road ahead, but it's growing into something I'm quite proud of and happy about.
- Show HN: Exhibitor – Snappy, no-fuss, delightful React component workshop
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?
epub2tts - Turn an epub or text file into an audiobook
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
MLVPN - Multi-link VPN (ADSL/SDSL/xDSL/Network aggregation / bonding)
celery - Distributed Task Queue (development branch)
scheme-for-max - Max/MSP external for scripting and live coding Max with s7 Scheme Lisp
redpanda - Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM!
mqtt-to-kafka-bridge - Move your messages from MQTT to Apache Kafka in real-time :rocket:
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
brethap
Apache ActiveMQ - Mirror of Apache ActiveMQ
ratarmount - Access large archives as a filesystem efficiently, e.g., TAR, RAR, ZIP, GZ, BZ2, XZ, ZSTD archives
nsq - A realtime distributed messaging platform