In a typical deployment, the scheduler and worker processes run as daemons, lingering during idle periods (the scheduler literally sleeps as part of its run loop).
Meanwhile, deploying to a serverless platform is attractive for various reasons (cost, security, simplicity, scaling). For example, on Azure where there's a free grant of 1,000,000 executions per month, running a single iteration of the Airflow scheduler loop on a timer trigger set to once every 3 seconds would cost nothing. Still using Azure as an example, tasks might be submitted using an event grid connected to an Azure Function App which would immediately pick up one or more tasks. It seems like this wouldn't be too difficult to implement for a given cloud provider, but I'd like to ask on this list whether there are obvious issues with this execution model and whether this has been suggested or even implemented previously. I wasn't able to find any mention. --\-- cheers
