Infrastructure · Software component
Version Rollback Controller
Software componentInfrastructureInfrastructureVariation point (abstract)arc:VersionRollbackController
An abstract release component that returns production traffic from a newly deployed agent or model version to the previous known-good version.
Responsibility. Restores the previous known-good version after a failed or degraded update.
Also known as: Rollback procedure
Variants
| Variant | When to choose |
|---|---|
| Gradual Rollback Controller | Choose for moderate quality degradation, performance issues or non-critical bugs. |
| Immediate Rollback Controller | Choose for critical issues: error rate > 5%, latency > 200% of baseline, system crash/unavailability or detected data corruption. |
Relationships
is invoked by dependency
reads dependency
writes dependency
is triggered by dynamic
triggers dynamic
overrides control
- Rollout Manager abstract Ref8.08
Design guidance
- MUST have a rollback plan prepared before any deployment (Ref8.08).
- SHOULD keep the previous version available for quick rollback after cleanup and test the rollback procedure regularly (Ref8.08).
Quantitative guidance
As stated by the sources; verify before use.
- Previous version retained ~4 hours (14,400 s grace period) after rollout (Ref8.08).
Classification
- Patterns
- Rollback
- Quality attributes
- Reliability (ISO/IEC 25010 | NIST AI RMF: valid and reliable)
- Risks mitigated
- Prolonged user impact from a regressed releaseSevere fairness violations in a newly deployed model version
Sources
- Ch9.4: T. Nguyen, "Fairness and Bias Mitigation," in Mastering Agentic AI Systems: Guide for the NVIDIA NCP-AAI Exam, 1st ed. 2026, ch. 9.4. ISBN: 9798244538229.
- Ref8.08: "Model Updates and Maintenance Procedures," unpublished reference note (08-Model-Updates-Maintenance-Procedures.md), Mastering Agentic AI Systems: Guide for the NVIDIA NCP-AAI Exam supplementary materials, 2026. unpublished note