2 ms·
So it sounds like you're using the service communication to mean the stream? Although "toward the original caller" suggests that two inter communicating servic
by gnabgib 5y ago
So it sounds like you're using the service communication to mean the stream? Although "toward the original caller" suggests that two inter communicating services would be flip-flopping for ownership of "upstream". Aardvark calls Bear, Aardvark is upstream, Bear calls Aardvark.. Bear is upstream.
Stream could also refer to data (upstream=original/raw, downstream=processed/final), the overall process stage (upstream=prior stage, downstream=next stage - this requires knowledge of the system architecture, the stage boundaries are likely business-defined), some business term (eg in energy upstream=energy producer, downstream=consumer). A stream and the messaging direction may not match.
- tyingq 5y agoI agree with that, but in this case, the author had already scoped it down to services calling other services in a "microservices" context. And even if the call graph is a->b->c->a->b, I can still say up/down if I give the context of which invocation. I'm hoping people don't do that much in real life though, too easy to recurse.