[v3-3-test] Add Task SDK, Go and Java SDK execution architecture diagrams (#69750)

airflow-core/docs/core-concepts/overview.rst

@@ -192,6 +192,91 @@ code is never executed in the context of the *scheduler*.
     bundle version when dispatching each task. If needed, the cadence of sync and scan
     of the *Dag bundle* can be configured.
 
+Task execution architecture
+---------------------------
+
+The diagrams above show how Airflow's components are *deployed*. The diagrams below instead show what happens
+*inside a worker when a task actually runs* — how the Task SDK, the Supervisor and Coordinator processes, and
+the language runtimes work together: which processes are involved, and the classes and protocols they use to
+communicate.
+
+.. _overview-task-sdk-execution-architecture:
+
+Python Task SDK execution
+.........................
+
+When a *worker* actually runs a task, it does not run the user's code directly. Instead it starts a
+lightweight **Supervisor** that runs in its own **native operating-system process** and
+*forks* a second native process in which the **Task SDK** runtime (``task_runner``) executes the user code.
+The two processes talk over a socket, and the Supervisor is the only side that ever holds the short-lived
+task JWT or talks to the *Execution API* — the user's code never sees the token and never touches the
+database.
+
+The same runtime can also run *in-process* (a single Python process, no fork, no sockets, no HTTP) for
+``dag.test()`` and local runs. The diagram below contrasts the two paths and marks where each Python process
+lives:
+
+.. image:: ../img/diagram_task_sdk_execution_architecture.png
+
+The message flow of a supervised run — startup, running the user code, proxied Connection/Variable/XCom
+lookups, heartbeats, and reporting the final state — is shown below as a sequence diagram, with each process
+on its own lifeline. The **Supervisor** sits in the middle, so the Task ↔ Supervisor request/response
+round-trip (the task asks for a Connection/Variable/XCom and gets the answer back) reads as arrows going back
+and forth between neighboring lifelines. Each arrow is numbered, colored by its sender, and labeled with the
+message class or protocol used:
+
+.. image:: ../img/diagram_task_sdk_execution_sequence.png
+
+.. _overview-non-python-language-sdks:
+
+Non-Python language SDKs (Go and Java)
+......................................
+
+The Task Execution Interface (TEI) introduced in AIP-72 is language-agnostic, so a task can also be written in
+a **compiled, non-Python language**. A Python Dag still declares the task with ``@task.stub(queue=...)`` (so
+Python and non-Python tasks can be mixed in one Dag), but the actual work is delegated to the matching runtime.
+There are currently **two different integration styles** — the Go SDK runs a standalone worker, while the Java
+SDK plugs into the existing Python Supervisor.
+
+.. _overview-go-sdk-architecture:
+
+**Go SDK — standalone edge worker.** The `Go Task SDK
+<https://github.com/apache/airflow/blob/main/go-sdk/README.md>`_ has **no Python Supervisor and no msgpack
+stdin socket**. A long-running, compiled **edge worker** (``airflow-go-edge-worker``) *pulls* work from the
+**Edge Executor API**, launches the user's compiled Dag bundle as a **go-plugin (gRPC) subprocess**, and
+invokes the task over gRPC. The task then uses the **native TEI client** to reach the **Execution API**
+directly over HTTPS — so, unlike the Python task, it holds the task JWT itself:
+
+.. image:: ../img/diagram_native_language_sdk_architecture.png
+
+.. _overview-java-sdk-architecture:
+
+**Java (JVM) SDK — Coordinator plugged into the Supervisor.** The `Java Task SDK
+<https://github.com/apache/airflow/blob/main/java-sdk/README.md>`_ takes the opposite approach: it *reuses* the
+existing Python Supervisor through a new **Coordinator** layer. ``CoordinatorManager`` resolves the task's
+``queue`` to a ``BaseCoordinator`` — ``JavaCoordinator`` for the ``java`` queue, or the built-in
+``_PythonCoordinator`` otherwise. ``JavaCoordinator`` opens two loopback-TCP servers, spawns a **JVM bundle
+process** with ``subprocess.Popen``, and drives it with ``_JavaActivitySubprocess`` (a subclass of the shared
+``ActivitySubprocess``). The JVM connects *back* over TCP and speaks the **same msgpack protocol** as a Python
+task, so the Python side heartbeats, manages state, and **proxies every Execution-API call** — meaning the JVM
+task, like a Python task, never holds the task JWT itself:
+
+.. image:: ../img/diagram_java_sdk_execution_architecture.png
+
+The end-to-end workflow of a Java task — from ``@task.stub`` through the coordinator, the JVM subprocess, the
+proxied Connection/Variable/XCom lookups, and reporting the final state — is shown below as a sequence diagram.
+As above, the **Supervisor** is the central lifeline, so the JVM ↔ Supervisor round-trip over loopback TCP is
+drawn as arrows going back and forth to its neighbours:
+
+.. image:: ../img/diagram_java_sdk_execution_sequence.png
+
+.. note::
+
+    Both the Go and Java SDKs are **experimental** and under active development. See the `Go Task SDK
+    documentation <https://github.com/apache/airflow/blob/main/go-sdk/README.md>`_ and the `Java Task SDK
+    documentation <https://github.com/apache/airflow/blob/main/java-sdk/README.md>`_ for current status,
+    quick-starts, and known limitations.
+
 .. _overview:workloads:
 
 Workloads

airflow-core/docs/img/diagram_java_sdk_execution_architecture.md5sum

@@ -0,0 +1 @@
+061e71105ed4ce16e740a942073b7ace

airflow-core/docs/img/diagram_java_sdk_execution_architecture.py

@@ -0,0 +1,287 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+# /// script
+# requires-python = ">=3.10"
+# dependencies = [
+#    "rich>=13.6.0",
+#    "graphviz>=0.20.1",
+# ]
+# ///
+"""
+Architecture diagram for the Java (JVM) Task SDK.
+
+Unlike the Go SDK (a standalone edge worker), the Java SDK plugs into the *same*
+Python Supervisor via a new **Coordinator** layer:
+
+* ``CoordinatorManager`` resolves the task's ``queue`` to a ``BaseCoordinator``
+  (``JavaCoordinator`` for the ``java`` queue, ``_PythonCoordinator`` otherwise);
+* ``JavaCoordinator.execute_task()`` opens two loopback-TCP servers, spawns a JVM
+  bundle process with ``subprocess.Popen``, and drives it with
+  ``_JavaActivitySubprocess`` — a subclass of the shared ``ActivitySubprocess``;
+* the JVM process connects *back* over TCP and speaks the same msgpack protocol as
+  a Python task, so the Python side heartbeats, proxies every Execution-API call,
+  and manages state. The JVM task therefore **never holds the task JWT**.
+
+Rendered with graphviz directly so labels sit inside sized shapes: 3-D box =
+native OS process, rounded box = an object inside a process, component = a server
+app, cylinder = the database, note = a caption.
+"""
+
+from __future__ import annotations
+
+from pathlib import Path
+
+import graphviz
+from rich.console import Console
+
+MY_DIR = Path(__file__).parent
+MY_FILENAME = Path(__file__).with_suffix("").name
+
+console = Console(width=400, color_system="standard")
+
+# (fill, border) per role — consistent with the other Task SDK diagrams.
+COORD = ("#ede7f6", "#5e35b1")  # Coordinator layer (Python, deep purple)
+SUP = ("#e3f2fd", "#1565c0")  # Supervisor / ActivitySubprocess + Client (blue)
+JVM = ("#fbe9e7", "#d84315")  # JVM SDK runtime (deep orange)
+USER = ("#e8f5e9", "#2e7d32")  # user task code (green)
+API = ("#fdecea", "#c62828")  # Execution API (red)
+NEUTRAL = ("#eceff1", "#455a64")  # database
+NOTE = ("#fffde7", "#f9a825")  # caption
+
+
+def _label(title: str, sub: str | None = None) -> str:
+    html = f"<<b>{title}</b>"
+    if sub:
+        html += f'<br/><font point-size="11" color="#37474f">{sub}</font>'
+    return html + ">"
+
+
+def _node(g, node_id: str, title: str, sub: str, *, shape: str, theme: tuple[str, str]) -> None:
+    fill, border = theme
+    style = "filled" if shape in ("box3d", "cylinder", "component", "note") else "rounded,filled"
+    g.node(
+        node_id,
+        label=_label(title, sub),
+        shape=shape,
+        style=style,
+        fillcolor=fill,
+        color=border,
+        penwidth="2",
+        margin="0.18,0.12",
+    )
+
+
+def generate_java_sdk_execution_architecture_diagram():
+    image_file = MY_DIR / f"{MY_FILENAME}.png"
+    console.print(f"[bright_blue]Generating architecture image {image_file}")
+
+    g = graphviz.Digraph("java_sdk_execution_architecture")
+    g.attr(
+        rankdir="TB",
+        splines="spline",
+        nodesep="0.6",
+        ranksep="0.9",
+        pad="0.5",
+        bgcolor="white",
+        fontname="Helvetica",
+        newrank="true",
+        compound="true",
+    )
+    g.attr("node", fontname="Helvetica", fontsize="13", fontcolor="#102027")
+    g.attr("edge", fontname="Helvetica", fontsize="10", penwidth="1.8", color="#546e7a")
+
+    # ------------------------------------------------------------------ #
+    # Worker host — native OS processes.
+    # ------------------------------------------------------------------ #
+    with g.subgraph(name="cluster_host") as host:
+        host.attr(
+            label="Worker host — native OS processes",
+            labelloc="t",
+            style="rounded,filled",
+            fillcolor="#f7f7fb",
+            color="#90a4ae",
+            penwidth="1.5",
+            fontsize="16",
+            fontname="Helvetica-Bold",
+            margin="18",
+        )
+
+        with host.subgraph(name="cluster_sup") as sup:
+            sup.attr(
+                label="Supervisor process   ·   native OS process (Python)",
+                labelloc="t",
+                style="rounded,filled",
+                fillcolor="#eef0fb",
+                color=SUP[1],
+                penwidth="1.5",
+                fontsize="13",
+                fontname="Helvetica-Bold",
+                margin="14",
+            )
+            _node(
+                sup,
+                "coord_mgr",
+                "CoordinatorManager.for_queue()",
+                "resolves the task queue → a coordinator via<br/>[sdk] queue_to_coordinator / [sdk] coordinators",
+                shape="box",
+                theme=COORD,
+            )
+            _node(
+                sup,
+                "java_coord",
+                "JavaCoordinator (BaseCoordinator)",
+                "execute_task(client): open two loopback-TCP<br/>servers, subprocess.Popen(java -jar bundle)",
+                shape="box",
+                theme=COORD,
+            )
+            _node(
+                sup,
+                "supervisor",
+                "_JavaActivitySubprocess",
+                "subclass of the shared ActivitySubprocess<br/>heartbeat · proxy every API call · manage state",
+                shape="box3d",
+                theme=SUP,
+            )
+            _node(
+                sup,
+                "client",
+                "Client",
+                "authenticated Execution API client<br/>holds the short-lived task JWT",
+                shape="box",
+                theme=SUP,
+            )
+            sup.edge(
+                "coord_mgr", "java_coord", style="dotted", color=COORD[1], arrowhead="vee", label="picks"
+            )
+            sup.edge(
+                "java_coord", "supervisor", style="dotted", color=SUP[1], arrowhead="vee", label="drives"
+            )
+            sup.edge("supervisor", "client", style="dotted", color=SUP[1], arrowhead="none")
+
+        with host.subgraph(name="cluster_jvm") as jvm:
+            jvm.attr(
+                label="JVM bundle subprocess   ·   native OS process (JVM)   ·   runs USER CODE",
+                labelloc="t",
+                style="rounded,filled",
+                fillcolor="#fdefe9",
+                color=JVM[1],
+                penwidth="1.5",
+                fontsize="13",
+                fontname="Helvetica-Bold",
+                margin="14",
+            )
+            _node(
+                jvm,
+                "server",
+                "Server.serve(bundle)",
+                "bundle JAR entry point (Main-Class)<br/>Kotlin runtime · connects back over TCP",
+                shape="box3d",
+                theme=JVM,
+            )
+            _node(
+                jvm,
+                "task",
+                "Task.execute(Context, Client)",
+                "your Java / Kotlin task  [user code]<br/>Context = static run data · Client = API accessors",
+                shape="box3d",
+                theme=USER,
+            )
+            _node(
+                jvm,
+                "comm",
+                "CoordinatorComm / Frame",
+                "msgpack framing (Kotlin)",
+                shape="box",
+                theme=JVM,
+            )
+            jvm.edge("server", "task", style="dotted", color=JVM[1], arrowhead="vee", label="invokes")
+            jvm.edge("task", "comm", style="dotted", color=JVM[1], arrowhead="none")
+
+        # Loopback-TCP comms between the two native OS processes (JVM connects back).
+        g.edge(
+            "comm",
+            "supervisor",
+            label="msgpack frames over loopback TCP (127.0.0.1)\nJVM connects back · ToSupervisor / ToTask",
+            color=JVM[1],
+            fontcolor=JVM[1],
+            dir="both",
+            penwidth="2.2",
+        )
+        g.edge(
+            "comm",
+            "supervisor",
+            label="structured logs\n(second TCP channel)",
+            color=JVM[1],
+            fontcolor="#a1674f",
+            style="dashed",
+        )
+
+    # ------------------------------------------------------------------ #
+    # API server — separate process / host.
+    # ------------------------------------------------------------------ #
+    with g.subgraph(name="cluster_server") as server:
+        server.attr(
+            label="API server   ·   separate process / host",
+            labelloc="t",
+            style="rounded,filled",
+            fillcolor="#fdeeec",
+            color=API[1],
+            penwidth="1.5",
+            fontsize="13",
+            fontname="Helvetica-Bold",
+            margin="14",
+        )
+        _node(
+            server,
+            "execution_api",
+            "Execution API",
+            "FastAPI · TEI / AIP-72",
+            shape="component",
+            theme=API,
+        )
+        _node(server, "metadata_db", "Metadata DB", "", shape="cylinder", theme=NEUTRAL)
+        server.edge("execution_api", "metadata_db", style="dotted", color=API[1], dir="both")
+
+    g.edge(
+        "client",
+        "execution_api",
+        label="HTTPS + task JWT\n(proxied for the JVM task)",
+        color=API[1],
+        fontcolor=API[1],
+        penwidth="2.2",
+    )
+
+    # Contrast caption.
+    _node(
+        g,
+        "note",
+        "How it differs",
+        "vs Python task: same Supervisor, but a JVM subprocess over loopback TCP<br/>"
+        "instead of a forked Python process over a UNIX socketpair<br/>"
+        "vs Go SDK: the JVM task does <b>not</b> hold the JWT and does <b>not</b> call the<br/>"
+        "Execution API directly — the Python Supervisor proxies every call",
+        shape="note",
+        theme=NOTE,
+    )
+    g.edge("supervisor", "note", style="invis")
+
+    g.render(outfile=str(image_file), format="png", cleanup=True)
+    console.print(f"[green]Generated architecture image {image_file}")
+
+
+if __name__ == "__main__":
+    generate_java_sdk_execution_architecture_diagram()

airflow-core/docs/img/diagram_java_sdk_execution_sequence.md5sum

@@ -0,0 +1 @@
+5c927fe1f455ae4fc5bf77ebf7fc7ae7