How deeply does MongoDB 8.0 in Action, Third Edition cover software upgrade?

Explains minor and major upgrade procedures, maintenance windows, rolling upgrades, health checks, snapshots, sequencing, and compatibility review.

Software upgrade

As explained in MongoDB 8.0 in Action, Third Edition

An upgrade is a change that moves a software system or database deployment to a newer version.

A software upgrade moves a system or database deployment to a newer version. In Atlas, regular upgrades maintain security and performance while providing new features, but minor and major upgrades require different operational decisions. section 21.4

Plan an Atlas upgrade according to its scope:

Use a minor upgrade within the same major version, such as 8.0.3 to 8.0.5, for security patches, bug fixes, and small improvements. Atlas applies these automatically during the maintenance window through rolling upgrades, updating nodes one at a time. section 21.4
Schedule or change the maintenance window with the Atlas CLI commands atlas maintenanceWindows create, atlas maintenanceWindows update, and atlas maintenanceWindows delete, or use the Atlas UI. section 21.4
Treat a major upgrade, such as MongoDB 7.0 to 8.0, as a deliberate migration: confirm cluster health, complete on-demand snapshots, and advance only one major version at a time. section 21.4
Review release notes and verify MongoDB driver compatibility before a major upgrade because new versions can introduce non-backward-compatible features or driver interactions. section 21.4

Choosing the upgrade path

Moving from MongoDB 8.0.3 to 8.0.5 is a minor upgrade handled during the maintenance window with little to no downtime. Moving from MongoDB 7.0 to 8.0 is a major upgrade that requires manual initiation, a healthy cluster, completed snapshots, compatibility checks, and release-note review. section 21.4 section 21.5

How MongoDB 8.0 in Action, Third Edition covers it

Cover of MongoDB 8.0 in Action, Third Edition

liveBook manning.com

Read MongoDB 8.0 in Action, Third Edition on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

PostgreSQL Mistakes and How to Avoid ThemA software upgrade is the process of installing a newer version of software or its supporting components.
liveBook manning.com

Google Anthos in ActionCluster upgrading is the process of changing a cluster's software or platform components to a newer version.
liveBook manning.com

Infrastructure as Code, Patterns and Practices: With examples in Python and TerraformA tool upgrade is the process of replacing an infrastructure tool with a newer version while preserving or adapting its managed resources and configuration.
liveBook manning.com

Kafka for ArchitectsAn upgrade is a change that replaces software or its components with a newer version to improve security, stability, functionality, or compatibility.

Compare how 5 books explain 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.

This explainer was generated by Manning's knowledge graph from the text of MongoDB 8.0 in Action, Third Edition. The section links point to the parts of the book it draws on.