[v3-3-test] Add Task SDK, Go and Java SDK execution architecture diagrams (#69750)#70100
Merged
Conversation
…rams (#69750) * Add Task SDK, Go and Java SDK execution architecture diagrams Add graphviz-generated diagrams to the architecture overview showing how a task actually runs across the different SDKs, and embed them in core-concepts/overview.rst: - Python Task SDK: supervised (two native OS processes over a msgpack socket) vs native/in-process paths, plus a numbered message-flow sequence. - Go SDK: standalone edge worker pulling from the Edge API, task talks to the Execution API directly. - Java (JVM) SDK: Coordinator layer reusing the Python Supervisor, driving a JVM subprocess over loopback TCP, with an architecture diagram and a numbered execution-workflow sequence. * Draw Task and Java SDK execution flows as true sequence diagrams The message-flow diagrams added earlier in this PR drew every step on a single vertical spine, so the request/response round-trips between the task runtime and the Supervisor were hard to follow. Responding to review feedback, redraw them as true sequence diagrams — one lifeline per participant with the Supervisor in the middle — so each round-trip reads as arrows going back and forth between neighboring lifelines, with straight message arrows and margined labels. (cherry picked from commit 2de0223) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
1 task
potiuk
marked this pull request as ready for review
July 19, 2026 16:49
Contributor
Author
|
Hi maintainer, this PR was merged without a milestone set.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add graphviz-generated diagrams to the architecture overview showing how a
task actually runs across the different SDKs, and embed them in
core-concepts/overview.rst:
vs native/in-process paths, plus a numbered message-flow sequence.
Execution API directly.
JVM subprocess over loopback TCP, with an architecture diagram and a numbered
execution-workflow sequence.
The message-flow diagrams added earlier in this PR drew every step on a single
vertical spine, so the request/response round-trips between the task runtime and
the Supervisor were hard to follow. Responding to review feedback, redraw them
as true sequence diagrams — one lifeline per participant with the Supervisor in
the middle — so each round-trip reads as arrows going back and forth between
neighboring lifelines, with straight message arrows and margined labels.
(cherry picked from commit 2de0223)
Co-authored-by: Jarek Potiuk jarek@potiuk.com