What mechanism does Web Deploy 3.0 use to provide atomic deployment without downtime?
"Atomic" means that client requests are either processed by the current version or by a new deployed version. This is tricky due to dependencies external to the web application (such as database changes)
“No downtime” means that HTTP requests are delayed only during deployment, and not to receive offline or 503 responses.
source share