Traffic management between new version of API (Canary release)

[umeshtiwari23]

Description

Most modern API Gateway supports the canary release where canary release receives a small percentage of API traffic and the production release takes up the rest.

Acceptance Criteria

Policy thats supports a pre-configured ratio of traffic routing between old and new API version.

Motivation

No response

Details

No response

[msavy]

Do you already use Apiman, and are you familiar with writing plugins?

What kinds of different ways would you want to configure routing traffic between old and new version.

e.g.

• Accept header modification
• Different base URL
• Custom header?

[umeshtiwari23]

I have used APIMan before but I am not familiar with writing plugins. My use case is slightly different here, I want to route the traffic to new backend & old backend but the API version remains unchanged. e.g.

[msavy]

You can create an Apiman policy plugin to do this today. It might be a tiny bit awkward, but it's certainly doable.

Your 'canary policy' would simply rewrite the destination URL for 30% of the incoming requests to the alternative backend.

Does that make sense?

[umeshtiwari23]

thanks for the feedback