Rolling updates replace instances gradually with minimal extra capacity but can expose partial issues. Blue/green keeps two environments and switches traffic at once; rollback is easy but costs more. Canary releases to a small % first to validate metrics, reducing risk but requiring strong monitoring.
Expanding on the short answer — what usually matters in practice:
A tiny example (an explanation template):
// Example: discuss trade-offs for "rolling-vs-blue/green-vs-canary-deployments-—-wh"
function explain() {
// Start from the core idea:
// Rolling updates replace instances gradually with minimal extra capacity but can expose par
}