Add (image) caching microservice #27
Labels
No Label
todo/H&S
todo/electronics
todo/equipment
todo/event
todo/ideas
todo/information
todo/infra
todo/inspiration
todo/media
todo/merch
todo/museum
todo/presentation
todo/work-shop
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: k-space/kube#27
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The cached content could be placed in S3 bucket, if it exists there redirect to signed URL otherwise attempt to fetch from original URL and upload it to S3 bucket.
The microservice could keep in-memory lookup table of items it knows are in present on S3.
This setup could/should somehow support workers that preemptively get the content cached, maybe by watching events on the original bucket a'la:
Note that the content on the URL should be immutable, so best candidate would be to use hash of the content in the original URL