Taking the site down for every release is not acceptable when teams ship many times a day. Zero-downtime deploys use rolling, blue-green or canary strategies with readiness probes and graceful shutdown so users never see errors. Use them for any service with live traffic, keeping database changes backward compatible because old and new versions run together. Renaming a column in the same release as the code change is the usual mistake; use expand and contract instead.