KFJ 🇦🇹 🇪🇺
Preslav Rachev@kfj I assume, you’re looking for something resembling the Actor model? BTW, there are channels and goroutines at play in the depths of the HTTP server. It’s just that most of the time you don’t need the raw access.
@preslavrachev pretty much that. I somehow assume with my limited Go day 4 knowledge, that it might be much easier to run servers that interconnect several external sources asynchronously without a known time of response arrival.
Adam@kfj @preslavrachev what might this middleware do, asynchronously to the requested?
For the most part go is simple and more than fast enough
@adam_straughan @preslavrachev the thought wasn't that much about speed, but about the different times when an external source might return data.
@adam_straughan @preslavrachev the thought also was a out separately handling things that belong to some subtask. Like subrouters or scoped sub-tasks of a request. Think main Middleware set handles from Auth to throttling, cors, csrf etc and then there happens to be side-channels that start handling data flowing to or from various, unconnected systems, where no one cares about order.
@adam_straughan @preslavrachev An answer like "doesn't make sense, total overhead, hard to control" is ok. I am just looking at all the new shiny Go stuff and wonder what people already tried and why they left some routes untouched.