Custom data sources for A/B testing with Vamp Lamia and Istio 1.0.2

Welcome to our ongoing series of post on our experiences in using Istio during the development of Vamp Lamia.

In our previous post, we presented Vamp Lamia’s approach to A/B testing and then delved deeper into how Experiments use Welch’s t-test to identify the test’s winner in a statistically sound way.

In both scenarios, however, we relied solely on Elasticsearch to gather the necessary statistics to calculate the A/B test outcome. This begs the question: what if we wanted to use a different source? In this post we will discuss the possibility of employing a custom data source, be it a different database or another application, deployed inside or outside the cluster.

Welch's t-test for A/B testing with Vamp Lamia and Istio 1.0.2

Welcome back to our ongoing series on the development of Vamp Lamia and our experiences in using Istio for traffic routing on Kubernetes. In one of our previous posts, we presented our approach to A/B testing with Vamp Lamia through the use of Experiments, which enable the user to quickly create a complex Virtual Service configuration and set up a Policy that will redirect the traffic based on the users’ behaviour, for example moving all visitors to the winning variant of an Experiment. As we stated at the end of the post, however, our implementation was, at that time, pretty simple.  Since then, we made quite a few improvements and we are now ready to share them.

Vamp's Gateway Agent

This post is the start of a series of posts about Vamp’s Gateway Agent component and our experiences of adopting Istio for east-west traffic on Kubernetes. Join us as we discuss the architecture, implementation and evolution of this key component of Vamp.

Putting Istio to work

This is part of an ongoing series of posts describing Vamp’s Gateway Agent component and our experiences of adopting Istio for east-west traffic on Kubernetes. In this post we want to introduce Lamia and give you a first glimpse of the working code.

Taming Istio

This is part of an ongoing series of posts describing Vamp’s Gateway Agent component and our experiences of adopting Istio for east-west traffic on Kubernetes. Join us as we continue discussing the architecture, implementation and evolution of this key component of Vamp.

How to extend Marathon-LB with Canary releasing features using Vamp

At the Vamp HQ in Amsterdam we get to talk to a lot of Docker, DC/OS and Kubernetes users. For us, as a startup in this corner of the tech space, talking to the engineers and architects behind some pretty serious container based cloud environments is of course worth the proverbial gold. It’s also a lot of fun to just help people out.