Who has experience with nats.io?

I want to make farma servers (Go) send events to NATS, and have other services (like the nodejs pingem frontend subscribe to these events).

Anything I should be aware of or be careful with?

Dad, geek, conversation liquidity provider. vrypan.net (home), @l--o--l (fun). devcoin:$lemon3

do you/team understand data streaming, delivery configs/guarantees and consumer clients well? even if you wrote a kafka consumer historically, same principles will help design/debug/think about nats.

"do you understand" has a wide range of meanings, I'd say I have a decent understanding of the concepts and how they work in practice.

Every service involved is run and developed by me, which makes things easier and the environment more trusted.

I played with Server Side Events in the last couple of days, and it works, but there are too many things that I would have to implement on my side to make this reliable, so I thought using something like NATS would let me get access to them for free, and much more.

GitHub.com/vrypan/farma is a farcaster notification server. To make it easy to deploy and use, I use an embedded BadgerDB, and everything works fine. Think sendmail for Farcaster notifications.

pingem.xyz is a hosted frontend to a hosted Farma instance. Accessing the data in the farma KV store and performing complex queries is practically impossible, so I want Farma to be able to send events (user added/removed miniapp, user enable/disabled notifications, etc.) to pingem and let pingem store them in an RDBMS.

A NATS setup seems like it will also open the door to easy clustering farma servers, implementing stats easier, etc.

not sure if you can share usecase, is this for a decentralized network eg ai infra or bitcoin rigs? nats works great when you don't own/run all nodes. if its all "internally" run/maintained nodes then it is helpful but can be skipped (maybe, b/c large overhead; redis works fine too)