A separate application slot
The standby instance provides a place to install a candidate without immediately replacing the live application. Both slots must remain compatible with the shared data they use.
Prepare the next release before moving live traffic.
Business owners and IT contacts who need to understand what to expect during a release.
In ZOVRO’s configured blue/green ERP deployment setup, the current application serves users while an update is prepared on a standby instance. The release is validated before an authorized switch. This approach reduces avoidable application-update interruption; it does not make the website, network, database or every maintenance task immune to downtime.
Understand the activity, its controls and the information available for follow-up.
The standby instance provides a place to install a candidate without immediately replacing the live application. Both slots must remain compatible with the shared data they use.
The supplied deployment flow checks the artifact, target health, routing consistency and session-store readiness before switching traffic.
Database-backed sessions are designed to preserve eligible logins across compatible updates. Explicit logout, expiry, security revocation and incompatible changes remain separate considerations.
The team verifies the active release after switching and can use a healthy compatible previous application for reversal. Application rollback does not undo business transactions or database migrations.
Follow the process from preparation to review. Configuration and responsibilities are agreed during implementation.
Keep the current slot live and upload the candidate to the standby process.
Check artifact identity, target health and data/session compatibility.
Authorize the traffic move and verify the new active route.
Review sessions and critical workflows; retain a compatible recovery path.
A routine compatible application release can be prepared while users continue using the live instance. A destructive database migration, operating-system reboot or DNS incident is a different operation and needs separate assessment and communication.
Discuss your workflow →Illustrative ERP blue/green architecture—not a promise of infrastructure redundancy.
Serves requests while the next release is prepared.
Receives traffic after the required release checks.
Confirm the selected release, integrations, hardware and limits in the agreed scope.
No. The architecture reduces avoidable application-release interruption. Infrastructure, DNS, network, database and external-service incidents can still interrupt access.
No. Eligible sessions can persist during compatible tested updates, but normal expiry, logout and security changes still apply.
No. A traffic rollback selects an application version; it does not reverse database changes or transactions already saved.
No. Two application instances on one server still share infrastructure failure risks. Backups and broader recovery arrangements are separate topics.
Tell us about your locations, users and daily challenges. We will map a focused demonstration to your needs.
Read practical business articles →