docs(framework) Add Flower architecture explanation

doc/source/conf.py

@@ -249,8 +249,6 @@ def find_test_modules(package_path):
     "creating-new-messages": "contributor-how-to-create-new-messages.html",
     "write-documentation": "contributor-how-to-write-documentation.html",
     "release-process": "contributor-how-to-release-flower.html",
-    # Restructuring: contributor explanations
-    "architecture": "contributor-explanation-architecture.html",
     # Restructuring: contributor references
     "good-first-contributions": "contributor-ref-good-first-contributions.html",
     "secagg": "contributor-ref-secure-aggregation-protocols.html",
@@ -265,6 +263,8 @@ def find_test_modules(package_path):
     "ref-api/flwr.simulation.run_simulation_from_cli": "index.html",
     "contributor-how-to-create-new-messages": "index.html",
     "example-jax-from-centralized-to-federated": "tutorial-quickstart-jax.html",
+    "architecture": "explanation-flower-architecture.html",
+    "contributor-explanation-architecture.html": "explanation-flower-architecture.html",
 }
 
 # -- Options for HTML output -------------------------------------------------

doc/source/explanation-flower-architecture.rst

@@ -0,0 +1,180 @@
+#####################
+ Flower Architecture
+#####################
+
+This page explains the architecture of deployed Flower federated
+learning system.
+
+In federated learning (FL), there is typically one server and a number
+of clients that are connected to the server. This is often called a
+federation.
+
+The role of the server is to coordinate the training process. The role
+of each client is to receive tasks from the server, execute those tasks
+and return the results back to the server.
+
+This is sometimes called a hub-and-spoke topology:
+
+.. figure:: ./_static/flower-architecture-hub-and-spoke.svg
+   :align: center
+   :width: 600
+   :alt: Hub-and-spoke topology in federated learning
+   :class: no-scaled-link
+
+   Hub-and-spoke topology in federated learning (one server, multiple clients).
+
+In a real-world deployment, we typically want to run different projects
+on such a federation. Each project could use different hyperparameters,
+different model architectures, different aggregation strategies, or even
+different machine learning frameworks like PyTorch and TensorFlow.
+
+This is why, in Flower, both the server side and the client side are
+split into two parts. One part is long-lived and responsible for
+communicating across the network, the other part is short-lived and
+executes task-specific code.
+
+A Flower `server` consists of **SuperLink** and ``ServerApp``:
+
+-  **SuperLink**: a long-running process that forwards task instructions
+   to clients (SuperNodes) and receives task results back.
+
+-  ``ServerApp``: a short-lived process with project-spcific code that
+   customizes all server-side aspects of federated learning systems
+   (client selection, client configuration, result aggregation). This is
+   what AI researchers and AI engineers write when they build Flower
+   apps.
+
+A Flower `client` consists of **SuperNode** and ``ClientApp``:
+
+-  **SuperNode**: a long-running process that connects to the SuperLink,
+   asks for tasks, executes tasks (for example, "train this model on
+   your local data") and returns task results back to the SuperLink.
+
+-  ``ClientApp``: a short-lived process with project-specific code that
+   customizes all client-side aspects of federated learning systems
+   (local model training and evaluation, pre- and post-processing). This
+   is what AI researchers and AI engineers write when they build Flower
+   apps.
+
+Why SuperNode and SuperLink? Well, in federated learning, the clients
+are the actual stars of the show. They hold the training data and they
+run the actual training. This is why Flower decided to name them
+**SuperNode**. The **SuperLink** is then responsible for acting as the
+`missing link` between all those SuperNodes.
+
+.. figure:: ./_static/flower-architecture-basic-architecture.svg
+   :align: center
+   :width: 600
+   :alt: Basic Flower architecture
+   :class: no-scaled-link
+
+   The basic Flower architecture for federated learning.
+
+In a Flower app project, users will typically develop the ``ServerApp``
+and the ``ClientApp``. All the network communication between `server`
+and `clients` is taken care of by the SuperLink and SuperNodes.
+
+.. tip::
+
+   For more details, please refer to the |serverapp_link|_ and
+   |clientapp_link|_ documentation.
+
+With *multi-run*, multiple ``ServerApp``\s and ``ClientApp``\s are now
+capable of running on the same federation consisting of a single
+long-running SuperLink and multiple long-running SuperNodes. This is
+sometimes referred to as `multi-tenancy` or `multi-job`.
+
+As shown in the figure below, two projects, each consisting of a
+``ServerApp`` and a ``ClientApp``, could share the same SuperLink and
+SuperNodes.
+
+.. figure:: ./_static/flower-architecture-multi-run.svg
+   :align: center
+   :width: 600
+   :alt: Multi-tenancy federated learning architecture
+   :class: no-scaled-link
+
+   Multi-tenancy federated learning architecture with Flower
+
+To illustrate how multi-run works, consider one federated learning
+training run where a ``ServerApp`` and a ``ClientApp`` are participating
+in ``[run 1]``. Note that a SuperNode will only run a ``ClientApp`` if
+it is selected to participate in the training run.
+
+In ``[run 1]`` below, all the SuperNodes are selected and therefore run
+their corresponding ``ClientApp``\s:
+
+.. figure:: ./_static/flower-architecture-multi-run-1.svg
+   :align: center
+   :width: 600
+   :alt: Multi-tenancy federated learning architecture - Run 1
+   :class: no-scaled-link
+
+   Run 1 in a multi-run federated learning architecture with Flower.
+   All SuperNodes participate in the training round.
+
+However, in ``[run 2]``, only the first and third SuperNodes are
+selected to participate in the training:
+
+.. figure:: ./_static/flower-architecture-multi-run-2.svg
+   :align: center
+   :width: 600
+   :alt: Multi-tenancy federated learning architecture - Run 2
+   :class: no-scaled-link
+
+   Run 2 in a multi-run federated learning architecture with Flower.
+   Only the first and third SuperNodes are selected to participate in the
+   training round.
+
+Therefore, with Flower multi-run, different projects (each consisting of
+a ``ServerApp`` and ``ClientApp``) can run on different sets of clients.
+
+To help you start and manage all of the concurrently executing training
+runs, Flower offers one additional long-running server-side service
+called **SuperExec**. When you type ``flwr run`` to start a new training
+run, the ``flwr`` CLI bundles your local project (mainly your
+``ServerApp`` and ``ClientApp``) and sends it to the **SuperExec**. The
+**SuperExec** will then take care of starting and managing your
+``ServerApp``, which in turn selects SuperNodes to execute your
+``ClientApp``.
+
+This architecture allows many users to (concurrently) run their projects
+on the same federation, simply by typing ``flwr run`` on their local
+developer machine.
+
+.. figure:: ./_static/flower-architecture-deployment-engine.svg
+   :align: center
+   :width: 800
+   :alt: Flower Deployment Engine with SuperExec
+   :class: no-scaled-link
+
+   The SuperExec service for managing concurrent training runs in
+   Flower.
+
+.. note::
+
+   This explanation covers the Flower Deployment Engine. An explanation
+   covering the Flower Simulation Engine will follow.
+
+.. important::
+
+   As we continue to enhance Flower at a rapid pace, we'll periodically
+   update this explainer document. Feel free to share any feedback with
+   us.
+
+.. |clientapp_link| replace::
+
+   ``ClientApp``
+
+.. |serverapp_link| replace::
+
+   ``ServerApp``
+
+.. _clientapp_link: ref-api/flwr.client.ClientApp.html
+
+.. _serverapp_link: ref-api/flwr.server.ServerApp.html
+
+.. title:: Flower federated learning architecture
+
+.. meta::
+   :description: Explore the federated learning architecture of the Flower framework, featuring multi-run, concurrent execution, and scalable, secure machine learning while preserving data privacy.

doc/source/index.rst

@@ -115,6 +115,7 @@ Understanding-oriented concept guides explain and discuss key topics and underly
 
    explanation-federated-evaluation
    explanation-differential-privacy
+   explanation-flower-architecture
 
 References
 ~~~~~~~~~~
@@ -173,7 +174,6 @@ The Flower community welcomes contributions. The following docs are intended to
    :maxdepth: 1
    :caption: Contributor explanations
 
-   contributor-explanation-architecture
    contributor-explanation-public-and-private-apis
 
 .. toctree::