Re:Microsoft Ubuntu repositories are broken because of space...
by iso1631 on Thursday June 17, 2021 @05:18AM
(#27537669)
The modern argument would be that you're more likely to have problems with your own cache than someone else, and you should just use caching as a service.
[ Parent
| on HN ]
Re:Microsoft Ubuntu repositories are broken because of space...
by pdpi on Thursday June 17, 2021 @05:45AM
(#27537863)
It's a lot easier to remove yourself from the critical path if your cache has problems than it is to add the caching after the fact when a third party is having problems, though.
Re:Microsoft Ubuntu repositories are broken because of space...
by hnlmorg on Thursday June 17, 2021 @07:15AM
(#27538374)
Exactly this!
You plan for failure. What happens if your cache fails? You fall back to Microsoft. But what happens if Microsoft fails and you don't have a cache? Well you build a cache in advance and default to that.
Caches can also improve build time, allow for security tools to scan, and other such benefits too. So there are other benefits outside of creating a redundancy.
Re:Microsoft Ubuntu repositories are broken because of space...
by coredog64 on Thursday June 17, 2021 @09:38AM
(#27539430)
We do local caching, and itβs caused more outages, downtime, headaches and lost productivity than I can count. Although the hardware requirement is minimal, all that other stuff makes it expensive. So run a risk calculation for your own use case.
Re:Microsoft Ubuntu repositories are broken because of space...
by ohgodplsno on Thursday June 17, 2021 @05:23AM
(#27537706)
The modern argument is most likely made by people who sell caching as a service and have an interest in you blowing $500/month on a glorified FTP or a script to setup Artifactory.