A/B Testing Deployment with Cloudoor Deploy¶

This deployment model releases two versions of the application simultaneously in production environments:

• The first, A, is unchanged and is automatically deployed on the market.
• The second, B, is only available to a defined customer sample.

The first version (A) is called “Control” and will be used by all users except those assigned as testing users. The second version (B) is called “Test”, and it will be used only by testers so that they can evaluate if there are any improvements made in either one version or another based on their feedback.

After monitoring feedback, It is up to you to choose the right moment to release the B version for all users.

Deploying the A/B Testing Strategy from Cloudoor UI¶

We can also deploy the and manage the A/B Testing Deployment through the Cloudoor UI.

Go to Deploy:

You’ll see all workloads. Simply tap the workload you want to edit.

Here, you can find the API Gateway IP. Monitor the Success Rate, Latency, the Requests per min of the Live and Staging versions of your application and the Headers of your application. You can visit either versions using the url in front of the version.

Click “Strategy” and choose A/B Testing from the Dropdown.

Deploying the B Version¶

You can also choose the B version of your application by scrolling down and choosing the version you want from the dropdown in “Staging”.

Setting the Header using Cloudoor UI¶

Headers are the defining differentiator of your B version. Any user of your app that matches the Header key-value pair will be taken to the B version of your application, making it very easy to choose which demograph of your userbase you want to test on. Click the “Add Value” at the bottom of the form. Fill in the Key, Value fields.

Finally, click "Update" and congrats on deploying your workload with the A/B Testing Strategy.

Switching - Going Live with Cloudoor UI¶

When you're completely satisfied with the new version of your application and you wish to push it live. Head over to "Switch" on your App Info page.

Simply click the toggle button and watch your versions swap. Click confirm.

Deploying the A/B Testing Strategy from DOOR¶

Run any of these commands to use the A/B Testing strategy:

door deploy abtesting <WorkloadName> -p <project name> -e <environment name>

-e or --environment: The environment name.

-p or --project: The project name.

--header: This refers to the key,value pair. The header format is key=value.

--image: The docker image of your application. It should be in /. When using the image flag, the version flag is required.

--version: the version of your application docker image i.e the tag. When using the version flag, the image flag is required.

--go-to-live:

There will be two versions of the application running.

door get workload --

The result should look like this:

Deploying the B Version using DOOR¶

To deploy the B version of your application. Run the command:

door deploy abtesting my-workload --image <image name> --version v2.0.0 -p projectName -e environmentName

Setting the Header using DOOR¶

You can configure your application to collect and receive any type of data you want to be the deciding factor of your B version users, e.g location, browser, browser language,etc. Supply the value to Cloudoor as a key=value pair, and Cloudoor will reroute all traffic that satisfies that criteria to your B version.

E.g

door deploy abtesting my-workload --header key=value  --project projectName --env environmentName

door get workload --project projectName --env environmentName

Going Live with DOOR¶

When you’re confident in your B version and you wish to officially release it to your entire user base. You can just run the command to replace your A (old)version with your B (new)version.

door deploy abtesting my-workload --go-to-live -p projectName -e environmentName

door get workload --project projectName --env environmentName