Currently, some S3 objects are deleted by the sync tasks as soon as they're cleaned up. This will present a problem with caching eventually, as the frontend won't immediately reflect updates in the db. (users could have pages cached by the browser or in-flight requests at the time of deletion)
We should look into setting up a lifecycle rule (PutBucketLifecycleConfiguration) and tagging objects for deletion instead - so that they're removed e.g. a day after being tagged.
Check if this configuration is compatible with minio (for local dev) as well as tigrisdata.
Currently, some S3 objects are deleted by the sync tasks as soon as they're cleaned up. This will present a problem with caching eventually, as the frontend won't immediately reflect updates in the db. (users could have pages cached by the browser or in-flight requests at the time of deletion)
We should look into setting up a lifecycle rule (PutBucketLifecycleConfiguration) and tagging objects for deletion instead - so that they're removed e.g. a day after being tagged.
Check if this configuration is compatible with minio (for local dev) as well as tigrisdata.