<a href="https://nats.io/" rel="nofollow">https://nats.io/</a> (Tracker removed)<p>> Connective Technology for Adaptive Edge & Distributed Systems<p>> An Introduction to NATS - The first screencast<p>I guess I don't need to know what it is
Does according to author, NATS is less reliable, if you want guaranteed ordering and to have multiple instances of worker, because NATS partitions lack "auto-balance" like in Kafka?<p>I would assume that NATS can be deployed in some Kubernetes cluster, so it
would not be uncommon to have 3 or 5 workers. In this case, what would happen, if someone wanted guaranteed ordering and used that deterministic subject token partitioning?<p>Let's assume that some worker would crash due to lack of storage space and it would keep restarting, so what happens to messages on this partition? Can they be processed, if specific worker is not available? Is it possible to react to this event and manually reassign these partitions to other workers? In case that there's no event, then maybe it's possible to write some script and run CronJob to manually check, if rebalance is needed?
A feature not covered in this article that I recently learned about is republishing[0]. This is super useful, because it lets you essentially "namespace" parts of the network. You can use very short subject names for an isolated part of the network, and then republish to a more specific name as it gets pushed out to a larger network.<p>[0] <a href="https://docs.nats.io/nats-concepts/jetstream/streams#republish" rel="nofollow">https://docs.nats.io/nats-concepts/jetstream/streams#republi...</a>
Here in my company we're running load tests against a POC application using NATS, and we're afraid that it can't handle some spikes in load that well. In some tests rounds the loss rate was a bit high. But I can't say if it's a NATS issue or our tests aren't well dimensioned.