Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Why cloud native transformation is about people as much as technology for Ticketmaster

Matthew Finnegan | April 4, 2017
Ticketmaster has reduced infrastructure provisioning from months to minutes with Kubernetes containers, says executive programme director Bindi Belanger.

Overall, the changes mean that the tech teams could move faster.

"Instead of having a weekly iteration or month long iteration, every morning the team will get together and say what are we delivering today and at the end of the day you are asked to demo the value that you delivered. So we get away from the two week iteration, or the end of the quarter we will have something delivered, we would like to see what we are going to get done each done."


Kubernetes containers

Of course, investment in new technologies also played a key role in the operations changes.

New tools were adopted, deploying Kubernetes container orchestration with CoreOS Tectonic. Prometheus monitoring and Helm packaging tools were also added.

Belanger said with the rapid changes in operations technology means that the team has to prepared to quickly adopt new systems.

"You can't stick to a single framework and say this is the box we are going to live in and we must live in that box," she said.

Kubernetes has helped create applications that are much easier to update, she said.

"One of the great use cases that we have seen is the new Ticketmaster web platforms that was built on Kubernetes. It is still in its beta phase now. Before Kubernetes, even though we were a modern team with great lean practices, we were building on new technology, it still took about 20 minutes or so to deploy, with low confidence - it would often run into issues.

With Kubernetes "fully automated updates that can happen within a minute. And because of that it helped to enable our daily delivery culture".


Previous Page  1  2  3  4 

Sign up for Computerworld eNewsletters.