| Pros | Cons |
|---|---|
| Low impact deployment: can deploy a new version of the application with minimal impact on the users or the service availability | High complexity and testing challenges: need to deal with multiple versions of the application running simultaneously, which can introduce new challenges and limitations. You also need to test and monitor both versions individually as well as compare them against each other |
| Early feedback: can get early feedback from real users or servers on how they experience and interact with the new version | High synchronization and coordination challenges: need to keep both versions in sync with each other in terms of data, configuration and dependencies. You also need to coordinate with other teams or stakeholders when performing the rollout or rollback |
| Low risk of failure and downtime: can detect and fix any issues or errors before they affect more users or servers |
Created
July 19, 2023 06:52
-
-
Save EliFuzz/e0f9862bebaeb7ae026e1daa784ba215 to your computer and use it in GitHub Desktop.
Pros & Cons: Canary deployment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment