We want to self-host Observable Framework on Azure. In the Azure DevOps pipeline we’re using a container image based on the framework-runtime to build the project . We then publish the build using Azure Static Web Apps.
Most of the data loaders are using DuckDB + Ibis to read from an Azure Data Lake Storage. However, some of the data loaders really need much more memory and CPU than what the build agents have. Any suggestions on how to deal with this? I guess we are forced to construct data loaders that kick off remote jobs, e.g., using Azure Functions or some other serverless service.