A/B testing deployment is a technique that's used to test features in your application.

This means that A/B testing is suitable for frontend applications that are introducing new interfaces, or changing the look and feel of the applications. Feedback from users is very important, thus doing it directly in production is the best test environment you can have. The users' reaction can show whether changes you have done are intuitive or not, and you can eventually adapt your software according to the feedback.

From OpenShift's perspective, this is literally the same as canary deployment, except that you set the weights between the two services to 50% each:

So, if you didn't follow Chapter 8, Microservices Patterns, please do so, and set 50% for the service weights.

As you can see, in OpenShift, it is very easy to achieve such deployment techniques, as they all have the route component as the kingmaker.