I see in the Temporal Archival docs:
Local file system: … This provider is used mainly for local installations and testing and should not be relied on for production environments.
Is this still true? We are using Azure as a cloud service, we don’t want to use Google Cloud or S3, it makes no sense for us. Does that mean we should not use Archival in production? Or we should write our own archiver?
This provider is used mainly for local installations and testing and should not be relied on for production environments.
I think the main concern is that if the host crashes you will lost the stored data.
For Azure cloud storage , I am afraid we don’t have an implementation, https://github.com/temporalio/temporal/tree/main/common/archiver , will you be willing to contribute ?
Well I don’t have the knowledge of Azure APIs to properly implement this.
Also, we have the Azure storage mounted as a drive on a linux mount. So if we use the local file system provider and set it at the Azure drive, it will automatically work.
But I still see “should not be relied” and I wonder what it exactly means.