News for hackers. Stuff that matters.
Re:Waltz: A Distributed Write-Ahead Log by zcw100 on Monday September 09, 2019 @06:38PM (#20923262)
Re:Waltz: A Distributed Write-Ahead Log by manigandham on Monday September 09, 2019 @07:14PM (#20923549)
Note that NATS on it's own is just a pub/sub system and doesn't have any queuing or persistence. There is no "log". You need the NATS Streaming server for that which implements persistence while communicating over NATS.
Re:Waltz: A Distributed Write-Ahead Log by afrodc_ on Monday September 09, 2019 @07:34PM (#20923686)
I was looking into https://github.com/liftbridge-io/liftbridge. I believe he was a maintainer of NATS streaming and wanted to make something lightweight and Kafka-esque.
Re:Waltz: A Distributed Write-Ahead Log by corford on Monday September 09, 2019 @08:37PM (#20924068)
Liftbridge looks cool but right now you need use their protobuf defs and cook your own client lib if you want bindings outside of go.
Re:Waltz: A Distributed Write-Ahead Log by manigandham on Monday September 09, 2019 @08:50PM (#20924122)
Liftbridge is an experiment and has no real production users. NATS Streaming is already fine for lightweight single-host usage. If you really need to scale to multiple servers then I recommend skipping NATS Streaming and going straight to Kafka or Apache Pulsar.
Re:Waltz: A Distributed Write-Ahead Log by dmix on Tuesday September 10, 2019 @01:59AM (#20925435)
Have any more lighter-weight recommendations that fit the queuing and persistence category?
Re:Waltz: A Distributed Write-Ahead Log by manigandham on Tuesday September 10, 2019 @07:37PM (#20935060)
RabbitMQ is another option. Clustering is fragile, but it's fine if you just need a single-node: https://www.rabbitmq.com/

There are also proprietary systems like Solace: https://solace.com/

Other than that, there are embedded queuing/log libraries or you can just dump the messages into a key/value store or write them out to a file yourself.