 From San Francisco, it's theCUBE, covering GitLab Commit 2020. Brought to you by GitLab. Hi, I'm Stu Miniman and this is theCUBE's exclusive coverage of GitLab Commit 2020 here in San Francisco. You might notice it's a little chilly in San Francisco today. Welcome to the program, first time against Vince Domenia, who is a senior director of engineering at Axway. And you can tell by the GitLab Commit jacket that he is a speaker at the show. And good thing to wear that one today, yes, Vince? Yes, it's very, very chilly here, but we're all having a great time. Yeah, absolutely. It's the warmth of the community that's keeping everyone going. First of all, I believe first time we've had Axway on our program, so for people that don't know, tell us a little bit about Axway. Sure, Axway's in the business of helping save your company, basically, and help them through the digital transformation. So if you've ever deposited a check electronically on your phone, you've probably, there's a 90% chance you've crossed one of our API gateways or managed file transfer systems. So we've helped banks, we help hospitals, healthcare, lots of verticals, and assisting them through their digital transformation. Awesome, so yeah, we love talking about digital transformation. Your presentation here at Commit is actually about Journey to Cloud. So tell us a little bit about what that means, gives a little bit of view inside what you're gonna be sharing with the community here. Sure, Journey to the Cloud is a program that we conceived a couple of years ago, and it's all about bringing our company into the cloud native space, as well as bringing our existing product line into the cloud so it can run, it can scale, easy to deploy, day two operations. So what we're gonna talk about today is basically Axway's journey as an ISV, going from quarterly and semi-annual deliveries to daily deployments, low change failure rates, faster lead time to changes, so. Yeah, it's wonderful things that if you hear about DevOps, it's all about how we can shorten those release cycles and have those continuous feedback loops, so how long have you been with Axway? I've been with Axway for four years now. Okay, so yeah, bring us inside a little bit that journey is, what are the ripple effects as you try to tighten things down and not get on the train, but just chip and chip and chip. Yeah, absolutely. I can say that it's a journey that really requires vigilance. It's constant practice, continuous learning to be lean. So if I were to describe the journey, it's about contributing together, working as one team to build one platform, and that's across DevOps and security. We'll go into a bit about how we really shifted security left this year by working closely with them. We really took the time to seek to understand their needs, as well as the security team understanding our needs in terms of continuous deployment. And we worked together on a solution called the Continuous Security Review, allows us to get to the deployment frequency of multiple times per day versus the deployment frequency. Before that, we still followed the traditional initial security view, final security view. We could only release once a sprint, two weeks. Yeah, a mantra we've heard at many of the shows we go to is security is everyone's responsibility. Was there a lot of retraining that needed to be done? Did the security people kind of lock everybody in the room and make them watch films? Or how did you work through some of these changes? That's a great question. So, there are a lot of things that our product security group does along with our cloud security team. They do have training globally for Axway, not only for the development team, operations team as well. They also, we also have built cross functional teams within our scrum team. So our scrum teams contain what's called a SPOC, a security point of contact, a DevOps point of contact, a quality point of contact. And those members of the team help that scrum team have full ownership of that service. So when you say security is everybody's job, it's really security, quality, reliability, scalability, and stability is everybody's job. And when you build those cross functional teams, you're able to provide the team the capability to have the ownership to take those services into the cloud on a daily basis. All right, Vince, help us connect the dots. Axway and GitLab, what's the connection there? Another great question. So we became a GitLab customer back in 2015. We were on SVN primarily and through lots of acquisitions, either CVS or SVN. And we were looking at the next generation, source control management tool. We actually invested and purchased GitLab for Axway in 2015 because it had a non-premise offering. And we needed to store all of our source code on premise. We have contracts with the governments around the world. And so that's how our journey started. But what we couldn't have imagined was how it was going to evolve. And that's why we're so happy with GitLab. They really take our feedback seriously. A lot of the things that we've asked them to go ahead and implement, they've gone and iterated and implemented those things, allowed us to test features, get faster feedback. One of the things we were looking for was EKS recently as a native way to basically plug in EKS as a GitLab runner and run your workloads there. That was implemented, I think, within the last release or two releases ago. So we really appreciate GitLab's responsiveness with their product. Okay, EKS, you're talking about Amazon's Kubernetes, of course they are. So you talked about on-premises. What is your cloud deployment? Are you multi-cloud now? Or where does Kubernetes fit in that overall discussion? Another great question. So our journey to cloud native started with a product called Amplify Central. And what we did was we started out with Docker Swarm. We evolved to cops. At the time when we had first gotten our production deployment running on cops, EKS was just in its initial phases of rolling out. We're an Amazon premier technology partner and we actually helped them with their valuation of the initial bit of EKS, gave them feedback a year later. We're looking at it as a way to consolidate platform and allow our teams to focus on building a better product rather than having infrastructure overhead of upgrading infrastructure and going through those cycles. We could just test the infrastructure before we roll it out. So Vince, you're talking a lot about your journey to cloud. What advice do you give to your peers as they're heading down their own journey? The advice I give to my peers is to keep calm and we'll go over that in our presentation. But really it's about behavior change. So it's not just words that are on some paper that you walk into and you look at. You really have to embody those behaviors and have those feelings about what you're doing and that's gonna change your values and attitudes about how you act and work and help each other out and that's how you break down silos and ultimately that's what changes culture. It's your values, attitudes, beliefs and behaviors that culminate to build a one team, operating as one team to deliver one platform. Okay, so you're speaking at the show, obviously you've used GitLab quite a bit. What else, what brings you to this show? What are you hoping to get out of it? Just to see what our peers and fellow practitioners are doing in the cloud. See how GitLab's evolving. It was really great keynote this morning from Todd and Sid. So it's great to keep abreast as to what, even some of our customers are here today and to hear their story about how they're moving to the cloud and how it might parallel and some things that we can learn from them. That's one of the key behaviors. When you move towards cloud native is creating a culture of learning and that's how you grow. All right, well, thanks so much for sharing your journey. Appreciate it. Appreciate to meet you and best of luck with your presentation and I'm Stu Miniman. This is GitLab Commit 2020. Thanks so much for watching theCUBE.