Skip to content

APIs Architecture #42322

New issue
Jump to bottom
New issue
Jump to bottom
Open
Open
APIs Architecture#42322
Labels
AIP-38Modern Web ApplicationAIP-84Modern Rest APIarea:APIAirflow's REST/HTTP APIarea:helm-chartAirflow Helm Chartkind:metaHigh-level information important to the community
@pierrejeambrun

Description

@pierrejeambrun
pierrejeambrun
opened on Sep 18, 2024

Context

Figure out how the architecture of the APIs will look like from a deployment (CLI, WSGI/ASGI processes, Helm Chart) and source code perspective.

Some of the constraints are:

  • Keep compatibility with FAB and legacy plugin system.
  • Allow users to run the task sdk API as a standalone.
  • Think about the deployment complexity implied by additional reverse proxy or processes.

This could consist of a spike exploring how this could work or putting that on paper via an architecture diagram as requested by @jscheffl in the last airflow 3 dev call.

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.

Metadata

Assignees

No one assigned

    Labels

    AIP-38Modern Web ApplicationAIP-84Modern Rest APIarea:APIAirflow's REST/HTTP APIarea:helm-chartAirflow Helm Chartkind:metaHigh-level information important to the community

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions