3 ms·
There's good and bad there, if you need to patch a security vulnerability you may need to redeploy tons of packages on each host (each package that contains a c
by tedd4u 10y ago
There's good and bad there, if you need to patch a security vulnerability you may need to redeploy tons of packages on each host (each package that contains a copy of the bad lib code) versus patching it once. Depending on how you deploy that might be no big deal or it might be.
- rb2k_ 10y agoThen again, patching it 'once' usually involves restarting all processes that are dynamically linked anyway (and really hoping that it loads the new lib). If deployment is fully automated and scales well, the only painful thing is the restart to begin with :)