Containers and patch management
One of the things that I have realized in the past few years while handling the patch management activities, is that patch management must be a very systematic approach as even updating certain system packages might bring the application down.
This is one of the reasons why having the same environment across DEV, QA, and production is a must; otherwise, there will be a lot of discrepancies that might occur. Many times, however, it's easier said than done.
With this said, it's better to move on with the approach of containers because it provides a lot of advantages, and along with this, patch management becomes a piece of cake as containers are generally self-managed and do not really depend on the system libraries ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access