If the blob artifact system is superior to s3, another option is migrating from s3 to blob artifact system. As I understand it, the blob artifact system gets us trusted sha256's of artifacts (so we can be sure artifacts are not tampered with), parallelised multipart uploads and downloads (i.e. faster uploads/downloads), smarter content-encoding(?), and maybe some other metadata/guarantees that we currently lack. I think also we have a tool for uploading/downloading blob artifacts so we can ensure consistent ergonomics of artifact uploading/downloading across workers and tools. I think the original intention was that the object service would use the blob artifact system, rather than replace it, so this may also help to reduce the amount of work required to implement the object service.
Bug 1577785 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
If the blob artifact system is superior to s3, another option is migrating from s3 to blob artifact system. As I understand it, the blob artifact system gets us trusted sha256's of artifacts (so we can be sure artifacts are not tampered with), parallelised multipart uploads and downloads (i.e. faster uploads/downloads), smarter content-encoding(?), and maybe some other metadata/guarantees that we currently lack. I think also we have a tool for uploading/downloading blob artifacts so we can ensure consistent behaviour of artifact uploading/downloading across workers and tools. I think the original intention was that the object service would use the blob artifact system, rather than replace it, so this may also help to reduce the amount of work required to implement the object service.