BlaBlaCar: Turning to Containerization to Support Millions of Rideshares

By October 25, 2017 Blog

For the 40 million users of BlaBlaCar, it’s easy to find strangers headed in the same direction to share rides and costs. You can even choose how much “bla bla” chatter you want from a long-distance ride mate.

Behind the scenes, though, the infrastructure was falling woefully behind the rider community’s exponential growth. Founded in 2006, the company hit its current stride around 2012. “Our infrastructure was very traditional,” says Infrastructure Engineer Simon Lallemand. “When you’re thinking about doubling the number of servers, you start thinking, ‘What should I do to be more efficient?’ The answer is not to hire more and more people just to deal with the servers and installation.”

Instead, BlaBlaCar began its cloud-native journey but wasn’t sure which route to take. “Going into the cloud meant we had to make a lot of changes in our application work, and we were just not ready to make the switch from on premise to the cloud,” says Lallemand. They wanted to keep the great performance they got on bare metal, so they didn’t want to go to virtualization on premise.

The solution: containerization. This was early 2015 and containers were still relatively new. “It was a bold move at the time,” says Lallemand. “We decided to go with containers and with CoreOS Container Linux as an abstraction for this hardware. It seemed future-proof to go with containers because we could see what companies were already doing with containers.”

Next, they needed to choose a runtime for the containers, but “there were very few deployments in production at that time,” says Lallemand. They experimented with Docker but decided to go with rkt. Lallemand explains that for BlaBlaCar, it was “much simpler to integrate things that are on rkt.” At the time,  the project was still pre-v1.0, so “we could speak with the developers of rkt and give them feedback. It was an advantage.” Plus, he notes, rkt was very stable, even at this early stage.

The first project the team decided to containerize was the database, which required creating some of their own tools. At the same time, the company was working to migrate its entire platform to containers with a deadline set for Christmas 2015. With all the work being done in parallel, BlaBlaCar was able to get about 80 percent of its production into containers by its deadline with live traffic running on containers during December. (It’s now at 100 percent.)

In the middle of that peak season for carpooling, everything worked well. “The biggest impact that we had was for the deployment of new services,” says Lallemand. “Before using containers, we had to first deploy a new server and create configurations with Chef. It would take sometimes a day, sometimes two, just to create a new service. And with all the tooling that we made around the containers, copying a new service is a matter of minutes. So it’s really a huge gain.”

In order to meet their self-imposed deadline, one of the decisions they made was to not do any “orchestration magic” for containers in the first production alignment. “But at some point you want to give more autonomy to the developer team,” Lallemand says. “We also realized that we don’t want to be the single point of contact for developers when they want to launch new services.” By the summer of 2016, they found their answer in Kubernetes, which had just begun supporting rkt implementation. They also started using Prometheus, as they were looking for “service-oriented monitoring that could be updated nightly.” Production on Kubernetes began in December 2016. “We like to do crazy stuff around Christmas,” he adds with a laugh.

BlaBlaCar now has about 3,000 pods, with 1200 of them running on Kubernetes. Lallemand leads a “foundations team” of 25 members who take care of the networks, databases and systems for about 100 developers.

When Lallemand speaks to other European companies curious about BlaBlaCar’s cloud-native journey, he tells them to come along for the ride: “It’s such a pleasure to deal with the infrastructure that we have today compared to what we had before.”

 

To learn more about what’s ahead for BlaBlaCar with Kubernetes and rkt, check out this in-depth case study.

Interested in more Kubernetes content? Get on the CNCF newsletter list for more Kubernetes information and updates.