No upgrade-time schedules for developers: no need to wait for maintenance windows.Instant rollbacks: undo the change without adverse effects and go back to the previous best state.Seamless customer experience: users don’t experience any downtime.This ensures that all aspects of the new versions are running as they should be. This is crucial as they need to figure out if there is an issue with the new version before users are impacted on a wide scale. Once the traffic is switched from the blue to green instance, the DevOps engineers get a small duration of time to run smoke tests on the green instance. Most users won’t even notice that they are now accessing a newer version of the service or application. With the help of their load balancer, traffic is switched from blue to green. Once the green instance (v1.1) is ready we move that into production and run it parallelly with the older version.
Blue green full#
Full control is desired because it will be necessary to quickly switch them back to version 1 (the blue instance) in case of a failure in a green instance. This allows us to be in full control of the users. There is no need to change DNS records as the load balancer will still reference the same DNS record but routes new traffic to the Green environment. This is where load balancers and routers help in switching users from the Blue instance to the Green one. For this to happen, we normally use a load balancer instead of a DNS record exchange because DNS propagation is not instantaneous.
Now that we have two instances named Blue and Green, we want users to be able to access the new green (v 1.1) instance rather than the older Blue instance.
0 kommentar(er)
