Amadeus: Another technical evolution for a 30-year-old company
Challenge
Amadeus found itself in need of a new platform for the 5,000 services supported by its service-oriented architecture. Among the company’s goals: to increase automation in managing its infrastructure, optimize the distribution of workloads, use data center resources more efficiently, and adopt new technologies more easily.
Solution
Eric Mountain, Senior Expert, Distributed Systems at Amadeus, has been overseeing the company’s migration to Kubernetes, using OpenShift Container Platform, Red Hat’s enterprise container platform.
Impact
One of the first projects deployed in Kubernetes was the Amadeus Airline Cloud Availability solution. “It’s now handling in production several thousand transactions per second, and it’s deployed in multiple data centers throughout the world,” says Mountain. “It’s a whole new workload that we couldn’t have done otherwise.”
Projects used
By the numbers
Response time
Few hundred milliseconds
Transactions
Several thousand per second
5,000 services supported by its service-oriented architecture
In his two decades at Amadeus, Eric Mountain has been the migrations guy.
Back in the day, he worked on the company’s move from Unix to Linux, and now he’s overseeing the journey to cloud native. “Technology just keeps changing, and we embrace it,” he says. “We are celebrating our 30 years this year, and we continue evolving and innovating to stay cost-efficient and enhance everyone’s travel experience, without interrupting workflows for the customers who depend on our technology.”
That was the challenge that Amadeus—which provides IT solutions to the travel industry around the world, from flight searches to hotel bookings to customer feedback—faced in 2014. The technology team realized it was in need of a new platform for the 5,000 services supported by its service-oriented architecture.
The tipping point occurred when they began receiving many requests, internally and externally, for solutions that needed to be geographically outside the company’s main data center in Germany. “Some requests were for running our applications on customer premises,” Mountain says. “There were also new services we were looking to offer that required response time to the order of a few hundred milliseconds, which we couldn’t achieve with transatlantic traffic. Or at least, not without eating into a considerable portion of the time available to our applications for them to process individual queries.”
While mainly a C++ and Java shop, Amadeus also wanted to be able to adopt new technologies more easily. Some of its developers had started using languages like Python and databases like Couchbase, but Mountain wanted still more options, he says, “in order to better adapt our technical solutions to the products we offer, and open up entirely new possibilities to our developers.” Working with recent technologies and cool new things would also make it easier to attract new talent.
All of those needs led Mountain and his team on a search for a new platform. “We did a set of studies and proofs of concept over a fairly short period, and we considered many technologies,” he says. “In the end, we were left with three choices: build everything on premise, build on top of Kubernetes whatever happens to be missing from our point of view, or go with OpenShift and build whatever remains there.”
The team decided against building everything themselves—though they’d done that sort of thing in the past—because “people were already inventing things that looked good,” says Mountain.
Ultimately, they went with OpenShift Container Platform, Red Hat’s Kubernetes-based enterprise offering, instead of building on top of Kubernetes because “there was a lot of synergy between what we wanted and the way Red Hat was anticipating going with OpenShift,” says Mountain. “They were clearly developing Kubernetes, and developing certain things ahead of time in OpenShift, which were important to us, such as more security.”
“We want multi-data center capabilities, and we want them for our mainstream system as well. We didn’t think that we could achieve them with our existing system. We need new automation, things that Kubernetes and OpenShift bring.”
— ERIC MOUNTAIN, SENIOR EXPERT, DISTRIBUTED SYSTEMS AT AMADEUS IT GROUP
The hope was that those particular features would eventually be built into Kubernetes, and, in the case of security, Mountain feels that has happened. “We realize that there’s always a certain amount of automation that we will probably have to develop ourselves to compensate for certain gaps,” says Mountain. “The less we do that, the better for us. We hope that if we build on what others have built, what we do might actually be upstream-able. As Kubernetes and OpenShift progress, we see that we are indeed able to remove some of the additional layers we implemented to compensate for gaps we perceived earlier.”
The first project the team tackled was one that they knew had to run outside the data center in Germany. Because of the project’s needs, “We couldn’t rely only on the built-in Kubernetes service discovery; we had to layer on top of that an extra service discovery level that allows us to load balance at the operation level within our system,” says Mountain. They also built a stream dedicated to monitoring, which at the time wasn’t offered in the Kubernetes or OpenShift ecosystem. Now that Prometheus and other products are available, Mountain says the company will likely re-evaluate their monitoring system: “We obviously always like to leverage what Kubernetes and OpenShift can offer.”
The second project ended up going into production first: the Amadeus Airline Cloud Availability solution, which helps manage ever-increasing flight-search volume and was deployed in public cloud. Launched in early 2016, it is “now handling in production several thousand transactions per second, and it’s deployed in multiple data centers throughout the world,” says Mountain. “It’s not a migration of an existing workload; it’s a whole new workload that we couldn’t have done otherwise. [This platform] gives us access to market opportunities that we didn’t have before.”
Having been through this kind of technical evolution more than once, Mountain has advice on how to handle the cultural changes. “That’s one aspect that we can tackle progressively,” he says. “We have to go on supplying our customers with new features on our pre-existing products, and we have to keep existing products working. So we can’t simply do absolutely everything from one day to the next. And we mustn’t sell it that way.”
The first order of business, then, is to pick one or two applications to demonstrate that the technology works. Rather than choosing a high-impact, high-risk project, Mountain’s team selected a smaller application that was representative of all the company’s other applications in its complexity: “We just made sure we picked something that’s complex enough, and we showed that it can be done.”
“We hope that if we build on what others have built, what we do might actually be upstream-able. As Kubernetes and OpenShift progress, we see that we are indeed able to remove some of the additional layers we implemented to compensate for gaps we perceived earlier.”
— ERIC MOUNTAIN, SENIOR EXPERT, DISTRIBUTED SYSTEMS AT AMADEUS IT GROUP
Next comes convincing people. “On the operations side and on the R&D side, there will be people who say quite rightly, ‘There is a system, and it works, so why change?’” Mountain says. “The only thing that really convinces people is showing them the value.” For Amadeus, people realized that the Airline Cloud Availability product could not have been made available on the public cloud with the company’s existing system. The question then became, he says, “Do we go into a full-blown migration? Is that something that is justified?”
“The bottom line is we want these multi-data center capabilities, and we want them as well for our mainstream system,” he says. “And we don’t think that we can implement them with our previous system. We need the new automation, homogeneity, and scale that Kubernetes and OpenShift bring.”
So how do you get everyone on board? “Make sure you have good links between your R&D and your operations,” he says. “Also make sure you’re going to talk early on to the investors and stakeholders. Figure out what it is that they will be expecting from you, that will convince them or not, that this is the right way for your company.”
His other advice is simply to make the technology available for people to try it. “Kubernetes and OpenShift Origin are open source software, so there’s no complicated license key for the evaluation period and you’re not limited to 30 days,” he points out. “Just go and get it running.” Along with that, he adds, “You’ve got to be prepared to rethink how you do things. Of course making your applications as cloud native as possible is how you’ll reap the most benefits: 12 factors, CI/CD, which is continuous integration, continuous delivery, but also continuous deployment.”
And while they explore that aspect of the technology, Mountain and his team will likely be practicing what he preaches to others taking the cloud native journey. “See what happens when you break it, because it’s important to understand the limits of the system,” he says. Or rather, he notes, the advantages of it. “Breaking things on Kube is actually one of the nice things about it—it recovers. It’s the only real way that you’ll see that you might be able to do things.”