Software upgrade
A software upgrade is a change that replaces or updates software or its components to a newer version.
PostgreSQL Mistakes and How to Avoid Them
A software upgrade is the process of installing a newer version of software or its supporting components.
- How it is used
- Guides planned PostgreSQL version maintenance and warns against treating apparent stability as a reason to defer upgrades.
- How deep it goes
- Explains release categories, compatibility, operational risks, staging, and a worked interval-behavior regression without detailing upgrade commands.
- Examples
- Uses a PostgreSQL 13-to-16 gym-subscription upgrade where adding 0.333 years changes an expiry date.
- What you can do after
- Operate/configure it by scheduling updates, reviewing intervening release notes, testing in production-like staging, and verifying application behavior.
Read how PostgreSQL Mistakes and How to Avoid Them explains software upgrade →
Google Anthos in Action
Cluster upgrading is the process of changing a cluster's software or platform components to a newer version.
- How it is used
- Uses version changes and command-line operations to maintain Anthos clusters as new platform releases become available.
- How deep it goes
- Explains configuration edits, tool selection, sequencing, prechecks, compatibility risks, and parallel-cluster rollback planning.
- Examples
- Uses Anthos version YAML, bmctl, gkectl, administrative kubeconfig files, and parallel clusters behind a load balancer.
- What you can do after
- Operate/configure Anthos cluster upgrades while preserving upgrade order and preparing a rollback path for production failures.
Read how Google Anthos in Action explains software upgrade →
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
A tool upgrade is the process of replacing an infrastructure tool with a newer version while preserving or adapting its managed resources and configuration.
- How it is used
- Guides infrastructure teams through controlled upgrades of provisioning, configuration-management, and image-building tools.
- How deep it goes
- Explains checklists, staged deployment, rolling updates, state isolation, and failure recovery, but does not provide a complete migration automation.
- Examples
- Uses a social-media feed migration from version 1.7 through 3.0 to 4.0, including DNS, load balancers, servers, and override scripts.
- What you can do after
- Operate/configure staged tool upgrades while limiting blast radius, testing compatibility, and isolating failures.
Kafka for Architects
An upgrade is a change that replaces software or its components with a newer version to improve security, stability, functionality, or compatibility.
- How it is used
- Maintains self-managed Kafka deployments while preserving resilience, compatibility, and access to security and reliability improvements.
- How deep it goes
- Explains compatibility checks, staging, automation, and upgrade risks without providing a complete version-specific operational runbook.
- Examples
- Uses compatibility checks, migration guides, inter.broker.protocol.version, message formats, Ansible, and Terraform as upgrade artifacts.
- What you can do after
- Operate/configure a staged Kafka upgrade by validating dependencies, consulting migration guidance, and automating production execution.
MongoDB 8.0 in Action, Third Edition
An upgrade is a change that moves a software system or database deployment to a newer version.
- How it is used
- Maintains Atlas security, performance, availability, and access to new features through minor or major version changes.
- How deep it goes
- Explains minor and major upgrade procedures, maintenance windows, rolling upgrades, health checks, snapshots, sequencing, and compatibility review.
- Examples
- Uses MongoDB 8.0.3-to-8.0.5 and 7.0-to-8.0 version changes, plus Atlas maintenance-window CLI commands.
- What you can do after
- Operate Atlas upgrades by selecting the correct path, scheduling maintenance, preparing snapshots, and checking compatibility.
Read how MongoDB 8.0 in Action, Third Edition explains software upgrade →
Related concepts
- pg_upgradeimplemented by · pg_upgrade is a PostgreSQL utility that upgrades a database cluster to a newer major version while preserving its data.
- bmctluses · bmctl is a command-line tool and binary executable for deploying and managing Anthos clusters on bare-metal infrastructure.
- release notesuses · Release notes are documentation summarizing changes, fixes, features, compatibility considerations, and other notable information associated with a software release.
- major upgradeincludes · A major upgrade is a software-version upgrade that introduces substantial changes and typically requires explicit initiation and preparation.
- rolling updateuses · A rolling update is a deployment or upgrade technique that updates or replaces instances or resources incrementally rather than all at once, allowing the rest of the system to continue operating during the change.
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.