Rolling Deployment Strategy involves gradually updating pods one at a time, therefore minimizing downtime and allowing rollback in case of failures.
This strategy is useful when the old and new versions can't run simultaneously, ensuring a completely fresh application state by replacing the old pods with new ones.
This strategy uses two environments to switch traffic between environments using a load balancer, reducing downtime but it uses double resources.
With this strategy, developers can gradually shift a small portion of traffic to the new version, testing its stability before a full rollout and ensuring smooth transit.
Shadow Deployment runs the new version alongside the current one without user impact, testing performance, and stability which is useful in testing.
A/B Deployment targets specific user segments based on parameters like HTTP headers which helps test the app performance of different versions.