At a minimum I envision the stream to go to a background process.
But if there are options available. There should be a way of pushing to a message queue like nats.io. I’m sure others would want zeromq, rabbitmq, kafka, etc. That would then allow for multiple background processes waiting. Which would also solve redundancy issues.
So in my case it would be a golang executable reading the stream. Which contains logic that depending on what happens, it would then create another job to execute a process or send something to the FE.
Having this ability makes the process fully reactive. Rather than having another golang executable hitting a table every second and checking to see if conditions are met. Which is something I’m actually doing now for my job queue ://
The more I think about it. Having a stream is the holy grail for me lol. There’s so much that I could do with it!
Even something like this lol: https://rxdb.info/
Hopefully all this makes sense.