3 ms·
Are you interested in mitigating risk by reducing central dependencies? I am. But it's too costly right now. All being equal, though, we should try to avoid
by mlyle 7y ago
Are you interested in mitigating risk by reducing central dependencies? I am. But it's too costly right now.
All being equal, though, we should try to avoid technical systems with unnecessary trust relationships and critical concentrated dependencies, though.
And if we must have a concentrated dependency, we should do our best to pick very trustworthy ones-- both based on their track record and their likely future interests relating to organizational structures.
- paxys 7y agoWhat kind of risk though? If you don't trust the code itself – it doesn't matter where it is hosted. Validation/audits etc. are essential in any case. If you don't trust the reliability/uptime of the central service — it's trivial to create a private mirror containing the packages you want. Every internal build system I have seen does this already.
- mlyle 7y agoAll kinds of risks. Risks of being co-opted. Risks of no longer being maintained. Risks of poor administration. The risks you mention-- availability, etc. NPM's had its share of catastrophes and controversies that have made things tougher and caused harm to downstream users. It has also saved lots of effort. Focusing on e.g. mirroring misses the point, IMO: One's dependency on something fundamental like package infrastructure isn't to survive one deployment or minimum sustaining, but to be an ongoing part of your technology stack. Yes, you can move on, but it'll be costly. If the component decides to start to suck, you're going to feel pain.
- imtringued 7y agoMirroring is the correct strategy. You either do something yourself or you let someone else do it.