leviathan is not horizontally scalable

[RA341]

Feature request

---

leviathan holds some internal state such as cancel funcs and broadcast channels to steam updates, and therefore cannot be correctly horizontally scaled

This way does not allow us to spin up 2 identical instances of leviathan

While leviathan is fast enough, a single instance more than enough for devu use case.

this could be a issue, if we want backup instances ready to go in case of failure

[RA341]

potential fix is to use unix sockets as a way to stream changes, instead of go channels

or

remove streaming entirely and use normal polling