: XComs consist of a key , value , and timestamp , along with attributes for the specific Task Instance and DAG Run.
: For high-security or high-volume needs, organizations implement Custom XCom Backends . This allows tasks to push data to an "exclusive" external storage (like S3 or Snowflake) rather than the shared Airflow metadata database. This provides exclusive control over data lifecycle policies, such as custom retention or encryption, that are not possible with standard XComs. Standard XCom Characteristics airflow xcom exclusive
@task def producer(): return "exclusive_for": "consumer_1", "data": [1,2,3] : XComs consist of a key , value
Pros:
In child DAG, exclusive mode ensures only keys passed via conf are accessible. : XComs consist of a key
@task def exclusive_pop(): with r.lock("xcom:my_key", timeout=10): value = r.get("xcom:my_key") r.delete("xcom:my_key") return value