wa-automate-nodejs VS omnistreams-spec

Love your hybrid model via gumroad! I do something similar for my own open-source project

https://github.com/open-wa/wa-automate-nodejs

There should be some sort of support group for those of us trying to monetize (sans donations) our open source projects!

if you can program in Node.js, or have an basic knowledge of javascript or are motivated to learn Node.js, then I would recommend looking at https://github.com/open-wa/wa-automate-nodejs

You can use a platform like otechie. There people are required to put in their card details before starting a conversation. This is what I do with open-wa (https://github.com/open-wa/wa-automate-nodejs#support)

Because I sell license keys to unlock features, it allows me to provide generalized support and quick bug fixes via the discord. If people need help with integration in their specific code base then that's when I ask them to go through the "consulting route" - if it's quick they use otechie. If it's more involved (1+ days) then we work out a contract arrangement.

I hardly get any clients through these means but it does put a clear value on my time which results in the community appreciating the time and effort into the project and the real time support (via discord).

My personal WebSockets vs SSE TL;DR goes something like this:

* If you're on HTTP/2, start with SSE

* If you need to send binary data, use WebSockets

* If you need fast bidi streaming, use WebSockets

* If you need backpressure and multiplexing for WebSockets, use RSocket or omnistreams[1] (one of my projects).

[0]: https://rsocket.io/

[1]: https://github.com/omnistreams/omnistreams-spec

I built omnistreams[0] primarily because of the lack of backpressure in browser WebSockets (lots of background information in that README). It's what fibridge[1] is built on. We've been using it in production for over 2 years, but I never ended up trying to push omnistreams as a thing. I believe the Rust implementation is actually behind the spec a bit, and the spec itself probably needs some work.

At the end of the day I think RSocket is probably the way to go for most people, though the simplicity of omnistreams is still appealing to me.

[0]: https://github.com/omnistreams/omnistreams-spec

[1]: https://iobio.io/2019/06/12/introducing-fibridge/