Skip to main content

Documentation Index

Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt

Use this file to discover all available pages before exploring further.

In this article, we explore the concept of canary deployments within an API Gateway environment. Canary deployments allow you to run a new version of your service alongside the existing production version, thereby minimizing risk during updates. When using the canary deployment strategy, a small segment of your incoming traffic—typically around 10%—is routed to the new version (the canary). This controlled traffic diversion enables you to monitor, test, and ensure the stability of the canary release without impacting the majority of your users.
  • Allows gradual rollout and validation of new features.
  • Reduces the risk of widespread impact from potential issues.
  • Enables quick rollback if any problems are detected.
If the canary version proves to be reliable and performs as expected, you can seamlessly transition the entirety of your traffic to this new release. Alternatively, if issues arise during this trial phase, you have the option to revert the traffic entirely back to the production version, ensuring uninterrupted service for your users. This method not only improves overall deployment safety but also facilitates a smoother, more controlled update process.

Watch Video