liveBook · Manning

Software update

A software update is a change applied to existing software to modify or improve its behavior, correct defects or vulnerabilities, or add functionality.

How 4 Manning books explain it

100 SQL Server Mistakes and How to Avoid Them

Patching is the process of applying software updates that fix defects, address vulnerabilities, or improve supported behavior.

How it is used
Frames patching as a DBA-led maintenance practice that protects business availability, security, and reputation.
How deep it goes
Explains avoidance motives, attack and outage consequences, and availability-based mitigations, but does not detail patch installation steps.
Examples
Uses MagicChoc’s online sales database, marketing data warehouse, overnight ETL, and company-wide ransomware outage.
What you can do after
Operate patching more safely by retaining regular coverage, using availability technologies, and scheduling around business constraints.

Read how 100 SQL Server Mistakes and How to Avoid Them explains software update →

Think Like a CTO

The process of applying software updates to correct defects, address vulnerabilities, or improve behavior.

How it is used
Positions updates as ongoing enterprise security maintenance against bugs and exploitable openings.
How deep it goes
Details inventory, alert monitoring, cadence, and testing; stops short of implementation commands.
Examples
Uses email and file servers without staging, plus network-connected devices needing manual checks.
What you can do after
Practice/perform it by monitoring alerts, testing patches, and scheduling small, frequent updates.

Read how Think Like a CTO explains software update →

Amazon Web Services in Action, Third Edition: An in-depth guide to AWS

A security update is a software change released to remediate a security vulnerability.

How it is used
Uses timely patching to reduce vulnerability exposure across running virtual machines and other installed software.
How deep it goes
Explains update urgency, startup commands, reboot limitations, and Patch Manager automation without detailing vulnerability assessment.
Examples
Uses kernel, OpenSSL, Java, Apache, PHP, WordPress, yum commands, and a Patch Manager maintenance window as examples.
What you can do after
Operate EC2 patching with Amazon Linux 2 user data or AWS Systems Manager Patch Manager and scheduled maintenance windows.

Read how Amazon Web Services in Action, Third Edition: An in-depth guide to AWS explains software update →

Build Python Web Apps with Streamlit

Patching is a testing technique that temporarily replaces a referenced object, function, or dependency with a controlled substitute during execution.

How it is used
Uses controlled substitutes to isolate backend dependencies and frontend components during unit tests.
How deep it goes
Explains decorators, configured mock responses, call assertions, and result checks without descending into mock-library internals.
Examples
Uses mocked movie-search responses, request-argument assertions, empty results, poster URLs, and Streamlit interaction simulation.
What you can do after
Apply it via unittest.mock to build deterministic tests that control dependencies and verify calls and outputs.

Read how Build Python Web Apps with Streamlit explains software update →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.