Generalized Javascript graph-based hierarchical programming and microservice architecture. Focus on BIGGER problems using self-configuring graph networks for simple or complex remote and local execution pipelining. Servers, workers, rendering, the works.
I have skimmed the example and I think it is a decent architecture. I wonder though whether the system is designed for high-throughput and modestly low-latency (in both directions) and could be thus used to stream real-time video to subscribers and vice versa (new video coming from subscribers and save it to HDD at the backend side).
Is this somehow possible? Or are there any known (i.e. "by design") bottle necks (e.g. due to compression, superfluous copying of data, synchronous messaging leading to random delays, ...)?