Lets add a NATS provider

[gedw99]

NATS is similar to Kafka but 100% golang and not needing zoo keeper etc to scaleout.

Here is the API: https://github.com/nats-io/nats.go/tree/main/jetstream

The Server which can also be embedded: https://github.com/nats-io/nats-server

Here is an example of embedding the Nats Server: https://github.com/maxpert/marmot/blob/master/stream/embedded_nats.go

[tmaxmax]

Hello and thank you for the proposal!

One thing that I'd like to iron out before implementing new providers is a way to add these new provider modules without polluting the go.mod of users which do not use them. For example, someone who doesn't use the NATS provider shouldn't have github.com/nats-io/nats as a dependency. This shouldn't be too difficult to come up to with a solution – something we could do is create an organisation named go-sse, in which the main sse module would be under github.com/go-sse/sse, and providers would be under github.com/go-sse/ssenats, for example.

Apart from that, would you be down to implement a quick prototype, especially if you have a use case for NATS + SSE now? We can review it together and see what rough edges around it and go-sse aswell we can refine. It would help to have a new programmer with fresh eyes use and review the interfaces inside go-sse, as there may be important things missing or that need to be improved. There is no time pressure – make it fit comfortably in your personal schedule, if you wish to work on it! In the meantime, I will familiarize myself with NATS, as I haven't heard of it before.

Lastly, if you have an use-case for NATS + SSE, would you mind sharing it here? I'd be curios to hear how you'd like to use go-sse, and see if there's anything needed to better accomodate the use-case.

Again, thank you for chiming in here – I'm eagerly waiting for your response and, of course, a result!

[gedw99]

Hello and thank you for the proposal!

One thing that I'd like to iron out before implementing new providers is a way to add these new provider modules without polluting the go.mod of users which do not use them. For example, someone who doesn't use the NATS provider shouldn't have github.com/nats-io/nats as a dependency. This shouldn't be too difficult to come up to with a solution – something we could do is create an organisation named go-sse, in which the main sse module would be under github.com/go-sse/sse, and providers would be under github.com/go-sse/ssenats, for example.

agree its a good idea to not bloat the go-mod.

I don't think you need another repo.
Instead, just use this current repo and make it a mono repo using go-work: https://blog.logrocket.com/go-workspaces-multi-module-local-development/ will work.
CI and CD still works.

https://github.com/streamdal/plumber is work looking at btw. Just to see some of the approaches they used as they support many "providers" of Message brokers. Might be some tips from that.

Apart from that, would you be down to implement a quick prototype, especially if you have a use case for NATS + SSE now? We can review it together and see what rough edges around it and go-sse aswell we can refine. It would help to have a new programmer with fresh eyes use and review the interfaces inside go-sse, as there may be important things missing or that need to be improved. There is no time pressure – make it fit comfortably in your personal schedule, if you wish to work on it! In the meantime, I will familiarize myself with NATS, as I haven't heard of it before.

Yep can help.

You can use hosted NATS BTW for free to make trying it out easy. https://www.synadia.com/ngs

www.synadia.com make NATS btw...

Lastly, if you have an use-case for NATS + SSE, would you mind sharing it here? I'd be curios to hear how you'd like to use go-sse, and see if there's anything needed to better accomodate the use-case.

I have a plethora of use cases with NATS and SSE.
You can run nats.go in a browser as WASM, but its a bit heavy. And your are not so agnostic.
Also its not agnostic !! that's really the big one for me.

Some ideas i have are:

• Browser and bun Web workers and Main thread separated and passing data diffs. Data diffs are needed for speed, because you only moving the diff between the 2 barriers. otherwise its slow. SSE can be used to pass the diffs basically.

• Between a Browser Service worker and backend golang Server. You want to send events from the server to the Service worker in the browser. The Service worker can be in gaoling wasm and can be an exact copy of the golang on the server.

• Between Backends you want to send events. SSE works well enough.

• Mobile and Desktop apps using gioui. https://github.com/gioui/gio-example is a golang GUI that works on Web, Desktop and Mobile, and so go-see can be its event transport.

• The main one is to make a golang htmx, using go-sse. Here is a golang example that uses htmx.js. https://github.com/acaloiaro/hugo-htmx-go-template

Again, thank you for chiming in here – I'm eagerly waiting for your response and, of course, a result!