I don’t wish to be rude. But you have just constructed a straw man and attacked it.
I never mentioned subscriptions. The original question had nothing to do with subscriptions.
That should be absolutely obvious and I’m sorry that it is not. Maybe because the conventional thinking is too narrow [with established users of dgraph] and I, still being new to Dgraph can think more outside of the box.
I doubt the facility exists right now. So let me be clear.
I would like to see in a future iteration of Dgraph. That it is websocket first. Especially looking at the future with web3 technologies.
Why use HTTP when websocket can be used?
Note to the devs, there is an awesome library called centrifugo it’s written in go as well. Perhaps a possibility exists where a more extensive websocket server exists within Dgraph allowing for more exotic features?