(gentle music) >> Hello, welcome to theCUBE's presentation of the AWS Showcase season one, episode two with the ISV Startups partners. I'm John Furrier, your host of theCUBE. We're joined by Morgan McLean, director of product management at Splunk, and Danielle Greshock, who is the director of ISVs solution architects at AWS. Welcome to the show. Thanks for coming on. >> Thanks for having us. >> And great. Thanks for having us. >> Great to see both of you, both theCUBE alumni, but the Splunk-AWS relationship has been going very, very well. You guys are doing great business enabling this app revolution. And cloud scale has been going extremely well. So let's get into it. You guys are involved in a lot of action around application revolution, around OpenTelemetry and open source. So let's get into it. What's the latest? >> Danielle, you go ahead. >> Well, I'll just jump in first. Obviously last year, not last year, but in 2020, we launched the AWS Distro for OpenTelemetry. The idea being essentially, we're able to bring in data from partners, from infrastructure running on AWS, from apps running on AWS, to really be able to increase observability across all cloud assets at your entire cloud platform. So, Morgan, if you want to chime in on how Splunk >> Morgan: Certainly. >> has worked out OpenTelemetry. >> Yeah. I mean, OpenTelemetry is super exciting. Obviously, there's a lot of partnership points between Amazon and Splunk, but OpenTelemetry is probably one of them that's the most visible to people who aren't already maybe using these two products together. And so, as Danielle mentioned, Amazon has their own distribution of OpenTelemetry, Splunk has their own, as well, and of course there's the main open source distribution that everybody knows and loves. Just for our viewers, just for clarity's sake, the separate distributions are fundamentally very similar to, almost identical to what's offered in the open source space, but they come preconfigured and they come with support guarantees from each company, meaning that you can actually get paid full support for an open source project, which is really fantastic for customers. And as Danielle mentioned, it's a great demonstration of the alliance between Splunk and Amazon Web Services. For example, the AWS Distro, when you use it, can export data to Amazon CloudWatch, various Amazon backed open source initiatives like Prometheus and others, and to Splunk Observability Cloud and to Splunk Enterprise. So it's a place that we've worked very closely together, and it's something that we're very excited about. >> So, Morgan, I want to get your take on the on the product management side and also how product are built these days. >> One of the big things we're seeing in cloud is that open source has been the big enabler for a lot of refactoring. And you got multiple distributions, but the innovations on top of that, can you talk about how you see the productization of new innovations with open source as you guys go into this market, because this is the new dynamic with cloud. We're seeing examples all over the place. Obviously, Amazon's going next level with what they're doing, and that open source, it's not a one game for all of it. You can have mix and match. Take us through the product angle. >> And in many ways, this is just another wave of the same thing, right? Like, if you think back in time, we all used and still use in many cases, virtual machines, most of those are based on Linux, right? Another large open source project. And so, open source software has been accelerating innovation in the cloud space and in the computing space generally for a very long time, which is fantastic. Our excitement with something like OpenTelemetry comes from both the project's capabilities but also what we can do with it. So for those who aren't already familiar with OpenTelemetry, OpenTelemetry allows you to extract really critical system telemetry, application signals and everything else you need from your own applications, from new services, from your infrastructure, from everything that you're running in a cloud environment. You can then send that data to another location for processing. And so John, you ask like, how does this accelerate innovation? What does it unlock? Well, the insight you can gain from this data means you can become so much more efficient as a development organization. You can make your applications so much more effective because when you send that data to something like Splunk Observability Cloud, to something like Amazon CloudWatch, to various other solutions on the market, they can give you deep, deep insight into your application's performance, to its structure, they can help you reduce outages. And so, it's very, very powerful because it allows organizations to use tools like Splunk, like Amazon, like other things to innovate so much more effectively. >> Danielle, can you comment >> If I could... >> on the AWS side because this is again on the big point. You guys are going next level, and you're starting to see patterns in the ISV world, certainly on the architecture side of partners doing things differently now on top of what they've already done. Could you share how AWS is helping customers accelerate? >> Well, just as Morgan was talking about what OpenTelemetry provides, you can see how from a partnership perspective, this is so valuable, right? What the partner team here at AWS is in the business of doing, is really enabling customer choice, right? And having that ability to plug in and pull data from different sources, post it to different sources, make it available for visibility across all of your resources is very powerful and it's something from the partner community that we really value because we want customers to be able to select best of breed solutions, what works for their business, which businesses are different and they may have different needs, and that also fosters that true innovation. A small company is going to develop and release software a lot differently than a large enterprise. And so, being able to support something like OpenTelemetry just enables that for all different kinds of customers. >> Morgan, add to that because the velocity of releases, certainly operational, stability, is key every predominant security, uptime, these are top concerns. And, you mention data too, >> And you mention challenges. >> You got the data in here. So you got a lot of data moving around, a lot of value. What's your take? >> Yeah. So, I'll speak with some specifics. So a challenge that developers have had for years when you're developing large services, which you can now do with platforms like AWS. So, it's very easy to go develop huge deployments. But a challenge they have is you go and build a mess, right? And like, I've worked earlier in my career in Web Services. And I remember in one of the first orgs I was in, I was one of the five people who really understood our ecommerce stack. Right? And so like, I would get dragged into all these meetings and I'd have to go draw like the 50 services we had, and how they interacted, and the changes that were made in the last week. And without observability tools like Splunk Observability Cloud, like the ones offered by Amazon, like the ones that are backed by the data that comes with OpenTelemetry, organizations basically rely on people like this, to go draw out their deployments so they understand what it is they've built. Well, as you can imagine, this crimps your development velocity, because most of your engineers, most of your tech leads, most of everyone else don't actually understand what it is they've built what it is they're running, because they need that global context. You get something like OpenTelemetry and the solutions that consume the data from it, and suddenly now, all your developers have that context, all of them when they're adding functionality to a service or they're updating their infrastructure, can actually understand how it interacts with the rest of the broader application. This lets you speed up your time to development, this lets you ship more safely, more securely. And finally, when things do go wrong, which will be less frequent, but when they do go wrong, you can fix them super rapidly. >> If I'm a customer, let me ask a question. I'm a customer and I say, "Okay, I love AWS, I love Splunk, I love OpenTelemetry. I got to have open sources, technology innovation is happening." What's the integration? What are some of the standards? Can you take us through how that's working together with you guys as a shared platform? >> Yeah. So let's take the Amazon distribution for OpenTelemetry or even the Splunk one. One of the first things they do is they include all of the receivers, all of the sort of data capture components that you need, out of box for platforms like AWS, right? And so, right away, you get that power and flexibility where you're getting access to all of these data sources, right? And so, that's part of that partnership. And additionally, once the data comes into OpenTelemetry, you can now send that to various different data sources, including, as Danielle mentioned, to multiple at the same time. So you can use whatever tools you want. And so when you talk about like what the partnership is actually providing to you as a customer and still, this is just within the context of OpenTelemetry, obviously there's a much broader partnership between these two companies than just that. But within the context of OpenTelemetry means you can download one of these distributions. It's fully supported. It works with both solutions and everything is just great, right? You don't need to go fiddle with that out of the box. To be clear, OpenTelemetry is a batteries included project, right? This means that even the standard distributions of OpenTelemetry include the components you need. You have to go directly, reference them and ensure that they're packaged in there, but they exist, right. But the nice thing about these distributions is that it's done, it's out of the box, you don't even have to worry about is something missing or do I need to include new exporters or new receivers? It's all there. It's preconfigured. It just works. And if something goes wrong and you have a support contact, you pick up the phone, you talk to someone to get it fixed. >> Danielle, what's the Amazon side 'cause agility and scale is one of the highlights you guys are seeing. How does this tie into that and how are you guys working backwards from the customers to support the partners? >> Well, I think just to add on essentially to what Morgan said, I think that AWS is a cloud platform, has always really had a focus on developers. And, we talk a lot about how AWS and Amazon as a whole really embraces this continuous integration and continuous deployment methods inside of our organization. And we talk about services, and observability is a huge part of that. The only way that you're actually able to release hundreds, thousands of times a day like Amazon does, is by having an observability platform, to be able to measure metrics, see changes in the environment, to be able to roll back if you need to, and to be able to quickly mitigate any challenges or anything that goes wrong at any part of the process. And so, when we preach that to our customers, I think it's something that we do that because we live it and breathe it. And so, things such as OpenTelemetry and such as the products that Splunk builds, those are also ways in which we believe our customers can achieve that. >> Yeah. And we can... I mean, as I mentioned before, this partnership goes well beyond OpenTelemetry, right? And so, if you go use like Splunk Enterprise, Enterprise Cloud, Splunk Observability Cloud, and you're running on AWS, you have excellent support and excellent visibility into your Amazon infrastructure, into the services and applications you've deployed on top of that infrastructure. We try and give you, and I think we do succeed in this. We give you the best possible experience, the deepest possible visibility, into what it is you've deployed on AWS, so that you can be even more successful as a business, and so that you can be even more successful on AWS as a platform. >> Yeah. This is a great conversation, Morgan. You mentioned the early days of Web Services. AWS stands for Amazon Web Services built on web services. So interesting throwback there, but made me think about the days of the early days of web services. And if you look at data, what's going on now, the top partners in AWS, you're seeing a lot of people thinking about data differently, they're refactoring, a lot of machine learning, a lot of AI going on at scale. So then, you got cloud native, things like Kubernetes and these new services being stood up and teared down with automation. A whole new operating model's coming. And so when you think about observability, the importance of it, I mean, can you share your perspective on this whole 'nother level? I mean, I always say that whole another level sounds cliche, but it is next level. I mean, this is completely different. What's your reaction? >> Yeah. There there's a ton of factors here, right? So as you point out, companies are totally shifting how they use their cloud infrastructure. And part of this you see during their cloud migrations, a part of it you see after, and they're shifting from their sort of stateful VMs that they may have had in the past to infrastructure that they tear down and put up regularly. And there's a lot more automation. With this, comes as I mentioned before, complexity, right? And also, with this comes more and more businesses becoming even more reliant on their digital infrastructure. And so, not having observability into your applications, into your services, into your infrastructure, to me, is akin to running a business, say running a large warehousing or distribution company, but not having any idea where you're shipping products or where things are, or not having any accounting or CFO, right? Like, business has become so digital. Business is so reliant on technology, and that's unlocked a ton of new things. It's great. But not having visibility into how that technology works or what it is that's deployed or how to fix it is akin to having no visibility to anything else in your business. It's nuts. And so, observability is super, super critical, particularly for customers who are adopting this new wave of cloud technologies on platforms like AWS. >> Danielle, on your side too, you're enabling this new capability so that businesses can do it, the partners do it, we're calling it super cloud. We've been calling it super cloud kind of dynamic where new things are happening with the data. And you guys are evolving with that. Can you share what you're seeing on your side as your partners start to go to the next level? What are you guys doing? How does it all come together? >> Well, we always talk about what has happened with data in the last couple of years, which the cloud has really enabled around, you know, variety and velocity and there's one other "V" that's escaping me right now, but essentially, all of this data is coming in and providing the ability for us to make better decisions, to build better products, to provide better experiences for customers. And so, I just think, the OpenTelemetry project, as well as what Splunk is doing is just another example of how we're taking this massive amount of data and being able to provide better experiences and outcomes for customers. >> And you guys have been working along together for long time, Splunk, and, it's been a great partners, if we're going back with that been covering it on theCUBE and SiliconANGLE. So, we know that, the change is key observability. Can you imagine a company without a CFO, Morgan? That's just boggles your mind, but that's what it's like right now. So... >> It is, yeah. >> And the people who take advantage of that are winning, right? So it's like, that's the key. >> Yeah, I know. I mean, even in my own career, right, I've moved between different companies. And I remember, when I joined Google in particular, which is where I worked at previously, I was very impressed with their internal observability tools. And I'm certain, I haven't worked at Amazon. I'm certainly, I just assume inside of Amazon they're excellent as well, so a lot of the large cloud firms these days. But it was so refreshing going from an organization where if we had some outage or something went wrong, there were like a very small set of people who could actually understand what was going on. And then you would just have to manually dive through logs and correlate requests manually between services. It's very challenging. And so, when things went wrong, they went wrong for a long, long time. And so, the companies that understood this even in the past are already very successful as a result. I think now, the rest of the industry is really in the midst of adopting these observability practices and the tools that are required to implement them, because you're right. Otherwise your development velocity slows down. Now you're getting out competed by your competition. And then, when you have a problem, it blows up for ages. And once again, your competition can take advantage of it. >> And, can you just summarize the observability piece relative to the OpenTelemetry? Where is that going to go? Where do you see that evolving? >> Sure. >> I see open source is growing like crazy, we all know that. >> Of course. >> But OpenTelemetry in particular and open source, 'cause this is a big hot area. >> Yes. So to set the stage for people, OpenTelemetry, unlocks observability in many ways. As I mentioned earlier, OpenTelemetry is how you capture data out of your application. It doesn't process it. It's not a replacement for something like Amazon CloudWatch or any Splunk's products, but it's how we get the data out of your system, which is a remarkably difficult problem. I won't dive into it today, but, those who work in this space are very aware. That's why this project exists and it's so big, that actually extracting information, metrics, logs, distributed traces, profiles, everything else, from your applications and from your infrastructure is very, very difficult. So for OpenTelemetry, where it's going is just continually getting better at extracting more types of data from more sources, and doing that more effectively for people in a more standardized way. That will unlock firms like Splunk, firms, like Amazon and others to better process this data. In terms of where that's going, the sky's the limit, right? Like, everyone's familiar with APM, people are familiar with infrastructure monitoring, but there's a lot more capabilities coming there for security analytics, for network performance monitoring, for getting down all the way to single lines of coding your application, how they impact everything. There's just so much power that's coming to the industry right now. I'm really excited to see where things go in the next few years. >> And Danielle, you're in the middle of all the action as a solution architect, really set the stage for their companies and the ISVs, and this is a big, hot area. What are the patterns you're seeing and what are some of the best practices that you're doing will help companies? >> Right. So I think, summarizing our entire conversation, the big things that we're seeing in the market is essentially more and more companies are looking to move to a continuous deployment and a continuous integration environment. And they're looking to innovate faster and spend less time hot patching or hot fixing their environments and they want to spend more time innovating. And so, that you know, the patterns that we're seeing is... What I see and what I actually experience firsthand at re:Invent when I talk to probably over 40 or 50 ISVs, is customers want to know in their environment, where are their changes? Where are their security vulnerabilities? Where are their data changes, and what are customers really experiencing, whether it's latency, poor experience throughout their products, those types of things? So security, data, and observability are just key to all of that experience and that's what we're definitely seeing as patterns, what we're seeing with our customers and also what value our ISVs are providing in that space. >> That's awesome. And the other thing I would observe is that there's more of an integration story going on around joint projects, whether it's open source. >> Absolutely. >> Because this is where we want to get that services connected. And it's mutual beneficial. I mean, this is really >> Exactly. >> whole 'nother, new kind of interoperable cloud scale. >> Yeah, if I could say one thing else there, I think that, a lot of the customers who are trying to move into the cloud now are, maybe not technology forward companies and they really need that solution. And that's very important. I think COVID has pushed a lot of companies into the cloud maybe very quickly. And, that has been something else we've observed in the market. So, solutions and full solutions between ISVs and ISVs, or ISVs and AWS is just becoming more and more common thing that we see. >> And, you mentioned John, in the open source space as well. Like, we're certainly from Amazon to Splunk. So we're talking a lot about those, but there's a lot of other firms involved in projects like OpenTelemetry. And I think it's very endearing, very heartening to see how well they cooperate in this community and how, when their interests are aligned, how effective they can be. And it's been very exciting to work in the space and very pleasant, honestly, to see everything come together with this huge set of customers and partners. >> Yeah. The pleasant surprise of the pandemic has been that people come into the cloud and they like it and they, "Hey, this works," and they double down on it. Then they realize, there's more there and they refactor. So, you're seeing real examples of that. So, this is a great discussion, great success story. Congratulations Morgan, Danielle. >> Thank you. >> Great partnership between Splunk and AWS. We've been following for a long time. And again, this highlights this whole another level of integrating super cloud kind of experience where people are getting more capabilities and doing more together, so great stuff. >> And this is just one facet of that, right? Like, there's all the other connections of Splunk Enterprise, Splunk security analytics products, and others. It's a deep, deep partnership between these firms. >> Yeah. And the companies that innovate and get that new capability are going to have an advantage. And you're seeing... >> Yes. >> Right? >> Agreed. >> And this is awesome, and great stuff, thank you for coming on and sharing that insight. >> Thank you. >> Congratulations Morgan over there at Splunk, great stuff. And Danielle, thanks for coming on and sharing the AWS perspective. >> Thanks for having me. >> And you guys are going to the next level. You moving up to stack as they say, all good stuff for customers. Thanks. >> Thank you. >> Okay. >> Thank you. >> This is season one, episode two of the AWS Partner Showcase. I'm John Furrier with theCUBE. Thanks for watching. (gentle music)

(gentle music) >> Hello, welcome to theCUBE's presentation of the AWS Showcase season one, episode two with the ISV Startups partners. I'm John Furrier, your host of theCUBE. We're joined by Morgan McLean, director of product management at Splunk, and Danielle Greshock, who is the director of ISVs solution architects at AWS. Welcome to the show. Thanks for coming on. >> Thanks for having us. >> And great. Thanks for having us. >> Great to see both of you, both theCUBE alumni, but the Splunk-AWS relationship has been going very, very well. You guys are doing great business enabling this app revolution. And cloud scale has been going extremely well. So let's get into it. You guys are involved in a lot of action around application revolution, around OpenTelemetry and open source. So let's get into it. What's the latest? >> Danielle, you go ahead. >> Well, I'll just jump in first. Obviously last year, not last year, but in 2020, we launched the AWS Distro for OpenTelemetry. The idea being essentially, we're able to bring in data from partners, from infrastructure running on AWS, from apps running on AWS, to really be able to increase observability across all cloud assets at your entire cloud platform. So, Morgan, if you want to chime in on how Splunk >> Morgan: Certainly. >> has worked out OpenTelemetry. >> Yeah. I mean, OpenTelemetry is super exciting. Obviously, there's a lot of partnership points between Amazon and Splunk, but OpenTelemetry is probably one of them that's the most visible to people who aren't already maybe using these two products together. And so, as Danielle mentioned, Amazon has their own distribution of OpenTelemetry, Splunk has their own, as well, and of course there's the main open source distribution that everybody knows and loves. Just for our viewers, just for clarity's sake, the separate distributions are fundamentally very similar to, almost identical to what's offered in the open source space, but they come preconfigured and they come with support guarantees from each company, meaning that you can actually get paid full support for an open source project, which is really fantastic for customers. And as Danielle mentioned, it's a great demonstration of the alliance between Splunk and Amazon Web Services. For example, the AWS Distro, when you use it, can export data to Amazon CloudWatch, various Amazon backed open source initiatives like Prometheus and others, and to Splunk Observability Cloud and to Splunk Enterprise. So it's a place that we've worked very closely together, and it's something that we're very excited about. >> So, Morgan, I want to get your take on the on the product management side and also how product are built these days. >> One of the big things we're seeing in cloud is that open source has been the big enabler for a lot of refactoring. And you got multiple distributions, but the innovations on top of that, can you talk about how you see the productization of new innovations with open source as you guys go into this market, because this is the new dynamic with cloud. We're seeing examples all over the place. Obviously, Amazon's going next level with what they're doing, and that open source, it's not a one game for all of it. You can have mix and match. Take us through the product angle. >> And in many ways, this is just another wave of the same thing, right? Like, if you think back in time, we all used and still use in many cases, virtual machines, most of those are based on Linux, right? Another large open source project. And so, open source software has been accelerating innovation in the cloud space and in the computing space generally for a very long time, which is fantastic. Our excitement with something like OpenTelemetry comes from both the project's capabilities but also what we can do with it. So for those who aren't already familiar with OpenTelemetry, OpenTelemetry allows you to extract really critical system telemetry, application signals and everything else you need from your own applications, from new services, from your infrastructure, from everything that you're running in a cloud environment. You can then send that data to another location for processing. And so John, you ask like, how does this accelerate innovation? What does it unlock? Well, the insight you can gain from this data means you can become so much more efficient as a development organization. You can make your applications so much more effective because when you send that data to something like Splunk Observability Cloud, to something like Amazon CloudWatch, to various other solutions on the market, they can give you deep, deep insight into your application's performance, to its structure, they can help you reduce outages. And so, it's very, very powerful because it allows organizations to use tools like Splunk, like Amazon, like other things to innovate so much more effectively. >> Danielle, can you comment >> If I could... >> on the AWS side because this is again on the big point. You guys are going next level, and you're starting to see patterns in the ISV world, certainly on the architecture side of partners doing things differently now on top of what they've already done. Could you share how AWS is helping customers accelerate? >> Well, just as Morgan was talking about what OpenTelemetry provides, you can see how from a partnership perspective, this is so valuable, right? What the partner team here at AWS is in the business of doing, is really enabling customer choice, right? And having that ability to plug in and pull data from different sources, post it to different sources, make it available for visibility across all of your resources is very powerful and it's something from the partner community that we really value because we want customers to be able to select best of breed solutions, what works for their business, which businesses are different and they may have different needs, and that also fosters that true innovation. A small company is going to develop and release software a lot differently than a large enterprise. And so, being able to support something like OpenTelemetry just enables that for all different kinds of customers. >> Morgan, add to that because the velocity of releases, certainly operational, stability, is key every predominant security, uptime, these are top concerns. And, you mention data too, >> And you mention challenges. >> You got the data in here. So you got a lot of data moving around, a lot of value. What's your take? >> Yeah. So, I'll speak with some specifics. So a challenge that developers have had for years when you're developing large services, which you can now do with platforms like AWS. So, it's very easy to go develop huge deployments. But a challenge they have is you go and build a mess, right? And like, I've worked earlier in my career in Web Services. And I remember in one of the first orgs I was in, I was one of the five people who really understood our ecommerce stack. Right? And so like, I would get dragged into all these meetings and I'd have to go draw like the 50 services we had, and how they interacted, and the changes that were made in the last week. And without observability tools like Splunk Observability Cloud, like the ones offered by Amazon, like the ones that are backed by the data that comes with OpenTelemetry, organizations basically rely on people like this, to go draw out their deployments so they understand what it is they've built. Well, as you can imagine, this crimps your development velocity, because most of your engineers, most of your tech leads, most of everyone else don't actually understand what it is they've built what it is they're running, because they need that global context. You get something like OpenTelemetry and the solutions that consume the data from it, and suddenly now, all your developers have that context, all of them when they're adding functionality to a service or they're updating their infrastructure, can actually understand how it interacts with the rest of the broader application. This lets you speed up your time to development, this lets you ship more safely, more securely. And finally, when things do go wrong, which will be less frequent, but when they do go wrong, you can fix them super rapidly. >> If I'm a customer, let me ask a question. I'm a customer and I say, "Okay, I love AWS, I love Splunk, I love OpenTelemetry. I got to have open sources, technology innovation is happening." What's the integration? What are some of the standards? Can you take us through how that's working together with you guys as a shared platform? >> Yeah. So let's take the Amazon distribution for OpenTelemetry or even the Splunk one. One of the first things they do is they include all of the receivers, all of the sort of data capture components that you need, out of box for platforms like AWS, right? And so, right away, you get that power and flexibility where you're getting access to all of these data sources, right? And so, that's part of that partnership. And additionally, once the data comes into OpenTelemetry, you can now send that to various different data sources, including, as Danielle mentioned, to multiple at the same time. So you can use whatever tools you want. And so when you talk about like what the partnership is actually providing to you as a customer and still, this is just within the context of OpenTelemetry, obviously there's a much broader partnership between these two companies than just that. But within the context of OpenTelemetry means you can download one of these distributions. It's fully supported. It works with both solutions and everything is just great, right? You don't need to go fiddle with that out of the box. To be clear, OpenTelemetry is a batteries included project, right? This means that even the standard distributions of OpenTelemetry include the components you need. You have to go directly, reference them and ensure that they're packaged in there, but they exist, right. But the nice thing about these distributions is that it's done, it's out of the box, you don't even have to worry about is something missing or do I need to include new exporters or new receivers? It's all there. It's preconfigured. It just works. And if something goes wrong and you have a support contact, you pick up the phone, you talk to someone to get it fixed. >> Danielle, what's the Amazon side 'cause agility and scale is one of the highlights you guys are seeing. How does this tie into that and how are you guys working backwards from the customers to support the partners? >> Well, I think just to add on essentially to what Morgan said, I think that AWS is a cloud platform, has always really had a focus on developers. And, we talk a lot about how AWS and Amazon as a whole really embraces this continuous integration and continuous deployment methods inside of our organization. And we talk about services, and observability is a huge part of that. The only way that you're actually able to release hundreds, thousands of times a day like Amazon does, is by having an observability platform, to be able to measure metrics, see changes in the environment, to be able to roll back if you need to, and to be able to quickly mitigate any challenges or anything that goes wrong at any part of the process. And so, when we preach that to our customers, I think it's something that we do that because we live it and breathe it. And so, things such as OpenTelemetry and such as the products that Splunk builds, those are also ways in which we believe our customers can achieve that. >> Yeah. And we can... I mean, as I mentioned before, this partnership goes well beyond OpenTelemetry, right? And so, if you go use like Splunk Enterprise, Enterprise Cloud, Splunk Observability Cloud, and you're running on AWS, you have excellent support and excellent visibility into your Amazon infrastructure, into the services and applications you've deployed on top of that infrastructure. We try and give you, and I think we do succeed in this. We give you the best possible experience, the deepest possible visibility, into what it is you've deployed on AWS, so that you can be even more successful as a business, and so that you can be even more successful on AWS as a platform. >> Yeah. This is a great conversation, Morgan. You mentioned the early days of Web Services. AWS stands for Amazon Web Services built on web services. So interesting throwback there, but made me think about the days of the early days of web services. And if you look at data, what's going on now, the top partners in AWS, you're seeing a lot of people thinking about data differently, they're refactoring, a lot of machine learning, a lot of AI going on at scale. So then, you got cloud native, things like Kubernetes and these new services being stood up and teared down with automation. A whole new operating model's coming. And so when you think about observability, the importance of it, I mean, can you share your perspective on this whole 'nother level? I mean, I always say that whole another level sounds cliche, but it is next level. I mean, this is completely different. What's your reaction? >> Yeah. There there's a ton of factors here, right? So as you point out, companies are totally shifting how they use their cloud infrastructure. And part of this you see during their cloud migrations, a part of it you see after, and they're shifting from their sort of stateful VMs that they may have had in the past to infrastructure that they tear down and put up regularly. And there's a lot more automation. With this, comes as I mentioned before, complexity, right? And also, with this comes more and more businesses becoming even more reliant on their digital infrastructure. And so, not having observability into your applications, into your services, into your infrastructure, to me, is akin to running a business, say running a large warehousing or distribution company, but not having any idea where you're shipping products or where things are, or not having any accounting or CFO, right? Like, business has become so digital. Business is so reliant on technology, and that's unlocked a ton of new things. It's great. But not having visibility into how that technology works or what it is that's deployed or how to fix it is akin to having no visibility to anything else in your business. It's nuts. And so, observability is super, super critical, particularly for customers who are adopting this new wave of cloud technologies on platforms like AWS. >> Danielle, on your side too, you're enabling this new capability so that businesses can do it, the partners do it, we're calling it super cloud. We've been calling it super cloud kind of dynamic where new things are happening with the data. And you guys are evolving with that. Can you share what you're seeing on your side as your partners start to go to the next level? What are you guys doing? How does it all come together? >> Well, we always talk about what has happened with data in the last couple of years, which the cloud has really enabled around, you know, variety and velocity and there's one other "V" that's escaping me right now, but essentially, all of this data is coming in and providing the ability for us to make better decisions, to build better products, to provide better experiences for customers. And so, I just think, the OpenTelemetry project, as well as what Splunk is doing is just another example of how we're taking this massive amount of data and being able to provide better experiences and outcomes for customers. >> And you guys have been working along together for long time, Splunk, and, it's been a great partners, if we're going back with that been covering it on theCUBE and SiliconANGLE. So, we know that, the change is key observability. Can you imagine a company without a CFO, Morgan? That's just boggles your mind, but that's what it's like right now. So... >> It is, yeah. >> And the people who take advantage of that are winning, right? So it's like, that's the key. >> Yeah, I know. I mean, even in my own career, right, I've moved between different companies. And I remember, when I joined Google in particular, which is where I worked at previously, I was very impressed with their internal observability tools. And I'm certain, I haven't worked at Amazon. I'm certainly, I just assume inside of Amazon they're excellent as well, so a lot of the large cloud firms these days. But it was so refreshing going from an organization where if we had some outage or something went wrong, there were like a very small set of people who could actually understand what was going on. And then you would just have to manually dive through logs and correlate requests manually between services. It's very challenging. And so, when things went wrong, they went wrong for a long, long time. And so, the companies that understood this even in the past are already very successful as a result. I think now, the rest of the industry is really in the midst of adopting these observability practices and the tools that are required to implement them, because you're right. Otherwise your development velocity slows down. Now you're getting out competed by your competition. And then, when you have a problem, it blows up for ages. And once again, your competition can take advantage of it. >> And, can you just summarize the observability piece relative to the OpenTelemetry? Where is that going to go? Where do you see that evolving? >> Sure. >> I see open source is growing like crazy, we all know that. >> Of course. >> But OpenTelemetry in particular and open source, 'cause this is a big hot area. >> Yes. So to set the stage for people, OpenTelemetry, unlocks observability in many ways. As I mentioned earlier, OpenTelemetry is how you capture data out of your application. It doesn't process it. It's not a replacement for something like Amazon CloudWatch or any Splunk's products, but it's how we get the data out of your system, which is a remarkably difficult problem. I won't dive into it today, but, those who work in this space are very aware. That's why this project exists and it's so big, that actually extracting information, metrics, logs, distributed traces, profiles, everything else, from your applications and from your infrastructure is very, very difficult. So for OpenTelemetry, where it's going is just continually getting better at extracting more types of data from more sources, and doing that more effectively for people in a more standardized way. That will unlock firms like Splunk, firms, like Amazon and others to better process this data. In terms of where that's going, the sky's the limit, right? Like, everyone's familiar with APM, people are familiar with infrastructure monitoring, but there's a lot more capabilities coming there for security analytics, for network performance monitoring, for getting down all the way to single lines of coding your application, how they impact everything. There's just so much power that's coming to the industry right now. I'm really excited to see where things go in the next few years. >> And Danielle, you're in the middle of all the action as a solution architect, really set the stage for their companies and the ISVs, and this is a big, hot area. What are the patterns you're seeing and what are some of the best practices that you're doing will help companies? >> Right. So I think, summarizing our entire conversation, the big things that we're seeing in the market is essentially more and more companies are looking to move to a continuous deployment and a continuous integration environment. And they're looking to innovate faster and spend less time hot patching or hot fixing their environments and they want to spend more time innovating. And so, that you know, the patterns that we're seeing is... What I see and what I actually experience firsthand at re:Invent when I talk to probably over 40 or 50 ISVs, is customers want to know in their environment, where are their changes? Where are their security vulnerabilities? Where are their data changes, and what are customers really experiencing, whether it's latency, poor experience throughout their products, those types of things? So security, data, and observability are just key to all of that experience and that's what we're definitely seeing as patterns, what we're seeing with our customers and also what value our ISVs are providing in that space. >> That's awesome. And the other thing I would observe is that there's more of an integration story going on around joint projects, whether it's open source. >> Absolutely. >> Because this is where we want to get that services connected. And it's mutual beneficial. I mean, this is really >> Exactly. >> whole 'nother, new kind of interoperable cloud scale. >> Yeah, if I could say one thing else there, I think that, a lot of the customers who are trying to move into the cloud now are, maybe not technology forward companies and they really need that solution. And that's very important. I think COVID has pushed a lot of companies into the cloud maybe very quickly. And, that has been something else we've observed in the market. So, solutions and full solutions between ISVs and ISVs, or ISVs and AWS is just becoming more and more common thing that we see. >> And, you mentioned John, in the open source space as well. Like, we're certainly from Amazon to Splunk. So we're talking a lot about those, but there's a lot of other firms involved in projects like OpenTelemetry. And I think it's very endearing, very heartening to see how well they cooperate in this community and how, when their interests are aligned, how effective they can be. And it's been very exciting to work in the space and very pleasant, honestly, to see everything come together with this huge set of customers and partners. >> Yeah. The pleasant surprise of the pandemic has been that people come into the cloud and they like it and they, "Hey, this works," and they double down on it. Then they realize, there's more there and they refactor. So, you're seeing real examples of that. So, this is a great discussion, great success story. Congratulations Morgan, Danielle. >> Thank you. >> Great partnership between Splunk and AWS. We've been following for a long time. And again, this highlights this whole another level of integrating super cloud kind of experience where people are getting more capabilities and doing more together, so great stuff. >> And this is just one facet of that, right? Like, there's all the other connections of Splunk Enterprise, Splunk security analytics products, and others. It's a deep, deep partnership between these firms. >> Yeah. And the companies that innovate and get that new capability are going to have an advantage. And you're seeing... >> Yes. >> Right? >> Agreed. >> And this is awesome, and great stuff, thank you for coming on and sharing that insight. >> Thank you. >> Congratulations Morgan over there at Splunk, great stuff. And Danielle, thanks for coming on and sharing the AWS perspective. >> Thanks for having me. >> And you guys are going to the next level. You moving up to stack as they say, all good stuff for customers. Thanks. >> Thank you. >> Okay. >> Thank you. >> This is season one, episode two of the AWS Partner Showcase. I'm John Furrier with theCUBE. Thanks for watching. (gentle music)

(upbeat music) >> Welcome back to theCUBE's continuous coverage of AWS re:Invent 2021 I'm Lisa Martin. This is our third day here on set We've got two live sets, two remote studios, over a hundred guests on the program and a lot going on with AWS and its ecosystem of partners am pleased to welcome back one of our Cube alumni, Buddy Brewer, the GVP & GM of product partnerships at New Relic. Welcome back, Buddy. Good to have you. >> Thanks it's great to be here >> Great to be in an in-person event isn't? >> No kidding it's really amazing to see everybody out here and after spending so much time on zoom calls, we had a lot of really great moments among the team and the booth playing the game of seeing if people's height matched up with >> (laughs) >> What your expectation was because so many of the people we work with >> Never mind. >> We've only known over zoom. >> Yes ,and zoom has been a savior for all of us we've been doing so much recording on zoom at the same time it's great to be here in person and seeing what a safe job AWS has done with getting I from hearing upwards of 30,000 people in here that are here in person. So talk to me about you lead the technology partnerships at New Relic. Talk to me about your role, and then we'll get into the partnership with AWS. >> Yeah, absolutely. Well, you know, the point about zoom, it's fascinating. Like you said, that just having the ability to communicate with people has been such a key enabler of being able to make progress and to continue to lead our personal and our professional lives despite the pandemic I mean, imagine what it would have been like if this had happened 10 years ago, even, but certainly 50 years ago >> Right. or something like that, right? Like everything would have ground to a halt and technology took on such an amazing, you know, critical role in allowing us to do all of these things and so at New Relic, we're all about helping people make sure that all of this software works correctly. And so observability helps people understand the detail level about everything from the front end, the end user experience to every single piece that happens along the path of delivering that experience all the way down to the infrastructure into the network. But my role at New Relic is also to help all of the other tools that software developers use every day to create those experiences that they connect into their observability platform so that they can understand all of those details and make sure that people are able to continue doing things that have become really so basic to life like ordering groceries or getting food, or, you know, communicating with a loved one over something like zoom. >> Yeah the things that to your point, if this had happened, you know, five, 10 years ago, it would have been a completely different story. We've been able to function really well and one of the things too, that, you know, I noticed yesterday and today, you probably did as well with the plethora, typical AWS the plethora of announcements, the amount of innovation that's going on, the customer flywheel that we've just seen this acceleration of technology and what it's enabling, but the observability portion is really key you talk about, you know, the developers need to the whole SDLC they need to be able to understand exactly what's going on because at the end of the day, whether it's a consumer or an enterprise of the other end of the spectrum, we need to know exactly what's going on because people's patience is far thinner these days the pandemic showed is that there is really no having access to real-time data. Isn't a luxury anymore it's really a necessity. >> Right, yeah, absolutely. >> Talk to me about some of these so a lot of announcements coming up from AWS, you guys talk to me about the partnership, what you guys are doing there. And some of the things that are exciting on that front. >> Yeah, AWS is a really key partner for us. We're big users of AWS ourselves for our observability platform and all of our infrastructure and, you know, we've had our own journey as a 13 year old business that started out pre cloud and moving our own infrastructure to the cloud. And then along that journey, we've worked closely with AWS and we've built a lot of joint solutions to help people who are moving to the cloud themselves or who are cloud native to understand all of the details about what's happening in that software so we have over 60 different integrations to all of the different tools with Amazon that you can use on the cloud from data storage, to EKS on Fargate and all of that stuff. And then we recently announced a five-year strategic agreement with Amazon to make it even easier for customers to adopt New Relic if they're building in Amazon AWS and so you know, we're in their marketplace, we have an offering for startups, for people who are just getting started that, you know, provides really simple and fast on-ramps with discounts and things like that. That's all designed to help people, software developers in particular, focus on what matters most to them, which is building great experiences for their customers. You know, you mentioned that the SDLC and this is one of the things that, you know, our mission at New Relic is to make observability a daily data-driven habit for developers across all phases of the software delivery life cycle. The problem with observability and how it's used today is that it's only used in the run phase by most people they use it when the software is on fire to put the fire out we believe that, that telemetry has tremendous strategic value in the plan, build and deploy phases of software development as well. And so partnerships like AWS allow us to unlock the accessibility of that data across all of those different phases for people who software developers are as a result in many ways that the things that we were talking about earlier with the expectations that the pandemic has placed on how software has to work, it's not an option they're busier, they're under more pressure than they've ever been before and so we want to help them relieve that pressure with tools that help them do their jobs better. >> Relieving that pressure is key there is so much pressure on developers I mean, these days from observability to security and that sort of thing, but it sounds like one of the things that you're also fundamentally doing is really shifting that observability left and helping them from a cultural perspective, it seems like almost a shift, but you're trying to make things easier for them giving them more tools and to unlock what they're not seeing right now. >> That's right and you know, the interesting thing about it is everyone realizes that observability is critical to, you know, successful software businesses so for example, we did a survey recently of 1300 software developers and IT decision makers and executives, and found that among the C-level executives that were surveyed 80% of them expected to increase their observability budget and 20% of those expected to increase it significantly. However, that same survey found that a very small percentage of those who we actually surveyed feel that they have a mature observability practice today. And when we unpack the reasons why in the survey, we found that most of them reduce down to basically this issue of they just don't have enough time to instrument all of the software, especially in a world where the shift to the cloud has driven a change in architecture where monoliths have been torn down and replaced by hundreds, or may be even thousands of microservices. >> Right. >> And we're in an era now where if observability isn't really, really easy and incredibly fast and simple to execute on then software developers can no longer instrument fast enough to keep up with the pace of the software that they're delivering and so what that leads to is visibility gaps, visibility gaps lead to poor customer experiences. And so what we're trying to do, and we've been on this massive simplification of our own platform to make it, you know, incredibly cost-effective at just 25 cents a gigabyte for ingestion and really simple licensing seat based licensing, where you get access to all of our tools to make it really simple and to take simply minutes to get observability on all those different pieces. >> If simplicity is a word that we throw around a lot, but it's really critical element and it's interesting to understand how do you actually facilitate that? You talked about, you know, kind of the 80 20 rule there. >> Yeah. >> A lot of the organization's not on that maturity curve with observability, how does New Relic and its ecosystem of partners like AWS how do you help have those conversations within organizations in any industry tell them, understand how you can actually simplify that and unlock that visibility, knowing that it's not only a matter of software development, but it's a competitive differentiator. It's also something that can damage a brand if they're not top of it. >> Yeah, we launched a re-imagined version of our partner ecosystem really our entire integration ecosystem about six weeks ago on October 13th called New Relic Instant Observability. And one of the central goals of New Relic IO, which we call it for short is to make it take just like five minutes for people to instrument something. So in the old way, what people had to do is if they wanted observability, they had to go learn about an observability vendor then they had to go install it, figure out how all that works and then they could get to solving their problem, which might've just been simply instrumenting a Kafka you know and so what we want to do is just keep people in that mode if all you wanted to do is instrument Kafka, then go find the Kafka instrumentation tile on New Relic and observability and then there's a guided install process that takes you through that and at the end you've instrumented Kafka and if you want to add something else like EKS Fargate from Amazon, or if you want to add something else like a Java service, you can simply click more of those guidance installs and add within minutes in an incremental way without having to stop and do a whole vendor evaluation to do so in fact, one of the other things that we launched recently is a free tier that's free forever. So there's no trial process or anything you don't have to put in a credit card if all you want to do is instrument this one thing right now, you can go through this process provision a free account you get access to all of our functionality for one user and ingest up to a hundred gigabytes of telemetry data for free within minutes. And so what we're trying to do is take all of that adoption friction out so that people aren't fighting with their instrumentation so much, and again, they can get back to doing what they really want to do in the first place, which has built great experiences for their end users. >> Great experiences for the end users but that translates to employee experience that translates to an end user customer experience, which translates back to brand reputation. I'm just wondering, you know, you're focused on the developers and we've been hearing a lot about the last two and a half days, a big focus on developers has observability kind of escalated up and its evolution up the stack within organizations is this a C-suite concern? Is this a board level concern? where does this fit now? and what's the vision of New Relic to deliver on that? >> With observability? >> Yes. >> Yeah, 90% of those in the survey that I was talking about felt that observability was not just a tool that they needed to use, but strategically critical to their business and, you know, this goes back to, as we know, and especially as a result of the intensity on the importance of software coming out of the pandemic, your digital business is your business these days. And so if you don't understand what's happening in that software and you can't move quickly, then you know you're really in trouble in terms of trying to succeed in a highly competitive environment and that goes back to again, one of our core beliefs is that all of this telemetry data that people have been collecting about how their software operates is so useful in contexts outside of just when there's a problem in production. Imagine if you could take that information and you could actually put it inside the IDE, which is something that we did with a recent acquisition of a company called CodeStream. We can take this telemetry data and put it inside the IDE so that as developers are writing the software, they know where those issues are. You can click straight from a stack frame, for example, inside of our, where we show all of our errors in a capability called Error's inbox and shoot right into your IDE and go see where the line of code is that caused that error, shortening that feedback loop and unlocking this really big investment that a lot of companies make in telemetry data earlier in the software life cycle, we believe is the future of observability and we want to help people get there. >> Well, the observability is really key for organizations these days because we've been hearing every company these days has to be a data company. >> Yeah. >> And it's one thing to say that it's a whole other thing to be able to implement it and observability is absolutely critical to that as being able to take that data and apply it in different contexts to really enable that business to be digital which is absolutely table-stakes these days to be successful and to deliver that customer experience ultimately. >> Yeah. >> That's what it all do. >> Yeah, absolutely. And you know, the other thing is really hard about this problem when I talk with our customers and we found this in the survey as well, is that, you know, software developers, don't just use one tool to create software they use a lot of tools in fact, 13% of those that we surveyed use 10 or more tools. >> Whoa. >> Just for the observability piece. And so, you know, obviously we're always trying to expand organically what we do inside of our platform to cover more and more use cases, but an equally important part of our strategy, if we really want to make observability a data-driven daily habit for people is to find all of those other, you know, really well-built amazing tools that those developers use and find valuable ways to integrate with them. And so that's the other part of our ecosystem that we've built out is this ability to take all of the other tools that you use and wire them into New Relic so that, for example, if you're using, let's say Lacework for security then you can, you know, if someone's installed a Bitcoin miner on your infrastructure somewhere, you can quickly navigate because of that integration from a poor customer experience through the infrastructure that's suffering may be with, you know, a lot of memory pressure, and a lot of CPU being used for this Bitcoin miner and then find out that, you know, through the integration where the miner was installed, how it got installed so that you can remediate those types of issues and connecting those pieces together, making software truly interoperable is another thing that's really critical to our mission at New Relic. >> It is critical to not only to the developers, but to the organizations and their success as businesses these days Buddy thank you for joining me, talking about what's going on at New Relic What's new, how you're really empowering those developers and all of the downstream positive effects that, that leads to we appreciate your time. >> Thank you ,thanks for having me. >> All right, you are Buddy Brewer I'm Lisa Martin you're watching theCUBE, the global leader in live tech coverage. (soft music)

>> Announcer: From theCUBE studios in Palo Alto and Boston, connecting with thought leaders all around the world, this is a CUBE Conversation. >> Hello and welcome to this special CUBE Conversation here in the Palo Alto studios, I'm John Furrier, host of theCUBE, for this Leading with Observability series with Under the Hood with Splunk Observability, I'm John Furrier with Arijit Mukherji with Splunk, he's a distinguished engineer, great to have you on. These are my favorite talks. Under the Hood means we're going to get all the details, what's powering observability, thanks for coming on. >> It's my pleasure, John, it's always nice to talk to you. >> Leading with Observability is the series, want to take a deep dive look across the spectrum of the product, the problems that it's solving, but Under the Hood is a challenge, because, people are really looking at coming out of COVID with a growth strategy, looking at cloud-native, Kubernetes, you're starting to see microservices really be a big part of that, in real deployments, in real scale. This has been a theme that's been growing, we've been covering it. But now, architectural decisions start to emerge. Could you share your thoughts on this, because this becomes a big conversation. Do you buy a tool here, how do you think it through, what's the approach? >> Exactly, John. So it's very exciting times in some sense, with observability right now. So as you mentioned and discussed a few times, there's a bunch of trends that are happening in the industry which is causing a renewed interest in observability, and also an appreciation of the importance of it, and observability now as a topic, it's like a huge umbrella topic, it covers many many different things like APM, your infrastructure monitoring, your logging, your real user monitoring, your digital experience management, and so on. So it's quite a set of things that all fall under observability, and so the challenge right now, as you mentioned, is how do we look at this holistically? Because, I think at this point, it is so many different parts to this edifice, to this building, that I think having a non-integrated strategy where you just maybe go buy or build individual pieces, I don't think that's going to get you very far, given the complexity of what we're dealing with. And frankly, that's one of the big challenges that we, as architects within Splunk, we are scratching our heads with, is how do we sort of build all of this in a more coherent fashion? >> You know, one of the things, Arijit, I want to get your thoughts on is because, I've been seeing this trend and, we've been talking about it on theCUBE a lot around systems thinking, and if you look at the distributed computing wave, from just go back 20 years and look at the history of how we got here, a lot of those similar concepts are happening again, with the cloud, but not as simple. You're seeing a lot more network, I won't say network management, but observability is essentially instrumentation of the traffic and looking at all the data, to make sure things like breaches and cybersecurity, and also making systems run effectively, but it's distributed computing at the end of it, so there's a lot of science that's been there, and now new science emerging around, how do you do this all? What's your thoughts on this, because this becomes a key part of the architectural choices that some companies have to make, if they want to be in position to take advantage of cloud-native growth, which is multifold benefits, and your product people talk about faster time to market and all that good stuff, but these technical decisions matter, can you explain? >> Yes, it absolutely does. I think the main thing that I would recommend that everybody do, is understand why observability, what do you want to get out of it? So it is not just a set of parts, as I mentioned earlier, but it brings direct product benefits, as we mentioned, like faster mean time to resolution, understanding what's going on in your environment, having maybe fewer outages at the same time, understanding your causes, so many different benefits. So the point is not that one has the ability to do maybe (indistinct) or ability to do infrastructure (indistinct), the main question is aspirationally, what are my goals that are aligned to what my business wants? So what do I want to achieve, do I want to innovate faster? In that case, how is observability going to help me? And this is sort of how you need to define your strategy in terms of what kind of tools you get and how they work together. And so, if you look at what we're doing at Splunk, you'll notice it's extremely exciting right now, there's a lot of acquisitions happening, a lot of products that we're building, and the question we're asking as architects is, suppose we want to use, that will help us achieve all of this, and at the same time be somewhat future-proofed. And I think any organization that's either investing in it, or building it, or buying it, they all would probably want to think along those lines. Like what are my foundational principles, what are the basic qualities I want to have out of this system? Because technologies and infrastructures will keep on changing, that's sort of the rule of nature right now. The question is how do we best address it in a more future-proofed system? At Splunk, we have come up with a few guiding principles, and I'm sure others will have done the same. >> You know, one of the dynamics I want to get your reaction to is kind of two perspectives, one is, the growth of more teams that are involved in the work, so whether it's from cyber to monitoring, there's more teams with tools out there that are working on the network. And then you have just the impact of the diversity of use cases, not so much data volume, 'cause that's been talked about, lot of, we're having a tsunami of data, that's clear. But different kinds of dynamics, whether it's real-time, bursting, and so when you have this kind of environment, you can have gaps. And solar winds have taught us anything, it's that you have to identify problems and resolve them, this comes up a lot in observability conversations, MTTI, mean time to identify, and then to resolve. These are concepts. If you don't see the data, you can't understand what's going on if you can't measure it. This is like huge. >> Yes, absolutely right, absolutely right. So what we really need now is, as you mentioned, we need an integrated tool set, right? What we mean by that, is the tools must be able to work together, the data must be able to be used across the board. So like by use case it should not be siloed or fragmented, that they should work as one system that users are able to learn, and then sort of be able to use effectively without context switching. Another concept that's quite important is, how flexible are you? Are you digging yourself into a fixed solution, or are you depending on open standards that will then let you change out implementations, or vendors, or what have you, (static crackles) down the line, relatively easily. So understanding how you're collecting the data, how good can open standards and open source you're using is important. But to your point about missing and gaps, I think full fidelity, like understanding every single transaction, if you can pull it off, is a fascinating superpower, because that's where you don't get the gaps, and if you are able to go back and track any bad transaction, any time, that is hugely liberating, right? Because without that, if you're going to do a lot of sampling, you're going to miss a huge percentage of the user interactions, that's probably a recipe for some kind of trouble down the line, as you mentioned. And actually, these are some of those principles that we are using to build the Splunk Observability Suite, is no sample or full fidelity is a core foundational principle, and for us, it's not just isolated to, let's say application performance management, where user gets your API and you're able to track what happened, we are actually taking this upstream, up to the user, so the user is taking actions on the browser, how do we capture and correlate what's happening on the browser, because (indistinct) as you know, there's a huge move towards single-page applications, where half of my logic that my users are using is actually running on the browser, right? And so understanding the whole thing end to end, without any gaps, without any sampling, is extremely powerful. And so yes, so those are some of the things that we're investing in, and I think, again, one should keep in mind, when they're considering observability. >> You know, we were talking the other day, and having a debate around technical debt, and how that applies to observability, and one of the things that you brought up earlier about tools, and tool sprawl, that causes problems, you have operational friction, and we've heard people say "Yeah, I've got too many tools," and just too much, to replatform or refactor, it's just too much pain in the butt for me to do that, so at some point they break, I take on too much technical debt. When is that point of no return, where someone feels the pain on tool sprawl? What are some of the signaling where it's like, "You better move now (indistinct) too late," 'cause this integrated platform, that's what seems to be the way people go, as you mentioned. But this tool sprawl is a big problem. >> It is, and I think it starts hitting you relatively early on, nowadays, if you ask my opinion. So, tool sprawl is I think, if you find yourself, I think using three or four different tools, which are all part of some critical workload together, that's a stink that there's something could be optimized. For example, let's say I'm observing whether my website works fine, and if my alerting tool is different from my data gathering, or whatever, the infrastructure monitoring metrics tool, which is different from my incident management tool, which is different from my logs tool, then if you put the hat on of an engineer, a poor engineer who's dealing with a crisis, the number of times they have to context switch and the amount of friction that adds to the process, the delay that it adds to the process is very very painful. So my thinking is that at some point, especially if we find that core critical workloads are being fragmented, and that's when sort of I'm adding a bunch of friction, it's probably not good for us to sort of make that sort of keep on going for a while, and it would be time to address that problem. And frankly, having these tools integrated, it actually brings a lot of benefit, which is far bigger than the sum of the parts, because think about it, if I'm looking at, say, an incident, and if I'm able to get a cross-tool data, all presented in one screen, one UI, that is hugely powerful because it gives me all the information that I need without having to, again, dig into five different tools, and allows me to make quicker, faster decisions. So I think this is almost an inevitable wave that everybody must and will adopt, and the question is, I think it's important to get on the good program early, because unless you sort of build a lot of practices within an organization, that becomes very very hard to change later, it is just going to be more costly down the line. >> So from an (indistinct) standpoint, under the hood, integrated platform, takes that tool sprawl problem away, helps there. You had open source technology so there's no lock-in, you mentioned full fidelity, not just sampling, full end to end tracing, which is critical, wants to avoid those gaps. And then the other are I want to get your thoughts on, that you didn't bring up yet, that people are talking about is, real time streaming of analytics. What role does that play, is that part of the architecture, what function does that do? >> Right, so to me, it's a question of, how quickly do I find a problem? If you think about it, we are moving to more and more software services, right? So everybody's a software service now, and we all talk to each other in different services. Now, any time you use a dependency, you want to know how available it is, what are my SLAs and SLOs and so on, and three nines is almost a given, that you must provide three nines or better. Ideally four nines of availability, because your overall system stability is going to be less than the one of any single part, and if you go to look at four nines, you have about four or five minutes of total downtime in one whole month. That's a hard thing to be able to control. And if your alerting is going to be in order of five or 10 minutes, there's no chance you're going to be able to promise the kind of high availability that you need to be able to do, and so the fundamental question is you need to understand problems quick, like fast, within seconds, ideally. Now streaming is one way to do it, but that really is the problem definition, how do I find the problems early enough so that I can give my automation or my engineers time to figure out what happened and take corrective action? Because if I can't even know that there's something amiss, then there's no chance I'm going to be able to sort of provide that availability that my solution needs. So in that context, real time is very important, it is much more important now, because we have all these software and service dependencies, than it maybe used to be in the past. And so that's kind of why, again, at Splunk, we invested in real time streaming analytics, with the idea again being, let the problem, how can we address this, how can we provide customers with quick, high level important alerts in seconds, and that sort of real time streaming is probably the best way to achieve that. And then, if I were to, sorry, go ahead. >> No, go on, finish. >> Yeah, I was going to say that it's one thing to get an alert, but the question then is, now what do I do with it? And there's obviously a lot of alert noise that's going out, and people are fatigued, and I have all these alerts, I have this complex environment, understanding what to do, which is sort of reducing the MTTR part of it, is also important, I think environments are so complex now, that without a little bit of help from the tool, you are not going to be able to be very effective, it's going to take you longer, and this is also another reason why integrated tools are better, because they can provide you hints, looking at all the data, not just one type, not just necessarily logs, or not just necessarily traces, but they have access to the whole data set, and they can give you far better hints, and that's again one of the foundational principles, because this is in the emergent field of AIOps, where the idea is that we want to bring the power of data science, the power of machine learning, and to aid the operator in figuring out where a problem might be, so that they can at least take corrective action faster, not necessarily fix it, but at least bypass the problem, or take some kind of corrective action, and that's a theme that sort of goes across our suite of tools is, the question we ask ourselves is, "In every situation, what information could I have provided them, what kind of hints could we have provided them, to short circuit their resolution process?" >> It's funny you mention suite of tools, you have an Observability Suite, which Splunk leads with, as part of the series, it's funny, suite of tools, it's kind of like, you kind of don't want to say it, but it is kind of what's being discussed, it's kind of a platform and tool working together, and I think the trend seems to be, it used to be in the old days, you were a platform player or a tool player, really kind of couldn't do both, but now with cloud-native, as it's distributed computing, with all this importance around observability, you got to start thinking, suite has platform features, could you react to that, and how would you talk about that, because what does it mean to be a platform? Platforms have benefits, tools have benefits, working together implies it's a combination, could you share your thoughts on that reaction to that? >> That's a very interesting question you asked, John, so this is actually, if you asked me how I look at the solution set that we have, I will explain it thus. We are a platform, we are a set of products and tools, and we are an enterprise solution. And let me explain what I mean by that, because I think all of these matter, to somebody or the other. As a platform, you're like "How good am I in dealing with data?" Like ingesting data, analyzing data, alerting you, so those are the core foundational features that everybody has, these are the database-centric aspects of it, right? And if you look at a lot of organizations who have mature practices, they are looking for a platform, maybe it scales better than what they have, or whatnot, and they're looking for a platform, they know what to do, build out on top of that, right? But at the same time, a platform is not a product, 99% of our users, they're not going to make database calls to fetch and query data, they want an end to end, like a thing that they can use to say, "Monitor my Kubernetes," "Monitor my Elasticsearch," "Monitor my," you know, whatever other solution I may have. So then we build a bunch of products that are built on top of the platform, which provide sort of the usability, so where, it's very easy to get on, send the data, have built-in content, dashboard (indistinct), what have you, so that my day to day work is fast, because I'm not a observability engineer, I'm a software engineer working on something, and I want to use observability, make it easy for me, right? So that's sort of the product aspect of it. But then if you look at organizations that a little bit scale up, just a product is also not good enough. Now we're looking at a observability solution that's deployed in an enterprise, and there are many many products, many many teams, many many users, and then how can one be effective there? And if you look at what's important at that level, it's not the database aspect or the platform aspect, it's about how well can I manage it, do I have visibility into what I am sending, what my bill is, can I control against incorrect usage, do I have permissions to sort of control who can mess with my (indistinct) and so on, and so there's a bunch of layer of what we call enterprise capabilities that are important in an organizational setting. So I think in order to build something that's successful in this space, we have to think at all these three levels, right? And all of these are important, because in the end, it's how much value am I getting out of it, it's not just what's theoretically possible, what's really happening, and all of these are important in that context. >> And I think, Arijit, that's amazing masterclass right there, soundbite right there, and I think it's because the data also is important, if you're going to be busting down data silos, you need to have a horizontally scalable data observability space. You have to have access to the data, so I think the trend will be more integrated, clearly, and more versatile from a platform perspective, it has to be. >> Absolutely, absolutely. >> Well, we're certainly going to bring you back on our conversations when we have our events and/or our groups around digital transformation Under the Hood series that we're going to do, but great voice, great commentary, Arijit, thank you for sharing that knowledge with us, appreciate it. >> My pleasure, thank you very much. >> Okay, I'm John Furrier with theCUBE, here, Leading with Observability content series with Splunk, I'm John Furrier with theCUBE, thanks for watching. (calm music)

>> Narrator: From theCUBE studios in Palo Alto in Boston connecting with that leaders all around the world, this is a CUBE Conversation. >> Hello and welcome to this special CUBE Conversation. I'm John Furrier, your host. We're here for a special series, Leading with Observability, and this segment is: End-to-end observability drives great digital experiences. We've got a great guest here, Craig Hyde, senior director of product management for Splunk. Craig, great to see you. Thanks for coming on. >> And thanks for having me. This is great. >> So this series, Leading with Observability is a super hot topic obviously with cloud native. In the pandemic, COVID-19 has really kind of shown cloud native trend has been a tailwind for people who invested in it, who have been architecting for cloud on premises where data is a key part of that value proposition and then there's people who haven't been doing it. So, and out of this trend, the word observability has become a hot segment. And for us insiders in the industry, we know observability is just kind of network management on steroids in the cloud, so it's about data and all this. But at the end of the day, there's value that's enabled from observability. So I want to talk to you about that value that's enabled in the experience of the end user whether it's in a modern application or user inside the enterprise. Tell us what you think about this end user perspective. >> Sure, yeah thanks a lot for that intro. And I would actually argue that observability wouldn't even just be machine data or network data, it's more of a broader context where you can see everything that's going on inside the application and the digital user experience. From a user experience or a digital experience management perspective, I believe the metrics that you pull from such a thing are the most useful and ubiquitous metrics that you have and visibility in all of technology. And when done right, it can tell you what the actual end result of all this technology that you're piecing together, the end result of what's getting delivered to the user, both quantitatively and qualitatively. So, my background, I actually started a company in this domain. It was called Rigor and we focused purely on looking at user experience and digital experience. And the idea was that, you know, this was 10 years ago, we were just thinking, look, 10 years from now, more and more people are going to do business digitally, they're going to work more digitally and at the same time we saw the legacy data centers being shut down and things were moving to the cloud. So we said, look, the future is in the users, and where it all comes together is on the user's desktop or on their phone, and so we set out to focus specifically on that space. Fast forward 10 years, we're now a part of Splunk and we're really excited to bolt this onto an overall observability strategy. You know, I believe that it's becoming more and more popular, like you said, with the pandemic and COVID-19, it was already on a tear from a digital perspective, the adoption was going through the roof and people were doing more and more remote, they were buying more and more offline, but the pandemic has just pushed it through the roof. And I mean, wow, like the digital business genie's out of the bottle and there's no putting it back now. But, you know, there's also other things that are driving the need for this and the importance of it and part of it comes with the way technology is growing. It's becoming much more complex in terms of moving parts. Where an app used to be run off three different tiers in a data center, now it could be across hundreds of machines and opaque networks, opaque data centers all over the world, and the only time you often see things, how they come together, is on the user's desktop. And so that's where we really think you got to start from the user experience and work back. And, you know, all the drive in computing is all about making things better, faster and cheaper, but without this context of the user, often the customer and the experience gets left out from reaping the rewards from all these gains. So that's sort of like encapsulates my overall view of the space and why we got into it and why I'm so excited about it. >> Well Craig, I got to ask on a personal level. I mean, you look at what happened with the pandemic, I mean, you're a pioneer, you had a vision. Folks that are on the entrepreneurial side say, hey digital businesses is coming and they get it and it's slowly gets known in the real world, becomes more certain, but with the pandemic, it just happened all of a sudden so fast for everybody because everyone's impacted. Teachers, students, families, work, everyone's at home. So the entire user experience was impacted in the entire world. What was going through your mind when you saw all this happening and you see the winners obviously were people had invested in cloud native and data-driven technologies, what was your take on all this when you saw this coming? >> Well, the overall trend has been going on for decades, right? And so the direction of it isn't that surprising, but the magnitude and the acceleration, there's some stats out there from Forbes where the e-commerce adoption doubled within the first six months of the pandemic. So we're talking, you know, 10, 12 years of things ticking up and then within six months, a doubling of the adoption of e-commerce. And so like anybody else, you first freeze and say, what does this mean? But when people start working remote and people start ordering things from Amazon and all the other websites, it's quick to see like, aha! It no longer matters what chairs somebody is sitting in when they're doing work or that they're close to a store and you have a physical storefront when you're trying to buy something, it's all about that digital experience and it needs to be ubiquitous. So it's been interesting to see the change over the past few months for sure. But again, it doesn't change the trend, it just magnified it and I don't see it going back anytime soon. >> Yeah I mean, digital transformation has always been a buzz word that everyone kind of uses as a way to kind of talk about the big picture. >> Right. >> It's actually transforming and there's also share shifts that happen in every transformation, in any market shift. Obviously that's happening with cloud. Cloud native edge is becoming super important. In all of these, and by the way, in all the applications that sit on that infrastructure which is now infrastructure as code, has a data requirement that observability piece becomes super critical, not just from identifying and resolving, but also for training machine learning and AI, right? So, again, you have this new flywheel observability that's really at the heart of digital transformation. What should companies think about when they associate observability to digital transformation as they're sitting around whether they're CXOs or CSOs or solution architects going, okay, how does observability plug into my plans? >> Yeah, absolutely. I mean, my recommendation and the approach that I would take is that you want to start with the end in mind and it's all about how you set your goals when you're setting out in getting into digital transformation. And, you know, the late Steve Jobs, to borrow one of his quotes, he said that you have to start with the customer experience in mind and work backwards to the technology. And so I think that applies when you get into an observability strategy. So without understanding what the actual user experience is, you don't have a good enough yardstick to go out there and start working towards. So availability on a server or CPU time or transaction time in a database, like, those are all great, but without the context of what is the goal you're actually going after, it's kind of useless. So, like I said, it's not uptime, it's not server time, it's not any of that stuff, and it's user experience and these things are different. So they're like visual metrics, right? So what a user sees, because all kinds of things are going on in the background, but if it can see that the person can see and their experience is that they're getting some kind of response from the machine, then that's how you measure where the end point is and what the overall goal is. And so like to keep kind of going on with that, it's like you start with the end in mind, you use that end to set your goals, you use that domain and that visibility to troubleshoot faster. So when the calls start rolling in then they say, hey, I'm stuck at home and I'm on a slow internet connection, I can't get on the app and core IT is taking a phone call, You can quickly look and instrument that user and see exactly what they're seeing. So when you're troubleshooting, you're looking at the data from their perspective and then working backwards to the technology. >> That's super exciting. I want to get your thoughts on that. So just to double down on that because I think this highlights the trend that we were just talking about. But I'll break it down into three areas that I see happening in the marketplace. Number one, availability and performance. That's on everyone's mind. You just hit that, right? Number two, integrations. There's more integrations going on within platforms or tools or systems, whether it's an API over here, people are working together digitally, right? And you're seeing e-commerce. And third is the user patterns and the expectations are changing. So when you unpack those kinds of like trends, there's features of observability underneath each. Could you talk about that because I think that seems to be the common pattern that I'm seeing? Okay, high availability, okay, check. Everyone has to have that. Almost table stakes. But it's hard when you're scaling, right? And then integrations, all kinds of API is being slinged around. You've got microservices, you've got Kubernetes, people are integrating data flows, control planes, whatever, and then finally users. They want new things. New patterns emerge, which is new data. >> Yeah, absolutely. And to just kind of talk about that, it reminds me of like a Maslow's hierarchy of needs of visibility, right? Like, okay, the machine is on, check. Like you said, it's table stakes, make sure it's up and running. That's great. Then you want to see sort of the applications that are running on the machine, how they're talking to each other, are other components that you're making API calls to, are they timing out or are they breaking things? And so you get that visibility of like, okay, they're on, what's going on top of those machines are inside of them or in the containers or the virtual machines or whatever segment of computing that you're looking at, And then that cherry on top, the highest point is like, how is that stack of technology serving your customer? How's it serving the user and what's the experience? So those are sort of the three levels that we kind of look at when we're thinking of user experience. And so, it's a different way to look at it, but it's sort of the way that kind of we see the world is that three tier, that three layer cake. >> It's interesting. >> And you need all the layers. >> It's super relevant. And again, it's better together, but you can mix and match and have product in there. So I want to get into the Splunk solution. You guys have the digital experience monitoring solution. Can you explain what that is and how that fits into all this and what's in it for the customers, what's the benefit? >> Right, sure. So with the digital experience monitoring and the platform that we have, we're giving people the ability to basically do what I was talking about, where it enables you to take a look at what the user's experience are and pull metrics and then correlate them from the user all the way through the technical journey to the back end, through the different tiers of the application and so on. So that technology is called real user monitoring where we instrument the users. And then we also layer in synthetic monitoring which is the sort of robot users that are always on for when you're in lower level environments and you want to see, you know, what experience is going to look like when you push out new software, or when nobody's on the application, did something break? So a couple of those two together and then we feed that into our overall observability platform that's fed with machine data, we have all the metrics from all the components that you're looking at in that single pane of glass. And the idea is that we're also bringing you not only just the metrics and the events from logs and all the happenings, but we're also trying to help tease out some of these problems for you. So many problems that happen in technology have happened before, and we've got a catalog with our optimization platform of 300 plus things that go wrong when webpages or web applications or API calls start acting funky. And so we can provide, based on our intelligence that's built into the platform, basically run books for people to fix things faster and build those playbooks into the release process so you don't break the applications to begin with and you can set flags to where people understand what performance is before when it's being delivered to the customer, and if there are problems, let's fix them before we break the experience and lose the trust of the user. So again, it's the metrics from the stats that are coming across the wire of everything all the way to the users, it's the events from the logs that are coming in so you can see context, and then it's that user experience, it's a trace level data from where you can double click into each of the tiers and say, like, what's going on in here? What's going on in the browser? What's going on in the application? What's going on in the backend? And so you can sort of pool all that together in a single pane of glass and find problems faster, fix them faster and prevent users from having problems to begin with. And to do this properly, you really need it all under one roof and so that's why we're so excited to bring this all together. >> Yeah, I've been sitting on theCUBE for 10 years now. We've been 11 years, on our 11th year doing theCUBE. Digital you can measure everything. So why not? There should be no debate if done properly. So that brings up this whole concept that you guys are talking about full fidelity. Can you just take a minute to explain what that is? What is full fidelity mean? >> Sure, you know, full fidelity really comes down to a lot about these traces. So when we talk about metrics, logs and traces, it's all about getting all the activity that goes on in an application and looking at it. So when you or I interact with our company's app online and there's problems, that the person who's going to fix this problem, they can actually see specifically me. They can look at my experience and look at what it would look like in my browser, you know, what were all the services that I was interacting with and what was going on in the application, what code was being called, what services were being called, and look at specifically me as opposed to an aggregate of all the domains all put together. And it really is important from a troubleshooting standpoint. It's really important from an understanding of the actuals because without full fidelity and capturing all of the data, you're kind of going, you know, you're taking guesses and it eliminates a lot of the guesswork. And so that's something that's special with our platform is that ability to have the full fidelity. >> When does a client, a customer not have full fidelity? I might think I have it, someone sold me a product, What's the tell sign that I don't have full fidelity? >> Oh yeah, well with observability, there's a lot of tricks in the game. And so you see a lot of summary data that looks like, hey, this is that one call, but usually it's knitted together from a bunch of different calls. So that summary data just from, because this stuff takes up a lot of storage and there's a lot of problems with scale, and so when you might see something that looks like it's this call, it's actually like, in general, when a call like this happens, this is what it looks like. And so you've got to say like, is this the exact call? And, you know, it makes a big difference from a troubleshooting perspective and it's really hard to implement and that's something that Splunk's very good at, right? It's data at scale. It's the 800 pound gorilla in collecting and slicing apart machine data. So like, you have to have something of that scale in order to ingest all this information. It's a hard problem for sure. >> Yeah, totally. And I appreciate that. While I got you here, you're an expert, I got to ask you about Open Telemetry. We've heard that term kicked around. What does that mean? Is it an open source thing, is it an open framework? What is Open Telemetry and what does it mean for your customers or the marketplace? >> Yeah, I think of Open Telemetry as finally creating a standard for how we're collecting data from applications across AP- In the past, it's been onesie-twosie, here and there each company coming up with it themselves and there are never any standards of how to look at transactions across data, across applications and across tiers. And so Open Telemetry is the attempt and it's a consortium, so there's many people involved in pushing this together, but think of like a W3C, which creates the standards for how websites operate, and without it, the web wouldn't be what it is today. And now Open Telemetry is coming behind and doing that same thing from an observability standpoint. So you're not just totally locked into one vendor in the way that they do it and you're held hostage to only looking at that visibility. We're trying to set the standards to lower the barrier of entry into getting to application performance monitoring, network performance monitoring and just getting that telemetry where there are standards across the board. And so it's an open source project. We commit to it, and it's a really important project for observability in general. >> So does that speak to like, the whole more data you have, the less blind spots you might have? Is that the same concept? Is that some of the thinking behind this? >> It enables you to get more data faster. Now, if you think about, if there are no standards and there are no rules on the road and everybody can get on the road and they can decide if they want to drive in the left lane or the right lane today, it makes getting places a lot harder. And the same is true with Open Telemetry. without the standards of what, you know, the naming conventions, where you instrument, how you instrument, it becomes very hard to put some things in a single pane of glass because they just look differently everywhere. And so that's the idea behind it. >> Well Craig, great to have you on. You're super smart on this, and Leading with Observability, it's a hot topic. It's super cool and relevant right now with digital transformation as companies are looking to rearchitect and change how they're going to flip the script on software development, modern applications, modern infrastructure, edge, all of this is on top of mind of everyone's thing on their plans. And we certainly want to have you back in some of our conversations that we have around this on our editorial side as well with when we have these clubhouses we are going to start doing a lot of those. We definitely want to bring you in. I'll give you a final word here. Tell us what you're most excited about. Put the commercial for Splunk. Why Splunk? Why you guys are excited. Take a minute to get the plug in. >> It's so easy. Splunk has the base to make this possible. Splunk is, like I said, it's an 800 pound gorilla in machine data and taking in data at scale. And when you start going off into the observability abyss, the really, really hard part about it is having the scale to not only go broad in the levels of technology that you can collect, but also go deep. And that depth, when we talked about that full fidelity, it's really important when you get down to brass tacks and you start implementing changes and troubleshooting things and turning that data that you have in to doing, so understanding what you can do with it. And Splunk is fully committed to going, not only broad to get everything under one roof, but also deep so that you can make all of the information that you collect actionable and useful. And it's something that I haven't seen anybody even attempt and I'm really excited to be a part of building towards that vision. >> Well, I've been covering Splunk for, man, many, many years. 10 years plus, I think, since it's been founded, and really the growth and the vision and the mission still is the same. Leveraging data, making use of it, unlocking the power of data as it evolves and there's more of it. And it gets more complicated when data is involved in the user experience end-to-end from cybersecurity to user flows and new expectations. So congratulations. Great product. Thanks for coming on and sharing. >> Thanks again for having us. >> Okay, this is John Furrier in theCUBE. Leading with Observability is the theme of this series and this topic was End-to-end observability to enable great digital experiences. Thanks for watching. (lighthearted music)

(upbeat music) >> Announcer: From the keeps studios in Palo Alto in Boston, connecting with that leaders all around the world. This is theCube conversation. >> Welcome to theCube conversation here in Palo Alto, California. I'm John Furrier, host of theCube. With a special content series called, Leading with observability, and this topic is, Keeping watch over microservices and containers. With great guests, Patrick Lin, VP of Product Management for the observability product at Splunk. Patrick, great to see you. Thanks for coming on remotely. We're still in the pandemic, but thanks for coming on. >> Yeah, John, great to see you as well. Thanks for having me. >> So, leading with observability is a big theme of our content series. Managing end to end and user experience is a great topic around how data can be used for user experience. But now underneath that layer, you have this whole craziness of the rise of the container generation, where containers are actually going mainstream. And Gardner will forecast anywhere from 30 to 40 percent of enterprises still yet, haven't really adopted at full scale and you've got to keep watch over these. So, what is the topic about keeping watch over microservice and containers, because, yeah, we know they're being deployed. Is it just watching them for watching sake or is there a specific reason? What's the theme here? Why this topic? >> Yeah, well, I think containers are part of the entire kind of stack of technology that's being deployed in order to develop and ship software more quickly. And, the fundamental reasons for that haven't changed but they've been greatly accelerated by the impact of the pandemic. And so I think for the past few years we've been talking about how software's eating the world, how it's become more and more important that company go through the transformation to be more digital. And I think now that is so patently obvious to everybody. When your only way of accessing your customer and for the customer to access your services is through a digital media. The ability for your IT and DevOps teams to be able to deliver against those requirements, to deliver that flawless customer experience, to sort of keep pace with it the digital transformation and the cloud initiatives. All of that is kind of coming as one big wave. And so, we see a lot of organizations migrating workloads to the cloud, refactoring applications, building new applications natively. And so, when they do that oftentimes the infrastructure of choice is containers. Because it's the thing that keeps up with the pace of the development. It's a much more efficient use of underlying resources. So it's all kind of part of the overall movement that we see. >> What is the main driver for this use case microservices and where's the progress bar in your mind of the adoption and deployment of microservices, and what is the critical things that are there you guys are looking at that are important to monitor and observe and keep track of? Is it the status of the microservices? Is it the fact that they're being turned on and off, the state, non-state, I mean take us through some of the main drivers for why you guys are keeping an eye on the microservices component? >> Sure, well, I think that if we take a step back the reason that people have moved towards microservices and containers fundamentally has to do with the desire to be able to, number one, develop and ship more quickly. And so if you can parallelize the development have API is the interface between these services rather than having sort of one monolithic code base, you can evolve more quickly. And on top of that, the goal is to be able to deliver software that is able to scale as needed. And so, that is a part of the equation as well. So when you sort of look at at this the desire to be able to iterate on your software and services more quickly, to be able to scale infinitely, staying up and so on. That's all like a great reason to do it, but what happens along those lines, what comes with it is a few kind of additional layers of complexity because now rather than have, let's say an end to your app that you're watching over on some hosts that you could reboot when there's a problem. Now you have 10's, maybe 100's of services running on top of maybe 100,000's, maybe 10,000's of containers. And so the complexity of that environment has grown quite quickly. And the fact that those containers may go away as you are scale the service up and down to meet demand also adds to that complexity. And so from an observability perspective, what you need to be able to do is a few things. One is you need to actually be tracking this in enough detail and at a high enough resolution in realtime. So that you know when things are coming in and out. And that's been one of the more critical things that we've built towards a Splunk, is that ability to watch over it in realtime. But more important, or just as important in that is, understanding the dependencies and the relationships between these different services. And so, that's one of the main things that we worked on here is to make sure that you can understand the dependency so that when there's an issue you have a shot at actually figuring out where the problem is coming from. Because of the fact that there's so many different services and so many things that could be affecting the overall user experience when something goes wrong. >> I think that's one of the most exciting areas right now, on observability is this whole microservices container equation, because a lot of actions being done there, there's a lot of complexity but the upside, if you do it right, it's significant. I think people generally are bought into that concept, Patrick, but I want to get your thoughts. I get this question a lot from executives and leaders whether it's a cloud architect or a CXO. And the question is, what should I consider? What do I need to consider when deploying an observability solution? >> Yeah, that's a great question. Cause I think they're obviously a lot of considerations here. So, I think one of the main ones, and this is something that I think is a pattern that we are pretty familiar with in the this sort of monitoring and management tool world. Is that, over time most enterprises have gotten themselves a very large number of tools. One for each part of their infrastructure or their application stack and so on. And so, what you end up with is sprawl in the monitoring toolset that you have. Which creates not just sort of a certain amount of overhead in terms of the cost, but also complexity that gets in the way of actually figuring out where the problem is. I've been looking at some of the toolsets that some of our customers have pulled together and they have the ability to get information about everything but it's not kind of woven together in a useful way. And it sort of gets in the way actually, having so many tools when you are actually in the heat of the moment trying to figure something out. It sort of hearkens back to the time when you have an outage, you have a con call with like a cast of 1000's on it trying to figure out what's going on. And each person comes to that with their own tool, with their own view, without anything that ties that to what the others are seeing. And so, that need to be able to provide sort of an integrated toolset, with a consistent interface across infrastructure, across the application, across what the user experience is and across the different data types. The metrics, the traces, the logs. Fundamentally I think that ability to kind of easily correlate the data across it and get to the right insight. We think that's a super important thing. >> Yeah, and I think what that points out, I mean, I always say, don't be a fool with a tool. And if you have too many tools, you have a tool shed, and there are too many tools everywhere. And that's kind of a trend, and tools are great when you need tools. To do things. But when you have too many, when you have a data model where essentially what you're saying is, a platform is the trend, because weaving stuff together you need to have a data control plane, you need to have data visualization. You need to have these things for understanding the success there. So, really it's a platform, but platforms also have tools as well. So tools or features of a platform if I get what you're saying, right? Is that correct? Yeah, so I think that there's one part of this which is, you need to be able to, if I start from the user point of view, what you want is a consistent and coherent set of workflows for the people who are trying to actually do the work. You don't want them to have to deal with the impedance mismatches across different tools that exist based on, whatever, even the language that they use but how they bring the data in and how it's being processed. You go down one layer from that. You sort of want to make sure that what they're working with is actually consistent as well. And that's the sort of capabilities that you're looking at whether you're whatever, trying to chart something to be able to look at the details, or go from a view of logs to the related traces. You sort of want to make sure that the information that's being served up there is consistent. And that in turn relies on data coming in, in a way that is sort of processed to be correlated well. So that if you say, Hey, I'm I'm looking at a particular service. I want to understand what infrastructure is sitting on or I'm looking at a log and I see that it relates to a particular service. And I want to look at traces for that service. Those things need to be kind of related from the data on in and that needs to be exposed to the user so that they can navigate it properly and make use of it. Whether that's during kind of, or time during an incident or peace time. >> Yeah, I love that wartime conciliary versus peace time. I saw blog posts from a VC, I think said, don't be a Tom Hagen, which is the guy in The Godfather when the famous lines said, you're not a wartime conciliary. Which means things are uncertain in these times and you've got to get them to be certain. This is a mindset, this is part of the pandemic we're living in. Great point, I love that. Maybe we could follow up on that at the end, but I want to get some of these topics. I want to get your reactions to. So, I want you to react to the following, Patrick. it's an issue in a topic, and there it is, missing data results in limited analytics and misguided troubleshooting. What's your reaction to that? What's your take on that? What's the Splunk's take on that? >> Yeah, I mean, I think Splunk has sort of been a proponent of that view for a very long time. I think that whether that's from the log data or from, let's say, the metric data that we capture at high resolution or from tracing. The goal here is to have the data that you need in order to actually properly diagnose what's going on. And I think that older approaches, especially on the application side, tend to sample data right at the source and provide hopefully useful samples of it for when you have that problem. That doesn't work very well in the microservice world because you need to actually be able to see the entirety of a transaction, to a full trace across many services before you could possibly make a decision as to what's useful to keep. And so, the approach that I think we believe is the right one, is to be able to capture at full fidelity all of those bits of information, partly because of what I just said, you want to be able to find the right sample, but also because it's important to be able to tie it to something that may be being pulled in by different system. So, an example of that might be, in a case where you are trying to do real user monitoring alongside of APM, and you want to see the end to end trace from what the user sees all the way through to all the backend services. And so, what's typical in this world today is that, that information is being captured by two different systems independent sampling decisions. And therefore the ability to draw a straight line from what the end user sees all the way to what is effecting it on the backend is pretty hard. Where it gets really expensive. And I think the approach that we've taken is to make it so that that's easy and cost-effective. And it's tremendously helpful then to tie it back to kind of what we were talking about at the outset here where you were trying to provide services that make sense and are easy access and so on to your end user. to be able to have that end to end view because you're not missing data. It's tremendously valuable. >> You know what I love about Splunk is, cause I'm a data geek going back when it wasn't fashionable back in the 80's. And Splunk has always been about ingesting all the data. So they bring all the data, we'll take it all. Now from at the beginning it was pretty straightforward, complex but still it had a great utility. But even now, today, it's the same thing you just mentioned, ingest all the data because there's now benefits. And I want to just ask you a quick question on this, distributed computing trend, because I mean everyone's pretty much in agreement that's in computer science or in the industry and in technology says, okay, cloud is a distributed computing with the edge. It's essentially distributed computing in a new way, new architecture with new great benefits, new things, but science is still kicking apply some science there. You mentioned distributed tracing because at the end of the day that's also a new major thing that you guys are focused on and it's not so much about, it's also good get me all the data but distributed tracing is a lot harder than understanding that because of the environment and it's changing so fast. What's your take on it? >> Yeah, well fundamentally I think this goes back to, ironically one of the principles in observability. Which is that oftentimes you need participation from the developers in sort of making sure that you have the right visibility. And it has to do with the fact that there are many services that are being kind of strong together as it were to be able to deliver on some end user transaction or some experience. And so, the fact that you have many services that are part of this, means that you need to make sure that each of those components is actually kind of providing some view into what it's doing. And distribute tracing is about taking that and kind of weaving it together so that you get that coherent view of the business workflow within the overall kind of web of services that make up your application. >> So the next topic, I want to get into, we've got limited time, but I'm going to squeeze through, but I'm going to read it to you real quick. Slow alerts and insights are difficult to scale. If they're difficult to scale it holds back the meantime between resolving. And so, it's difficult to detect in cloud. It was easier maybe on premise, but with cloud this is another complexity thing. How are you seeing the inability to scale quickly across the environments for to manage the performance issues and delays that are coming out of not having that kind of in slow insights or managing that? What's your reaction to that? >> Yeah, well, I think there are a lot of tools out there that we'll take in events or where issues from cloud environments. But they're not designed from the very beginning to be able to handle the sort of scale of what you're looking at. So, I mentioned, it's not uncommon for a company to have 10's or maybe even 100's of services and 1000's of containers or hosts. And so, the sort of sheer amount of data you have to be looking at on an ongoing basis. And the fact that things can change very quickly. Containers can pop in and go away within seconds. And so, the ability to track that in realtime implies that you need to have an architectural approach that is built for that from the very beginning. It's hard to retrofit a system to be able to handle orders to magnitude more complexity and change in pace of change. You need to start from the very beginning. And the belief we have is that you need some form of a realtime streaming architecture. Something that's capable of providing that realtime detection and alerting across a very wide range of things in order to handle the scale and the ephemeral nature of cloud environments. >> Let me ask a question then, because I heard some people say, well, it doesn't matter. 10, 15 minutes to log in to an event is good enough. What would you react to that? (chuckles) What a great example of where it's not good enough? I mean, is it minutes is it's seconds, what are we talking about here? What's the good enough bar right now? >> Yeah, I mean, I think any anybody who has tried to deliver an experience digitally to an end user, if you think you can wait minutes to solve a problem you clearly haven't been paying enough attention. And I think that, I think it almost goes without saying, that the faster you know that you have a problem, the better off you are. And so, when you think about what are the objectives that you have for your service levels or your performance or availability. I think you run out of minutes pretty quickly, if you get to anything like say, three nines So, waiting 15 minutes, maybe would have been acceptable before people were really trying to use your service at scale. But definitely not any more. >> And the latest app requires it. It's super important. I brought that up and tongue in cheek kind of tee that up for you because these streaming analytics, streaming engines are super valuable, and knowing when to use realtime and not also matters. This is where the platforms come in. >> Yes, absolutely. The platform is the thing that enables that. And I think you have to sort of build it from the very beginning with that streaming approach with the ability to do analytics against the streams coming in, in order for you to deliver on this sort of promise of alerts and insights at scale and in realtime. >> All right, final point. I'll give you the last word here. Give a plug for the Splunk observability suite. What is it? Why is it important? Why should people buy it? Why should people adopt it? Why should they upgrade to it? Give the perspective, give the plug. >> Yeah, sure. I appreciate the opportunity. So, I think as we've been out there speaking to customers right over the last year as part of Splunk and before that, I think they've spoken to us a lot about the need for better visibility into their environments. Which are increasingly complex and where they're trying to deliver on the best possible user experience. And to sort of add to that, where they're trying to actually consolidate the tools. We spoke about the sprawl at the beginning. And so, with what we're putting together here with the Splunk observability suite. I'd say we have the industry's most comprehensive and powerful combination of solutions that will help both sort of IT and DevOps teams tackle these new challenges for monitoring and observability that other tools simply can't address. So you're able to eliminate the management complexity by having a single consistent user experience across the metrics and logs and traces, so that you can have seamless monitoring and troubleshooting and investigation. You can create a better user experiences by having that true end to end visibility, all the way from the front end to the backend services, so that you can actually see what kind of impact you're having on users and figure it out within seconds. I think we're also able to help increase developer productivity. As these high performance tools that help the DevOps teams get to a better quality code faster, because they can get immediate feedback on how their coachings are doing with each we would see each release and they're able to operate more efficiently. So, I think there's a very large number of benefits from this approach of providing a single unified toolset that relies on a source of data that's consistent across it but then has the sort of particular tools that different users need for what they care about. Whether you're the front end developer, needing to understand the user experience, whether you're backend service owner wanting to see how your service relates to others, whether you're owning the infrastructure, and needs to see, is it actually providing what the services are running on it need. >> Well, Patrick, great to see you. And I just want to say, congratulations has been following your work, going back in the industry specifically with SignalFx, you guys were really early and seeing the value of observability before it was a category. And so how has more often so relevant as you guys had saw it. So, congratulations and keep up the great work. We'll keep a competition's open. Thanks for coming on. >> Great, thanks so much, John. Great talking to you. >> All right, this is theCube, Leading with observability, it's a series, check it out. We have a multiple talk tracks. Check out the Splunk's a series, Leading with observability. I'm John Furrier with theCube. Thanks for watching. (upbeat music)

ladies and gentlemen this is your captain speaking we will soon be taking off on our way to altitude please keep your seatbelts fastened and remain in your seats we will be experiencing turbulence until we are above the clouds ladies and gentlemen we are now cruising at altitude sit back and enjoy the ride [Music] altitude is a community of thought leaders and pioneers cloud architects and enlightened network engineers who have individually and are now collectively leading their own IT teams and the industry on a path to lift cloud networking above the clouds empowering Enterprise IT to architect design and control their own cloud network regardless of the turbulent clouds beneath them it's time to gain altitude ladies and gentlemen Steve Mulaney president and CEO of aviatrix the leader of multi cloud networking [Music] [Applause] all right good morning everybody here in Santa Clara as well as to the what millions of people watching the livestream worldwide welcome to altitude 2020 all right so we've got a fantastic event today really excited about the speakers that we have today and the experts that we have and really excited to get started so one of the things I wanted to just share was this is not a one-time event it's not a one-time thing that we're gonna do sorry for the aviation analogy but you know sherry way aviatrix means female pilot so everything we do as an aviation theme this is a take-off for a movement this isn't an event this is a take-off of a movement a multi-cloud networking movement and community that we're inviting all of you to become part of and-and-and why we're doing that is we want to enable enterprises to rise above the clouds so to speak and build their network architecture regardless of which public cloud they're using whether it's one or more of these public clouds so the good news for today there's lots of good news but this is one good news is we don't have any powerpoint presentations no marketing speak we know that marketing people have their own language we're not using any of that in those sales pitches right so instead what are we doing we're going to have expert panels we've got Simone Rashard Gartner here we've got 10 different network architects cloud architects real practitioners they're going to share their best practices and there are real-world experiences on their journey to the multi cloud so before we start and everybody know what today is in the u.s. it's Super Tuesday I'm not gonna get political but Super Tuesday there was a bigger Super Tuesday that happened 18 months ago and maybe eight six employees know what I'm talking about 18 months ago on a Tuesday every enterprise said I'm gonna go to the cloud and so what that was was the Cambrian explosion for cloud for the price so Frank kibrit you know what a Cambrian explosion is he had to look it up on Google 500 million years ago what happened there was an explosion of life where it went from very simple single-cell organisms to very complex multi-celled organisms guess what happened 18 months ago on a Tuesday I don't really know why but every enterprise like I said all woke up that day and said now I'm really gonna go to cloud and that Cambrian explosion of cloud went meant that I'm moving from very simple single cloud single use case simple environment to a very complex multi cloud complex use case environment and what we're here today is we're gonna go and dress that and how do you handle those those those complexities and when you look at what's happening with customers right now this is a business transformation right people like to talk about transitions this is a transformation and it's actually not just the technology transformation it's a business transformation it started from the CEO and the boards of enterprise customers where they said I have an existential threat to the survival of my company if you look at every industry who they're worried about is not the other 30 year old enterprise what they're worried about is the three year old enterprise that's leveraging cloud that's leveraging AI and that's where they fear that they're going to actually get wiped out right and so because of this existential threat this is CEO lead this is board led this is not technology led it is mandated in the organization's we are going to digitally transform our enterprise because of this existential threat and the movement to cloud is going to enable us to go do that and so IT is now put back in charge if you think back just a few years ago in cloud it was led by DevOps it was led by the applications and it was like I said before their Cambrian explosion is very simple now with this Cambrian explosion and enterprises getting very serious and mission critical they care about visibility they care about control they care about compliance conformance everything governance IT is in charge and and and that's why we're here today to discuss that so what we're going to do today is much of things but we're gonna validate this journey with customers do they see the same thing we're gonna validate the requirements for multi-cloud because honestly I've never met an enterprise that is not going to be multi-cloud many are one cloud today but they all say I need to architect my network for multiple clouds because that's just what the network is there to support the applications and the applications will run and whatever cloud it runs best in and you have to be prepared for that the second thing is is is architecture again with the IT in charge you architecture matters whether it's your career whether it's how you build your house it doesn't matter horrible architecture your life is horrible forever good architecture your life is pretty good so we're gonna talk about architecture and how the most fundamental and critical part of that architecture and that basic infrastructure is the network if you don't get that right nothing works right way more important and compute way more important than storm dense storage network is the foundational element of your infrastructure then we're going to talk about day 2 operations what does that mean well day 1 is one day of your life that's who you wire things up they do and beyond I tell everyone in networking and IT it's every day of your life and if you don't get that right your life is bad forever and so things like operations visibility security things like that how do I get my operations team to be able to handle this in an automated way because it's not just about configuring it in the cloud it's actually about how do I operationalize it and that's a huge benefit that we bring as aviatrix and then the last thing we're going to talk and it's the last panel we have I always say you can't forget about the humans right so all this technology all these things that we're doing it's always enabled by the humans at the end of the day if the humans fight it it won't get deployed and we have a massive skills gap in cloud and we also have a massive skill shortage you have everyone in the world trying to hire cloud network architects right there's just not enough of them going around so at aviatrix as leaders knew we're gonna help address that issue and try to create more people we created a program and we call the ACE program again an aviation theme it stands for aviatrix certified engineer very similar to what Cisco did with CC IES where Cisco taught you about IP networking a little bit of Cisco we're doing the same thing we're gonna teach network architects about multi-cloud networking and architecture and yeah you'll get a little bit of aviatrix training in there but this is the missing element for people's careers and also within their organization so we're gonna we're gonna go talk about that so great great event great show when try to keep it moving I'd next want to introduce my my host he's the best in the business you guys have probably seen him multiple million times he's the co CEO and co-founder of Tube John Fourier okay awesome great great speech they're awesome I totally agree with everything you said about the explosion happening and I'm excited here at the heart of Silicon Valley to have this event it's a special digital event with the cube and aviatrix where we live streaming to millions of people as you said maybe not a million maybe not really take this program to the world this is a little special for me because multi-cloud is the hottest wave and cloud and cloud native networking is fast becoming the key engine of the innovation so we got an hour and a half of action-packed programming we have a customer panel two customer panels before that Gartner is going to come on talk about the industry we have a global system integrators we talk about how they're advising and building these networks and cloud native networking and then finally the Aces the aviatrix certified engineer is gonna talk more about their certifications and the expertise needed so let's jump right in and let's ask someone rashard to come on stage from Gartner we'll check it all up [Applause] [Music] okay so kicking things off certain started gartner the industry experts on cloud really kind of more to your background talk about your background before you got the gardener yeah before because gardener was a chief network architect of a fortune five companies with thousands of sites over the world and I've been doing everything and IT from a C programmer in the 90 to a security architect to a network engineer to finally becoming a network analyst so you rode the wave now you're covering at the marketplace with hybrid cloud and now moving quickly to multi cloud is really I was talking about cloud natives been discussed but the networking piece is super important how do you see that evolving well the way we see Enterprise adapt in cloud first thing you do about networking the initial phases they either go in a very ad hoc way is usually led by non non IT like a shadow whitey or application people or some kind of DevOps team and it's it just goes as it's completely unplanned decreed VP sees left and right with a different account and they create mesh to manage them and their direct connect or Express route to any of them so that's what that's a first approach and on the other side again it within our first approach you see what I call the lift and shift way we see like Enterprise IT trying to basically replicate what they have in a data center in the cloud so they spend a lot of time planning doing Direct Connect putting Cisco routers and f5 and Citrix and any checkpoint Palo Alto divides the data that are sent removing that to that cloud and I ask you the aha moments gonna come up a lot of our panels is where people realize that it's a multi cloud world I mean they either inherit clouds certainly they're using public cloud and on-premises is now more relevant than ever when's that aha moment that you're seeing where people go well I got to get my act together and get on this well the first but even before multi-cloud so these two approach the first one like the adduct way doesn't scale at some point idea has to save them because they don't think about the two they don't think about operations they have a bunch of VPC and multiple clouds the other way that if you do the left and shift wake they cannot take any advantages of the cloud they lose elasticity auto-scaling pay by the drink these feature of agility features so they both realize okay neither of these ways are good so I have to optimize that so I have to have a mix of what I call the cloud native services within each cloud so they start adapting like other AWS constructor is your construct or Google construct then that's I would I call the up optimal phase but even that they they realize after that they are very different all these approaches different the cloud are different identities is completely difficult to manage across clouds I mean for example AWS has accounts there's subscription and in adarand GCP their projects it's a real mess so they realize well I can't really like concentrate used the cloud the cloud product and every cloud that doesn't work so I have I'm doing multi cloud I like to abstract all of that I still wanna manage the cloud from an API to interview I don't necessarily want to bring my incumbent data center products but I have to do that in a more API driven cloud they're not they're not scaling piece and you were mentioning that's because there's too many different clouds yes that's the piece there so what are they doing whether they really building different development teams as its software what's the solution well this the solution is to start architecting the cloud that's the third phase I call that the multi cloud architect phase where they have to think about abstraction that works across cloud fact even across one cloud it might not scale as well if you start having like 10,000 security group in AWS that doesn't scale you have to manage that if you have multiple VPC it doesn't scale you need a third party identity provider so it barely scales within one cloud if you go multiple cloud it gets worse and worse see way in here what's your thoughts I thought we said this wasn't gonna be a sales pitch for aviatrix you just said exactly what we do so anyway I'm just a joke what do you see in terms of where people are in that multi cloud a lot of people you know everyone I talked to started in one cloud right but then they look and they say okay but I'm now gonna move to adjourn I'm gonna move do you see a similar thing well yes they are moving but they're not there's not a lot of application that use a tree cloud at once they move one app in deserve one app in individuals one get happened Google that's what we see so far okay yeah I mean one of the mistakes that people think is they think multi-cloud no one is ever gonna go multi-cloud for arbitrage they're not gonna go and say well today I might go into Azure because I got a better rate of my instance that's never do you agree with that's never going to happen what I've seen with enterprise is I'm gonna put the workload in the app the app decides where it runs best that may be a sure maybe Google and for different reasons and they're gonna stick there and they're not gonna move let me ask you infrastructure has to be able to support from a networking team be able to do that do you agree with that yes I agree and one thing is also very important is connecting to that cloud is kind of the easiest thing so though while I run Network part of the cloud connectivity to the cloud is kind of simple I agree IPSec VP and I reckon Express that's a simple part what's difficult and even a provisioning part is easy you can use terraform and create v pieces and v nets across which we cloud provider right what's difficult is the day-to-day operations so it's what to find a to operations what is that what does that actually mean this is the day-to-day operations after it you know the natural let's add an app let's add a server let's troubleshoot a problem so what so your life something changes how would he do so what's the big concerns I want to just get back to this cloud native networking because everyone kind of knows with cloud native apps are that's been a hot trend what is cloud native networking how do you how do you guys define that because that seems to be the oddest part of the multi-cloud wave that's coming as cloud native networking well there's no you know official garner definition but I can create one on another spot it's do it I just want to leverage the cloud construct and a cloud epi I don't want to have to install like like for example the first version was let's put a virtual router that doesn't even understand and then the cloud environment right if I have if I have to install a virtual machine it has to be cloud aware it has to understand the security group if it's a router it has to be programmable to the cloud API and and understand the cloud environment you know one things I hear a lot from either see Saussure CIOs or CXOs in general is this idea of I'm definitely on going API so it's been an API economy so API is key on that point but then they say okay I need to essentially have the right relationship with my suppliers aka clouds you call it above the clouds so the question is what do i do from an architecture standpoint do I just hire more developers and have different teams because you mentioned that's a scale point how do you solve this this problem of okay I got AWS I got GCP or Azure or whatever do I just have different teams or just expose api's where is that optimization where's the focus well I take what you need from an android point of view is a way a control plane across the three clouds and be able to use the api of the cloud to build networks but also to troubleshoot them and do they to operation so you need a view across a three cloud that takes care of routing connectivity that's you know that's the aviatrix plug of you right there so so how do you see so again your Gartner you you you you see the industry you've been a network architect how do you see this this plane out what are the what are the legacy incumbent client-server on-prem networking people gonna do well these versus people like aviatrix well how do you see that plane out well obviously all the incumbent like Arista cisco juniper NSX right they want to basically do the lift and ship or they want to bring and you know VM I want to bring in a section that cloud they call that NSX everywhere and cisco monks bring you star in the cloud recall that each guy anywhere right so everyone what and and then there's cloud vision for my red star and contrail is in the cloud so they just want to bring the management plain in the cloud but it's still based most of them it's still based on putting a VM them in controlling them right you you extend your management console to the cloud that's not truly cloud native right cloud native you almost have to build it from scratch we like to call that cloud naive clown that close one letter yeah so that was a big con surgeon i reinvent take the tea out of cloud native its cloud naive i went super viral you guys got t-shirts now i know you love it but yeah but that really ultimately is kind of a double-edged sword you got to be you can be naive on the on the architecture side and rolling out but also suppliers are can be naive so how would you define who's naive and who's not well in fact they're evolving as well so for example in cisco you it's a little bit more native than other ones because they're really ACI in the cloud you call you you really like configure api so the cloud and nsx is going that way and so is Arista but they're incumbent they have their own tools it's difficult for them they're moving slowly so it's much easier to start from scratch Avenue like and you know and network happiness started a few years ago there's only really two aviatrix was the first one they've been there for at least three or four years and there's other ones like Al Kyra for example that just started now that doing more connectivity but they want to create an overlay network across the cloud and start doing policies and trying abstracting all the clouds within one platform so I gotta ask you I interviewed an executive at VMware Sanjay Pune and he said to me at RSA last week oh the only b2 networking vendors left Cisco and VMware what's your respect what's your response to that obviously I mean when you have these waves as new brands that emerge like AV X and others though I think there'll be a lot of startups coming out of the woodwork how do you respond to that comment well there's still a data center there's still like a lot of action on campus and there's the one but from the cloud provisioning and clown networking in general I mean they're behind I think you know in fact you don't even need them to start to it you can if you're small enough you can just keep if you're in AWS you can user it with us construct they have to insert themselves I mean they're running behind they're all certainly incumbents I love the term Andy Jesse's that Amazon Web Services uses old guard new guard to talk about the industry what does the new guard have to do the new and new brands that emerge in is it be more DevOps oriented neck Nets a cops is that net ops is the programmability these are some of the key discussions we've been having what's your view on how you see this program their most important part is they have to make the network's simple for the dev teams and from you cannot have that you cannot make a phone call and get it via line in two weeks anymore so if you move to that cloud you have to make the cloud construct as simple enough so that for example a dev team could say okay I'm going to create this VP see but this VP see automatically being your associate to your account you cannot go out on the internet you have to go to the transit VP C so there's a lot of action in terms of the I am part and you have to put the control around them too so to make it as simple as possible you guys both I mean you're the COC aviatrix but also you guys a lot of experience going back to networking going back to I call the OSI mace which for us old folks know that means but you guys know this means I want to ask you the question as you look at the future of networking here a couple of objectives oh the cloud guys they got networking we're all set with them how do you respond to the fact that networking is changing and the cloud guys have their own networking what some of the pain points that's going on premises and these enterprises so are they good with the clouds what needs what are the key things that's going on in networking that makes it more than just the cloud networking what's your take on well I as I said earlier that once you you could easily provision in the cloud you can easily connect to that cloud is when you start troubleshooting application in the cloud and try to scale so this that's where the problem occurs see what you're taking on it and you'll hear from the from the customers that that we have on stage and I think what happens is all the cloud the clouds by definition designed to the 80/20 rule which means they'll design 80% of the basic functionality and they'll lead the 20% extra functionality that of course every enterprise needs they'll leave that to ISVs like aviatrix because why because they have to make money they have a service and they can't have huge instances for functionality that not everybody needs so they have to design to the common and that's they all do it right they have to and then the extra the problem is that can be an explosion that I talked about with enterprises that's holy that's what they need that they're the ones who need that extra 20% so that's that's what I see is is there's always gonna be that extra functionality the in in an automated and simple way that you talked about but yet powerful with up with the visibility and control that they expect of on prep that that's that kind of combination that yin and the yang that people like us are providing some I want to ask you were gonna ask some of the cloud architect customer panels it's the same question this pioneers doing some work here and there's also the laggards who come in behind the early adopters what's gonna be the tipping point what are some of those conversations that the cloud architects are having out there or what's the signs that they need to be on this multi cloud or cloud native networking trend what are some the signals that are going on in their environment what are some of the threshold or things that are going on that there can pay attention to well well once they have application and multiple cloud and they have they get wake up at 2:00 in the morning to troubleshoot them they don't know it's important so I think that's the that's where the robber will hit the road but as I said it's easier to prove it it's okay it's 80s it's easy user transit gateway put a few V pcs and you're done and use create some presents like equinox and do Direct Connect and Express route with Azure that looks simple is the operations that's when they'll realize okay now I need to understand our car networking works I also need a tool that give me visibility and control not button tell me that I need to understand the basic underneath it as well what are some of the day in the life scenarios that you envision happening with multi cloud because you think about what's happening it kind of has that same vibe of interoperability choice multi-vendor because you have multi clouds essentially multi vendor these are kind of old paradigms that we've lived through the client-server and internet working wave what are some of those scenarios of success and that might be possible it would be possible with multi cloud and cloud native networking well I think once you have good enough visibility to satisfy your customers you know not only like to keep the service running an application running but to be able to provision fast enough I think that's what you want to achieve small final question advice for folks watching on the live stream if they're sitting there as a cloud architect or a CXO what's your advice to them right now in this market because honestly public check hybrid cloud they're working on that that gets on-premise is done now multi-class right behind it what's your advice the first thing they should do is really try to understand cloud networking for each of their cloud providers and then understand the limitation and is what their cloud service provider offers enough or you need to look to a third party but you don't look at a third party to start to it especially an incumbent one so it's tempting to say on and I have a bunch of f5 experts nothing against f5 I'm going to bring my five in the cloud when you can use a needle be that automatically understand ease ease and auto-scaling and so on and you understand that's much simpler but sometimes you need you have five because you have requirements you have like AI rules and that kind of stuff that you use for years you cannot do it's okay I have requirement and that net I'm going to use legacy stuff and then you have to start thinking okay what about visibility control about the tree cloud but before you do that you have to understand the limitation of the existing cloud providers so first try to be as native as possible until things don't work after that you can start taking multi-cloud great insight somewhat thank you for coming someone in charge with Gardner thanks for sharing thank you appreciate it [Applause] informatica is known as the leading enterprise cloud data management company we are known for being the top in our industry in at least five different products over the last few years especially we've been transforming into a cloud model which allows us to work better with the trends of our customers in order to see agile and effective in a business you need to make sure that your products and your offerings are just as relevant in all these different clouds than what you're used to and what you're comfortable with one of the most difficult challenges we've always had is that because we're a data company we're talking about data that a customer owns some of that data may be in the cloud some of that data may be on Prem some of them data may be actually in their data center in another region or even another country and having that data connect back to our systems that are located in the cloud has always been a challenge when we first started our engagement with aviatrix we only had one plan that was Amazon it wasn't till later that a jerk came up and all of a sudden we found hey the solution we already had in place for aviatrix already working in Amazon and now works in Missouri as well before we knew it GCP came up but it really wasn't a big deal for us because we already had the same solution in Amazon and integer now just working in GCP by having a multi cloud approach we have access to all three of them but more commonly it's not just one it's actually integrations between multiple we have some data and ensure that we want to integrate with Amazon we have some data in GCP that we want to bring over to a data Lake assure one of the nice things about aviatrix is that it gives a very simple interface that my staff can understand and use and manage literally hundreds of VPNs around the world and while talking to and working with our customers who are literally around the world now that we've been using aviatrix for a couple years we're actually finding that even problems that we didn't realize we had were actually solved even before we came across the problem and it just worked cloud companies as a whole are based on reputation we need to be able to protect our reputation and part of that reputation is being able to protect our customers and being able to protect more importantly our customers data aviatrix has been helpful for us in that we only have one system that can manage this whole huge system in a simple easy direct model aviatrix is directly responsible for helping us secure and manage our customers not only across the world but across multiple clouds users don't have to be VPN or networking experts in order to be able to use the system all the members on my team can manage it all the members regardless of their experience can do different levels of it one of the unexpected two advantages of aviatrix is that I don't have to sell it to my management the fact that we're not in the news at three o'clock in the morning or that we don't have to get calls in the middle of the night no news is good news especially in networking things that used to take weeks to build are done in hours I think the most important thing about a matrix is it provides me consistency aviatrix gives me a consistent model that I can use across multiple regions multiple clouds multiple customers okay welcome back to altitude 2020 for the folks on the livestream I'm John for Steve Mulaney with CEO of aviatrix for our first of two customer panels on cloud with cloud network architects we got Bobby Willoughby they gone Luis Castillo of National Instruments and David should Nick with fact set guys welcome to the stage for this digital event come on up [Music] hey good to see you thank you okay okay customer panelist is my favorite part we get to hear the real scoop we got the gardener giving us the industry overview certainly multi clouds very relevant and cloud native networking is the hot trend with the live stream out there and the digital event so guys let's get into it the journey is you guys are pioneering this journey of multi cloud and cloud native networking and it's soon gonna be a lot more coming so I want to get into the journey what's it been like is it real you got a lot of scar tissue and what are some of the learnings yeah absolutely so multi cloud is whether or not we we accepted as a network engineers is a is a reality like Steve said about two years ago companies really decided to to just to just bite the bullet and and and move there whether or not whether or not we we accept that fact we need to now create a consistent architecture across across multiple clouds and that that is challenging without orchestration layers as you start managing different different tool sets in different languages across different clouds so that's it's really important that to start thinking about that guys on the other panelists here there's different phases of this journey some come at it from a networking perspective some come in from a problem troubleshooting what's what's your experiences yeah so from a networking perspective it's been incredibly exciting it's kind of a once-in-a-generation 'el opportunity to look at how you're building out your network you can start to embrace things like infrastructure as code that maybe your peers on the systems teams have been doing for years but it just never really worked on pram so it's really it's really exciting to look at all the opportunities that we have and then all the interesting challenges that come up that you that you get to tackle an effect said you guys are mostly AWS right yep right now though we are looking at multiple clouds we have production workloads running in multiple clouds today but a lot of the initial work has been with Amazon and you've seen it from a networking perspective that's where you guys are coming at it from yep yeah we evolved more from a customer requirement perspective started out primarily as AWS but as the customer needed more resources to measure like HPC you know as your ad things like that even recently Google at Google Analytics our journey has evolved into mortal multi-cloud environment Steve weigh in on the architecture because this has been the big conversation I want you to lead this second yeah so I mean I think you guys agree the journey you know it seems like the journey started a couple years ago got real serious the need for multi-cloud whether you're there today of course it's gonna be there in the future so that's really important I think the next thing is just architecture I'd love to hear what you you know had some comments about architecture matters it all starts I mean every Enterprise that I talk to maybe talk about architecture and the importance of architecture maybe Bobby it's a particular perspective we sorted a journey five years ago Wow okay and we're just now starting our fourth evolution of our network architect and we'll call it networking security net sec yep adverse adjusters network and that fourth generation or architectures be based primarily upon Palo Alto Networks an aviatrix a matrix doing the orchestration piece of it but that journey came because of the need for simplicity okay I need for multi-cloud orchestration without us having to go and do reprogramming efforts across every cloud as it comes along right I guess the other question I also had around architectures also Louis maybe just talk about I know we've talked a little bit about you know scripting right and some of your thoughts on that yeah absolutely so so for us we started we started creating the network constructs with cloud formation and we've we've stuck with that for the most part what's interesting about that is today on premise we have a lot of a lot of automation around around how we provision networks but cloud formation has become a little bit like the new manual for us so we're now having issues with having to to automate that component and making it consistent with our on-premise architecture making it consistent with Azure architecture and Google cloud so it's really interesting to see to see companies now bring that layer of abstraction that SD when brought to the to the wine side now it's going up into into the into the cloud networking architecture so on the fourth generation of you mentioned you're in the fourth gen architecture what do you guys what have you learned is there any lessons scar tissue what to avoid what worked what was some of the there was a path that's probably the biggest list and there is when you think you finally figured it out you have it right Amazon will change something as you change something you know transit gateways a game changer so in listening to the business requirements is probably the biggest thing we need to do up front but I think from a simplicity perspective like I said we don't want to do things four times we want to do things one time we won't be able to write to an API which aviatrix has and have them do the orchestration for us so that we don't have to do it four times how important is architecture in the progression is it you guys get thrown in the deep end to solve these problems or you guys zooming out and looking at it it's a I mean how are you guys looking at the architecture I mean you can't get off the ground if you don't have the network there so all of those there we've gone through similar evolutions we're on our fourth or fifth evolution I think about what we started off with Amazon without a direct connect gate without a transit Gateway without a lot of the things that are available today kind of the 80/20 that Steve was talking about just because it wasn't there doesn't mean we didn't need it so we needed to figure out a way to do it we couldn't say oh you need to come back to the network team in a year and maybe Amazon will have a solution for it right you need to do it now and in evolve later and maybe optimize or change the way you're doing things in the future but don't sit around and wait you can I'd love to have you guys each individually answer this question for the live stream because it comes up a lot a lot of cloud architects out in the community what should they be thinking about the folks that are coming into this proactively and/or realizing the business benefits are there what advice would you guys give them an architecture what should be they be thinking about and what are some guiding principles you could share so I would start with looking at an architecture model that that can that can spread and and give consistency they're different to different cloud vendors that you will absolutely have to support cloud vendors tend to want to pull you into using their native toolset and that's good if only it was realistic to talk about only one cloud but because it doesn't it's it's it's super important to talk about and have a conversation with the business and with your technology teams about a consistent model so that's the David yeah talking as earlier about day two operations so how do I design how do I do my day one work so that I'm not you know spending eighty percent of my time troubleshooting or managing my network because I'm doing that then I'm missing out on ways that I can make improvements or embrace new technologies so it's really important early on to figure out how do I make this as low maintenance as possible so that I can focus on the things that the team really should be focusing on Bobby your advice the architect I don't know what else I can do that simplicity of operations is key alright so the holistic view of day to operation you mentioned let's can jump in day one is your your your getting stuff set up day two is your life after all right this is kinda what you're getting at David so what does that look like what are you envisioning as you look at that 20 mile stair out post multi-cloud world what are some of the things that you want in a day to operations yeah infrastructure is code is really important to us so how do we how do we design it so that we can fit start making network changes and fitting them into like a release pipeline and start looking at it like that rather than somebody logging into a router CLI and troubleshooting things on in an ad hoc nature so moving more towards the DevOps model is anything on that day - yeah I would love to add something so in terms of day 2 operations you can you can either sort of ignore the day 2 operations for a little while where you get well you get your feet wet or you can start approaching it from the beginning the fact is that the the cloud native tools don't have a lot of maturity in that space and when you run into an issue you're gonna end up having a bad day going through millions and millions of logs just to try to understand what's going on so that's something that that the industry just now is beginning to realize it's it's such a such a big gap I think that's key because for us we're moving to more of an event-driven or operations in the past monitoring got the job done it's impossible to modern monitor something there's nothing there when the event happens all right so the event-driven application and then detect is important yeah I think garden was all about the cloud native wave coming into networking that's gonna be a serious thing I want to get you guys perspectives I know you have different views of how you come into the journey and how you're executing and I always say the beauties in the eye of the beholder and that kind of applies how the networks laid out so Bobby you guys do a lot of high-performance encryption both on AWS and Azure that's kind of a unique thing for you how are you seeing that impact with multi cloud yeah and that's a new requirement for us to where we we have an intern crypt and they they ever get the question should I encryption and I'll encrypt the answer is always yes you should encrypt when you can encrypt for our perspective we we need to migrate a bunch of data from our data centers we have some huge data centers and then getting that data to the cloud is the timely experiencing some cases so we have been mandated that we have to encrypt everything leaving the data center so we're looking at using the aviatrix insane mode appliances to be able to encrypt you know 10 20 gigabits of data as it moves to the cloud itself David you're using terraform you got fire Ned you've got a lot of complexity in your network what do you guys look at the future for yours environment yeah so something exciting that or yeah now is fire net so for our security team they obviously have a lot of a lot of knowledge base around Palo Alto and with our commitments to our clients you know it's it's it's not very easy to shift your security model to a specific cloud vendor right so there's a lot of stuck to compliance of things like that where being able to take some of what you've you know you've worked on for years on Bram and put it in the cloud and have the same type of assurance that things are gonna work and be secure in the same way that they are on prem helps make that journey into the cloud a lot easier and Louis you guys got scripting and get a lot of things going on what's your what's your unique angle on this yeah no absolutely so full disclosure I'm not a not not an aviatrix customer yet it's ok we want to hear the truth that's good Ellis what are you thinking about what's on your mind no really when you when you talk about implementing the tool like this it's really just really important to talk about automation and focus on on value so when you talk about things like and things like so yeah encrypting tunnels and encrypting the paths and those things are it should it should should be second nature really when you when you look at building those backends and managing them with your team it becomes really painful so tools like aviatrix that that add a lot of automation it's out of out of sight out of mind you can focus on the value and you don't have to focus on so I gotta ask you guys I see AV traces here they're they're a supplier to the sector but you guys are customers everyone's pitching you stuff people are not gonna buy my stuff how do you guys have that conversation with the suppliers like the cloud vendors and other folks what's the what's it like where API all the way you got to support this what are some of the what are some of your requirements how do you talk to and evaluate people that walk in and want to knock on your door and pitch you something what's the conversation like um it's definitely it's definitely API driven we we definitely look at the at that the API structure of the vendors provide before we select anything that that is always first in mind and also what a problem are we really trying to solve usually people try to sell or try to give us something that isn't really valuable like implementing a solution on the on the on the cloud isn't really it doesn't really add a lot of value that's where we go David what's your conversation like with suppliers you have a certain new way to do things as as becomes more agile and essentially the networking become more dynamic what are some of the conversation is with the either incumbents or new new vendors that you're having what it what do you require yeah so ease of use is definitely definitely high up there we've had some vendors come in and say you know hey you know when you go to set this up we're gonna want to send somebody on site and they're gonna sit with you for your day to configure it and that's kind of a red flag what wait a minute you know do we really if one of my really talented engineers can't figure it out on his own what's going on there and why is that so you know having having some ease-of-use and the team being comfortable with it and understanding it is really important Bobby how about you I mean the old days was do a bake-off and you know the winner takes all I mean is it like that anymore what's the Volvic bake-off last year first you win so but that's different now because now when you you get the product you can install the product in AWS energy or have it up and running a matter of minutes and so the key is is they can you be operational you know within hours or days instead of weeks but but do we also have the flexibility to customize it to meet your needs could you want to be you won't be put into a box with the other customers we have needs that surpass their cut their needs yeah I almost see the challenge that you guys are living where you've got the cloud immediate value to make an roll-up any solutions but then you have might have other needs so you've got to be careful not to buy into stuff that's not shipping so you're trying to be proactive at the same time deal with what you got I mean how do you guys see that evolving because multi-cloud to me is definitely relevant but it's not yet clear how to implement across how do you guys look at this baked versus you know future solutions coming how do you balance that so again so right now we we're we're taking the the ad hoc approach and and experimenting with the different concepts of cloud and really leveraging the the native constructs of each cloud but but there's a there's a breaking point for sure you don't you don't get to scale this I like like Simone said and you have to focus on being able to deliver a developer they're their sandbox or their play area for the for the things that they're trying to build quickly and the only way to do that is with the with with some sort of consistent orchestration layer that allows you to so you've got a lot more stuff to be coming pretty quickly IDEs area I do expect things to start to start maturing quite quite quickly this year and you guys see similar trend new stuff coming fast yeah part of the biggest challenge we've got now is being able to segment within the network being able to provide segmentation between production on production workloads even businesses because we support many businesses worldwide and and isolation between those is a key criteria there so the ability to identify and quickly isolate those workloads is key so the CIOs that are watching or that are saying hey take that he'll do multi cloud and then you know the bottoms up organization think pause you're kind of like off a little bit it's not how it works I mean what is the reality in terms of implementing you know and as fast as possible because the business benefits are clear but it's not always clear in the technology how to move that fast yeah what are some of the barriers one of the blockers what are the enabler I think the reality is is that you may not think you're multi-cloud but your business is right so I think the biggest barriers there is understanding what the requirements are and how best to meet those requirements in a secure manner because you need to make sure that things are working from a latency perspective that things work the way they did and get out of the mind shift that you know it was a cheery application in the data center it doesn't have to be a Tier three application in the cloud so lift and shift is is not the way to go scale is a big part of what I see is the competitive advantage to allow these clouds and used to be proprietary network stacks in the old days and then open systems came that was a good thing but as clouds become bigger there's kind of an inherent lock in there with the scale how do you guys keep the choice open how're you guys thinking about interoperability what are some of the conversations and you guys are having around those key concepts well when we look at when we look at the moment from a networking perspective it it's really key for you to just enable enable all the all the clouds to be to be able to communicate between them developers will will find a way to use the cloud that best suits their their business team and and like like you said it's whether whether you're in denial or not of the multi cloud fact that your company is in already that's it becomes really important for you to move quickly yeah and a lot of it also hinges on how well is the provider embracing what that specific cloud is doing so are they are they swimming with Amazon or sure and just helping facilitate things they're doing the you know the heavy lifting API work for you or they swimming upstream and they're trying to hack it all together in a messy way and so that helps you you know stay out of the lock-in because they're you know if they're doing if they're using Amazon native tools to help you get where you need to be it's not like Amazon's gonna release something in the future that completely you know makes you have designed yourself into a corner so the closer they're more cloud native they are the more the easier it is to to deploy but you also need to be aligned in such a way that you can take advantage of those cloud native technologies will it make sense tgw is a game-changer in terms of cost and performance right so to completely ignore that would be wrong but you know if you needed to have encryption you know teach Adobe's not encrypted so you need to have some type of a gateway to do the VPN encryption you know so the aviatrix tool give you the beauty of both worlds you can use tgw with a gateway Wow real quick in the last minute we have I want to just get a quick feedback from you guys I hear a lot of people say to me hey the I picked the best cloud for the workload you got and then figure out multi cloud behind the scenes so that seems to be do you guys agree with that I mean is it do I go Mull one cloud across the whole company or this workload works great on AWS that work was great on this from a cloud standpoint do you agree with that premise and then wit is multi clouds did you mall together yeah from from an application perspective it it can be per workload but it can also be an economical decision certain enterprise contracts will will pull you in one direction that add value but the the network problem is still the same doesn't go away yeah yeah I mean you don't want to be trying to fit a square into a round hall right so if it works better on that cloud provider then it's our job to make sure that that service is there and people can use it agree you just need to stay ahead of the game make sure that the network infrastructure is there secure is available and is multi cloud capable yeah I'm at the end of the day you guys just validating that it's the networking game now how cloud storage compute check networking is where the action is awesome thanks for your insights guys appreciate you coming on the panel appreciate thanks thank you [Applause] [Music] [Applause] okay welcome back on the live feed I'm John fritz T Blaney my co-host with aviatrix I'm with the cube for the special digital event our next customer panel got great another set of cloud network architects Justin Smith was aura Justin broadly with Ellie Mae and Amit Oh tree job with Cooper welcome to stage [Applause] all right thank you thank you oK you've got all the cliff notes from the last session welcome rinse and repeat yeah yeah we're going to go under the hood a little bit I think they nailed the what we've been reporting and we've been having this conversation around networking is where the action is because that's the end of the day you got a move a pack from A to B and you get workloads exchanging data so it's really killer so let's get started Amit what are you seeing as the journey of multi cloud as you go under the hood and say okay I got to implement this I have to engineer the network make it enabling make it programmable make it interoperable across clouds I mean that's like I mean almost sounds impossible to me what's your take yeah I mean it's it seems impossible but if you are running an organization which is running infrastructure as a cordon all right it is easily doable like you can use tools out there that's available today you can use third-party products that can do a better job but but put your architecture first don't wait architecture may not be perfect put the best architecture that's available today and be agile to ET rate and make improvements over the time we got to Justin's over here so I have to be careful when I point a question adjusting they both have to answer okay journeys what's the journey been like I mean is there phases we heard that from Gardner people come into multi cloud and cloud native networking from different perspectives what's your take on the journey Justin yeah I mean from Mars like - we started out very much focused on one cloud and as we started doing errands we started doing new products the market the need for multi cloud comes very apparent very quickly for us and so you know having an architecture that we can plug in play into and be able to add and change things as it changes is super important for what we're doing in the space just in your journey yes for us we were very ad hoc oriented and the idea is that we were reinventing all the time trying to move into these new things and coming up with great new ideas and so rather than it being some iterative approach with our deployments that became a number of different deployments and so we shifted that tour and the network has been a real enabler of this is that it there's one network and it touches whatever cloud we want it to touch and it touches the data centers that we need it to touch and it touches the customers that we need it to touch our job is to make sure that the services that are of and one of those locations are available in all of the locations so the idea is not that we need to come up with this new solution every time it's that we're just iterating on what we've already decided to do before we get the architecture section I want to ask you guys a question I'm a big fan of you know let the app developers have infrastructure as code so check but having the right cloud run that workload I'm a big fan of that if it works great but we just heard from the other panel you can't change the network so I want to get your thoughts what is cloud native networking and is that the engine really that's the enabler for this multi cloud trend but you guys taken we'll start with Amit what do you think about that yeah so you are gonna have workloads running in different clouds and the workloads would have affinity to one cloud over other but how you expose that it's matter of how you are going to build your networks how we are going to run security how we are going to do egress ingress out of it so it's the big problem how do you split says what's the solution what's the end the key pain points and problem statement I mean the key pain point for most companies is how do you take your traditional on-premise network and then blow that out to the cloud in a way that makes sense you know IP conflicts you have IP space you pub public eye peas and premise as well as in the cloud and how do you kind of make them a sense of all of that and I think that's where tools like aviatrix make a lot of sense in that space from our site it's it's really simple it's latency and bandwidth and availability these don't change whether we're talking about cloud or data center or even corporate IT networking so our job when when these all of these things are simplified into like s3 for instance and our developers want to use those we have to be able to deliver that and for a particular group or another group that wants to use just just GCP resources these aren't we have to support these requirements and these wants as opposed to saying hey that's not a good idea now our job is to enable them not to disable them do you think you guys think infrastructure as code which I love that I think it's that's the future it is we saw that with DevOps but I just start getting the networking is it getting down to the network portion where it's network as code because storage and compute working really well is seeing all kubernetes on ServiceMaster and network is code reality is it there is it still got work to do it's absolutely there I mean you mentioned net DevOps and it's it's very real I mean in Cooper we build our networks through terraform and on not only just out of fun build an API so that we can consistently build V nets and VPC all across in the same way we get to do it yeah and even security groups and then on top and aviatrix comes in we can peer the networks bridge bridge all the different regions through code same with you guys but yeah about this everything we deploy is done with automation and then we also run things like lambda on top to make changes in real time we don't make manual changes on our network in the data center funny enough it's still manual but the cloud has enabled us to move into this automation mindset and and all my guys that's what they focus on is bringing what now what they're doing in the cloud into the data center which is kind of opposite of what it should be that's full or what it used to be it's full DevOps then yes yeah I mean for us it was similar on premise still somewhat very manual although we're moving more Norton ninja and terraform concepts but everything in the production environment is colored confirmation terraform code and now coming into the datacenter same I just wanted to jump in on a Justin Smith one of the comment that you made because it's something that we always talk about a lot is that the center of gravity of architecture used to be an on-prem and now it's shifted in the cloud and once you have your strategic architecture what you--what do you do you push that everywhere so what you used to see at the beginning of cloud was pushing the architecture on prem into cloud now i want to pick up on what you said to you others agree that the center of architect of gravity is here i'm now pushing what i do in the cloud back into on Prem and wait and then so first that and then also in the journey where are you at from zero to a hundred of actually in the journey to cloud do you 50% there are you 10% yes I mean are you evacuating data centers next year I mean were you guys at yeah so there's there's two types of gravity that you typically are dealing with no migration first is data gravity and your data set and where that data lives and then the second is the network platform that interrupts all that together right in our case the data gravity sold mostly on Prem but our network is now extend out to the app tier that's going to be in cloud right eventually that data gravity will also move to cloud as we start getting more sophisticated but you know in our journey we're about halfway there about halfway through the process we're taking a handle of you know lift and shift and when did that start and we started about three years ago okay okay go by it's a very different story it started from a garage and one hundred percent on the clock it's a business spend management platform as a software-as-a-service one hundred percent on the cloud it was like ten years ago right yes yeah you guys are riding the wave love that architecture Justin I want to ask you Sora you guys mentioned DevOps I mean obviously we saw the huge observability wave which is essentially network management for the cloud in my opinion right yeah it's more dynamic but this is about visibility we heard from the last panel you don't know what's being turned on or turned off from a services standpoint at any given time how is all this playing out when you start getting into the DevOps down well this layer this is the big challenge for all of us as visibility when you talk transport within a cloud you know we very interestingly we have moved from having a backbone that we bought that we owned that would be data center connectivity we now I work for soar as a subscription billing company so we want to support the subscription mindset so rather than going and buying circuits and having to wait three months to install and then coming up with some way to get things connected and resiliency and redundancy I my backbone is in the cloud I use the cloud providers interconnections between regions to transport data across and and so if you do that with their native solutions you you do lose visibility there there are areas in that that you don't get which is why controlling you know controllers and having some type of management plane is a requirement for us to do what we're supposed to do and provide consistency while doing it a great conversation I loved when you said earlier latency bandwidth availability with your sim pop3 things guys SLA I mean you just do ping times are between clouds it's like you don't know what you're getting for round-trip times this becomes a huge kind of risk management black hole whatever you want to call blind spot how are you guys looking at the interconnects between clouds because you know I can see that working from you know ground to cloud I'm per cloud but when you start doing with multi clouds workloads I mean s LA's will be all over the map won't they just inherently but how do you guys view that yeah I think we talked about workload and we know that the workloads are going to be different in different clouds but they are going to be calling each other so it's very important to have that visibility that you can see how data is flowing at what latency and whatever ability is our is there and our authority needs to operate on that so it's so you use the software dashboard look at the times and look at the latency in the old days strong so on open so on you try to figure it out and then your days you have to figure out just what she reinsert that because you're in the middle of it yeah I mean I think the the key thing there is that we have to plan for that failure we have to plan for that latency in our applications that start thinking start tracking in your SLI something you start planning for and you loosely couple these services and a much more micro services approach so you actually can handle that kind of failure or that type of unknown latency and unfortunately the cloud has made us much better at handling exceptions a much better way you guys are all great examples of cloud native from day one and you guys had when did you have the tipping point moment or the Epiphany of saying a multi clouds real I can't ignore it I got to factor it into all my design design principles and and everything you're doing what's it was there a moment was it was it from day one no there were two reasons one was the business so in business there was some affinity to not be in one cloud or to be in one cloud and that drove from the business side so as a cloud architect our responsibility was to support that business and other is the technology some things are really running better in like if you are running dot Network load or you are going to run machine learning or AI so that you have you would have that reference of one cloud over other so it was the bill that we got from AWS I mean that's that's what drives a lot of these conversations is the financial viability of what you're building on top of it which is so we this failure domain idea which is which is fairly interesting is how do I solve or guarantee against a failure domain you have methodologies with you know back-end direct connects or interconnect with GCP all of these ideas are something that you have to take into account but that transport layer should not matter to whoever we're building this for our job is to deliver the frames in the packets what that flows across how you get there we want to make that seamless and so whether it's a public internet API call or it's a back-end connectivity through Direct Connect it doesn't matter it just has to meet a contract that you signed with your application folks yeah that's the availability piece just in your thoughts on anything any common uh so actually a multi clouds become something much more recent in the last six to eight months I'd say we always kind of had a very much an attitude of like moving to Amazon from our private cloud is hard enough why complicate it further but the realities of the business and as we start seeing you know improvements in Google and Asia and different technology spaces the need for multi cloud becomes much more important as well as our acquisition strategies I matured we're seeing that companies that used to be on premise that we typically acquire are now very much already on a cloud and if they're on a cloud I need to plug them into our ecosystem and so that's really change our multi cloud story in a big way I'd love to get your thoughts on the clouds versus the clouds because you know you compare them Amazon's got more features they're rich with features I see the bills are how could people using them but Google's got a great network Google's networks pretty damn good and then you got a sure what's the difference between the clouds who with they've evolved something whether they peak in certain areas better than others what what are the characteristics which makes one cloud better do they have a unique feature that makes as you're better than Google and vice versa what do you guys think about the different clouds yeah to my experience I think there is approaches different in many places Google has a different approach very DevOps friendly and you can run your workload like the your network and spend regions time I mean but our application ready to accept that MS one is evolving I mean I remember 10 years back Amazon's Network was a flat network we will be launching servers and 10.0.0.0 so the VP sees concept came out multi-account came out so they are evolving as you are at a late start but because they have a late start they saw the pattern and they they have some mature set up on the yeah I think they're all trying to say they're equal in their own ways I think they all have very specific design philosophies that allow them to be successful in different ways and you have to kind of keep that in mind as you architectural solution for example amazon has a very much a very regional affinity they don't like to go cross region in their architecture whereas Google is very much it's a global network we're gonna think about as a global solution I think Google also has advantages its third to market and so has seen what Asia did wrong it seemed with AWS did wrong and it's made those improvements and I think that's one of their big advantage at great scale to Justin thoughts on the cloud so yeah Amazon built from the system up and Google built from the network down so their ideas and approaches are from a global versus or regional I agree with you completely that that is the big number one thing but the if you look at it from the outset interestingly the inability or the ability for Amazon to limit layer 2 broadcasting and and what that really means from a VPC perspective changed all the routing protocols you can use all the things that we have built inside of a data center to provide resiliency and and and make things seamless to users all of that disappeared and so because we had to accept that at the VPC level now we have to accept it at the LAN level Google's done a better job of being able to overcome those things and provide those traditional Network facilities to us just great panel can go all day here's awesome so I heard we could we'll get to the cloud native naive questions so kind of think about what's not even what's cloud is that next but I got to ask you had a conversation with a friend he's like Wayne is the new land so if you think about what the land was at a datacenter when is the new link you could talking about the cloud impact so that means st when the old st way is kind of changing into the new land how do you guys look at that because if you think about it what lands were for inside a premises was all about networking high-speed but now when you take the win and make it essentially a land do you agree with that and how do you view this trend and is it good or bad or is it ugly and what's what you guys take on this yeah I think it's a it's a thing that you have to work with your application architect so if you are managing networks and if you are a sorry engineer you need to work with them to expose the unreliability that would bring in so the application has to hand a lot of this the difference in the latencies and and the reliability has to be worked through the application there Lanois same concept is that BS I think we've been talking about for a long time the erosion of the edge and so is this is just a continuation of that journey we've been on for the last several years as we get more and more cloud native and we start about API is the ability to lock my data in place and not be able to access it really goes away and so I think this is just continuation that thing I think it has challenges we start talking about weighing scale versus land scale the tooling doesn't work the same the scale of that tooling is much larger and the need to automation is much much higher in a way and than it was in a land that's where is what you're seeing so much infrastructure as code yeah yes so for me I'll go back again to this its bandwidth and its latency right that bet define those two land versus win but the other thing that's comes up more and more with cloud deployments is where is our security boundary and where can I extend this secure aware appliance or set of rules to to protect what's inside of it so for us we're able to deliver vr af-s or route forwarding tables for different segments wherever we're at in the world and so they're they're trusted to talk to each other but if they're gonna go to someplace that's outside of their their network then they have to cross a security boundary and where we enforce policy very heavily so for me there's it's not just land when it's it's how does environment get to environment more importantly that's a great point and security we haven't talked to yet but that's got to be baked in from the beginning this architecture thoughts on security are you guys are dealing with it yeah start from the base have apt to have security built in have TLS have encryption on the data I transit data at rest but as you bring the application to the cloud and they are going to go multi-cloud talking to over the Internet in some places well have apt web security I mean I mean our principles day Security's day zero every day and so we we always build it into our design build into our architecture into our applications it's encrypt everything it's TLS everywhere it's make sure that that data is secured at all times yeah one of the cool trends at RSA just as a side note was the data in use encryption piece which is a homomorphic stuff is interesting all right guys final question you know we heard on the earlier panel was also trending at reinvent we take the tea out of cloud native it spells cloud naive okay they got shirts now aviatrix kind of got this trend going what does that mean to be naive so if you're to your peers out there watching a live stream and also the suppliers that are trying to supply you guys with technology and services what's naive look like and what's native look like when is someone naive about implementing all this stuff so for me it's because we are in hundred-percent cloud for us it's main thing is ready for the change and you will you will find new building blocks coming in and the network design will evolve and change so don't be naive and think that it's static you wall with the change I think the big naivety that people have is that well I've been doing it this way for 20 years and been successful it's going to be successful in cloud the reality is that's not the case you have to think some of the stuff a little bit differently and you need to think about it early enough so that you can become cloud native and really enable your business on cloud yeah for me it's it's being open minded right the the our industry the network industry as a whole has been very much I am smarter than everybody else and we're gonna tell everybody how it's going to be done and we had we fell into a lull when it came to producing infrastructure and and and so embracing this idea that we can deploy a new solution or a new environment in minutes as opposed to hours or weeks or four months in some cases is really important and and so you know it's are you being closed-minded native being open minded exactly and and it took a for me it was that was a transformative kind of where I was looking to solve problems in a cloud way as opposed to looking to solve problems in this traditional old-school way all right I know we're out of time but I ask one more question so you guys so good it could be a quick answer what's the BS language when you the BS meter goes off when people talk to you about solutions what's the kind of jargon that you hear that's the BS meter going off what are people talking about that in your opinion you here you go that's total BS but what triggers use it so that I have two lines out of movies that are really I can if I say them without actually thinking them it's like 1.21 jigowatts are you out of your mind from Back to the Future right somebody's getting a bang and then and then Martin Mull and and Michael Keaton and mr. mom when he goes to 22 21 whatever it takes yeah those two right there if those go off in my mind somebody's talking to me I know they're full of baloney so a lot of speech would be a lot of speeds and feeds a lot of data did it instead of talking about what you're actually doing and solutioning for you're talking about well I does this this this and any time I start seeing the cloud vendor start benchmarking against each other it's your workload is your workload you need to benchmark yourself don't don't listen to the marketing on that that's that's all what triggers you and the bsp I think if somebody explains you and not simple they cannot explain you in simplicity then that's good all right guys thanks for the great insight great time how about a round of applause DX easy solutions integrating company than we service customers from all industry verticals and we're helping them to move to the digital world so as a solutions integrator we interface with many many customers that have many different types of needs and they're on their IT journey to modernize their applications into the cloud so we encounter many different scenarios many different reasons for those migrations all of them seeking to optimize their IT solutions to better enable their business we have our CPS organization it's cloud platform services we support AWS does your Google Alibaba corkle will help move those workloads to wherever it's most appropriate no one buys the house for the plumbing equally no one buys the solution for the networking but if the plumbing doesn't work no one likes the house and if this network doesn't work no one likes a solution so network is ubiquitous it is a key component of every solution we do the network connectivity is the lifeblood of any architecture without network connectivity nothing works properly planning and building a scalable robust network that's gonna be able to adapt with the application needs critical when encountering some network design and talking about speed the deployment aviatrix came up in discussion and we then further pursued an area DHT products have incorporated aviatrix is part of a new offering that we are in the process of developing that really enhances our ability to provide cloud connectivity for the Lyons cloud connectivity is a new line of networking services so we're getting into as our clients moving the hybrid cloud networking it is much different than our traditional based services and aviatrix provides a key component in that service before we found aviatrix we were using just native peering connections but there wasn't a way to visualize all those peering connections and with multiple accounts multiple contacts for security with a VA Church were able to visualize those different peering connections of security groups it helped a lot especially in areas of early deployment scenarios were quickly able to then take those deployment scenarios and turn them into scripts that we can then deploy repeatedly their solutions were designed to work with the cloud native capabilities first and where those cloud native capabilities fall short they then have solution sets that augment those capabilities I was pleasantly surprised number one with the aviatrix team as a whole and their level of engagement with us you know we weren't only buying the product we were buying a team that came on board to help us implement and solution that was really good to work together to learn both what aviatrix had to offer as well as enhancements that we had to bring that aviatrix was able to put into their product and meet our needs even better aviatrix was a joy to find because they really provided us the technology that we needed in order to provide multi cloud connectivity that really added to the functionality that you can't get from the basically providing services we're taking our customers on a journey to simplify and optimize their IT maybe Atrix certainly has made my job much easier okay welcome back to altitude 2020 for the digital event for the live feed welcome back I'm John Ford with the cube with Steve Mulaney CEO aviatrix for the next panel from global system integrators the folks who are building and working with folks on their journey to multi cloud and cloud native networking we've got a great panel George Buckman with dxc and Derek Monahan with wwt welcome to the stage [Applause] [Music] okay you guys are the ones out there advising building and getting down and dirty with multi cloud and cloud native network and we just heard from the customer panel you can see the diversity of where people come in to the journey of cloud it kind of depends upon where you are but the trends are all clear cloud native networking DevOps up and down the stack this has been the main engine what's your guys take of the disk Jerry to multi cloud what do you guys seeing yeah it's it's critical I mean we're seeing all of our enterprise customers enter into this they've been through the migrations of the easy stuff you know now they're trying to optimize and get more improvement so now the tough stuffs coming on right and you know they need their data processing near where their data is so that's driving them to a multi cloud environment okay we heard some of the edge stuff I mean you guys are exactly you've seen this movie before but now it's a whole new ballgame what's your take yeah so I'll give you a hint so our practice it's not called the cloud practice it's the multi cloud practice and so if that gives you a hint of how we approach things it's very consultative and so when we look at what the trends are let's look a little year ago about a year ago we're having conversations with customers let's build a data center in the cloud let's put some VP C's let's throw some firewalls with some DNS and other infrastructure out there and let's hope it works this isn't a science project so what we're trying to see is customers are starting to have more of a vision and we're helping with that consultative nature but it's totally based on the business and you got to start understanding how the lines of business are using the and then we evolved into the next journey which is a foundational approach to what are some of the problem statement customers are solving when they come to you what are the top things that are on their my house or the ease of use of Julie all that stuff but what specifically they digging into yeah so complexity I think when you look at a multi cloud approach in my view is network requirements are complex you know I think they are but I think the approach can be let's simplify that so one thing that we try to do this is how we talk to customers is let's just like you simplify an aviatrix simplifies the automation orchestration of cloud networking we're trying to simplify the design the planning implementation of infrastructure across multiple workloads across multiple platforms and so the way we do it is we sit down we look at not just use cases and not just the questions in common we tis anticipate we actually build out based on the business and function requirements we build out a strategy and then create a set of documents and guess what we actually build in the lab and that lab that we platform we built proves out this reference architecture actually works absolutely we implement similar concepts I mean we they're proven practices they work great so well George you mentioned that the hard part's now upon us are you referring to networking what is specifically were you getting at Terrance's the easy parts done now so for the enterprises themselves migrating their more critical apps or more difficult apps into the environments you know they've just we've just scratched the surface I believe on what enterprises are doing to move into the cloud to optimize their environments to take advantage of the scale and speed to deployment and to be able to better enable their businesses so they're just now really starting the - so do you get you guys see what I talked about them in terms of their Cambrian explosion I mean you're both monster system integrators with you know top fortune enterprise customers you know really rely on you for for guidance and consulting and so forth and boy they're networks is that something that you you've seen I mean does that resonate did you notice a year and a half ago and all of a sudden the importance of cloud for enterprise shoot up yeah I mean we're seeing it not okay in our internal environment as you know we're a huge company or as customers so we're experiencing that internal okay and every one of our other customers so I have another question oh but I don't know the answer to this and the lawyer never asks a question that you don't know the answer to but I'm gonna ask it anyway DX c + w WT massive system integrators why aviatrix yep so great question Steve so I think the way we approach things I think we have a similar vision a similar strategy how you approach things how we approach things that world by technology number one we want to simplify the complexity and so that's your number one priorities let's take the networking let's simplify it and I think part of the other point I'm making is we have we see this automation piece as not just an afterthought anymore if you look at what customers care about visibility and automation is probably the top three maybe the third on the list and I think that's where we see the value and I think the partnership that we're building and what I would I get excited about is not just putting yours in our lab and showing customers how it works is Co developing a solution with you figuring out hey how can we make this better right visibility's a huge thing jump in security alone network everything's around visibility what automation do you see happening in terms of progression order of operations if you will it's a low-hanging fruit what are people working on now what are what are some of the aspirational goals around when you start thinking about multi cloud and automation yep so I wanted to get back to answer that question I want to answer your question you know what led us there and why aviatrix you know in working some large internal IT projects and and looking at how we were gonna integrate those solutions you know we like to build everything with recipes where network is probably playing catch-up in the DevOps world but with a DevOps mindset looking to speed to deploy support all those things so when you start building your recipes you take a little of this a little of that and you mix it all together well when you look around you say wow look there's this big bag of a VHS let me plop that in that solves a big part of my problems that I have to speed to integrate speed to deploy and the operational views that I need to run this so that was 11 years about reference architectures yeah absolutely so you know they came with a full slate of reference textures already the out there and ready to go that fit our needs so it's very very easy for us to integrate those into our recipes what do you guys think about all the multi vendor interoperability conversations that have been going on choice has been a big part of multi-cloud in terms of you know customers want choice they didn't you know they'll put a workload in the cloud that works but this notion of choice and interoperability is become a big conversation it is and I think our approach and that's why we talk to customers is let's let's speed and be risk of that decision making process and how do we do that because the interoperability is key you're not just putting it's not just a single vendor we're talking you know many many vendors I mean think about the average number of cloud application as a customer uses a business and enterprise business today you know it's it's above 30 it's it's skyrocketing and so what we do and we look at it from an interoperability approach is how do things interoperate we test it out we validate it we build a reference architecture it says these are the critical design elements now let's build one with aviatrix and show how this works with aviatrix and I think the the important part there though is the automation piece that we add to it in visibility so I think the visibility is what's what I see lacking across the industry today and the cloud needed that's been a big topic okay in terms of aviatrix as you guys see them coming in they're one of the ones that are emerging and the new brands emerging but multi-cloud you still got the old guard incumbents with huge footprints how our customers dealing with that that kind of component and dealing with both of them yeah I mean where we have customers that are ingrained with a particular vendor and you know we have partnerships with many vendors so our objective is to provide the solution that meets that client and you they all want multi vendor they all want interoperability correct all right so I got to ask you guys a question while we were defining day two operations what does that mean I mean you guys are looking at the big business and technical components of architecture what does day to Operations mean what's the definition of that yeah so I think from our perspective my experience we you know day to operations whether it's it's not just the you know the orchestration piece and setting up and let it a lot of automate and have some you know change control you're looking at this from a data perspective how do I support this ongoing and make it easy to make changes as we evolve the the the cloud is very dynamic the the nature of how the fast is expanding the number of features is astonish trying to keep up to date with a number of just networking capabilities and services that are added so I think day to operation starts with a fundable understanding of you know building out supporting a customer's environments and making it the automation piece easy from from you know a distance I think yeah and you know taking that to the next level of being able to enable customers to have catalog items that they can pick and choose hey I need this network connectivity from this cloud location back to this on pram and being able to have that automated and provisioned just simply by ordering it for the folks watching out there guys take a minute to explain as you guys are in the trenches doing a lot of good work what are some of the engagement that you guys get into how does that progress what is that what's what happens do they call you up and say hey I need some multi-cloud or you're already in there I mean take us through why how someone can engage to use a global si to come in and make this thing happen what's looks like typical engagement look like yeah so from our perspective we typically have a series of workshops in a methodology that we kind of go along the journey number one we have a foundational approach and I don't mean foundation meaning the network foundation that's a very critical element we got a factor in security we've got a factor in automation so we think about foundation we do a workshop that starts with education a lot of times we'll go in and we'll just educate the customer what is VP she's sharing you know what is a private Lincoln or how does that impact your business we have customers I want to share services out in an ecosystem with other customers and partners well there's many ways to accomplish that so our goal is to you know understand those requirements and then build that strategy with them thoughts Georgia yeah I mean I'm one of the guys that's down in the weeds making things happen so I'm not the guy on the front line interfacing with the customers every day but we have a similar approach you know we have a consulting practice that will go out and and apply their practices to see what those and when do you parachute in yeah and when I then is I'm on the back end working with our offering development leads for the networking so we understand or seeing what customers are asking for and we're on the back end developing the solutions that integrate with our own offerings as well as enable other customers to just deploy quickly to beep their connectivity needs it so the patterns are similar right final question for you guys I want to ask you to paint a picture of what success looks like and you know the name customers didn't forget in reveal kind of who they are but what does success look like in multi-cloud as you paint a picture for the folks here and watching on the live stream it's someone says hey I want to be multi-cloud I got to have my operations agile I want full DevOps I want programmability security built in from day zero what does success look like yeah I think success looks like this so when you're building out a network the network is a harder thing to change than some other aspects of cloud so what we think is even if you're thinking about that second cloud which we have most of our customers are on to public clouds today they might be dabbling in that as you build that network foundation that architecture that takes in consideration where you're going and so once we start building that reference architecture out that shows this is how to sit from a multi cloud perspective not a single cloud and let's not forget our branches let's not forget our data centers let's not forget how all this connects together because that's how we define multi-cloud it's not just in the cloud it's on Prem and it's off from and so collectively I think the key is also is that we provide them an hld you got to start with a high level design that can be tweaked as you go through the journey but you got to give a solid structural foundation and that that networking which we think most customers think as not not the network engineers but as an afterthought we want to make that the most critical element before you start the journey Jorge from your seed how do you success look for you so you know it starts out on these journeys often start out people not even thinking about what is gonna happen what what their network needs are when they start their migration journey to the cloud so I want this success to me looks like them being able to end up not worrying about what's happening in the network when they move to the cloud good point guys great insight thanks for coming on share and pen I've got a round of applause the global system integrators Hey [Applause] [Music] okay welcome back from the live feed I'm chef for with the cube Steve Eleni CEO of aviatrix my co-host our next panel is the aviatrix certified engineers also known as aces this is the folks that are certified their engineering they're building these new solutions please welcome Toby Foster min from Attica Stacy linear from Teradata and Jennifer Reid with Victor Davis to the stage I was just gonna I was just gonna rip you guys see where's your jackets and Jen's got the jacket on okay good love the aviatrix aces pile of gear they're above the clouds towards a new heights that's right so guys aviatrix aces love the name I think it's great certified this is all about getting things engineered so there's a level of certification I want to get into that but first take us through the day in the life of an ace and just to point out Stacey's a squad leader so he's like a Squadron Leader Roger and leader yeah Squadron Leader so he's got a bunch of aces underneath him but share your perspective day-in-the-life Jennifer will start with you sure so I have actually a whole team that works for me both in the in the North America both in the US and in Mexico and so I'm eagerly working to get them certified as well so I can become a squad leader myself but it's important because one of the the critical gaps that we've found is people having the networking background because they're you graduate from college and you have a lot of computer science background you can program you've got Python but now working in packets they just don't get and so just taking them through all the processes that it's really necessary to understand when you're troubleshooting is really critical mm-hmm and because you're gonna get an issue where you need to figure out where exactly is that happening on the network you know is my my issue just in the VP C's and on the instance side is a security group or is it going on print and this is something actually embedded within Amazon itself I mean I should troubleshot an issue for about six months going back and forth with Amazon and it was the vgw VPN because they were auto-scaling on two sides and we ended up having to pull out the Cisco's and put in aviatrix so I could just say okay it's fixed and I actually actually helped the application teams get to that and get it solved yeah but I'm taking a lot of junior people and getting them through that certification process so they can understand and see the network the way I see the network I mean look I've been doing this for 25 years when I got out when I went in the Marine Corps that's what I did and coming out the network is still the network but people don't get the same training they get they got in the 90s it's just so easy just write some software they work takes care of itself yes he'll be we'll come back to that I want to come back to that problem solve with Amazon but Toby I think the only thing I have to add to that is that it's always the network fault as long as I've been in network have always been the network's fault sure and I'm even to this day you know it's still the network's fault and part of being a network guy is that you need to prove when it is and when it's not your fault and that means you need to know a little bit about a hundred different things to make that and now you've got a full stack DevOps you got to know a lot more times another hundred and these times are changing they see your squadron leader I get that right what is what is a squadron leader first can you describe what it is I think it probably just leading all the network components of it but are they from my perspective when to think about what you asked them was it's about no issues and no escalation soft my day is like that's a good outcome that's a good day it's a good day Jennifer you mentioned the Amazon thing this brings up a good point you know when you have these new waves come in you have a lot of new things newly use cases a lot of the finger-pointing it's that guys problem that girls problem so what is how do you solve that and how do you get the young guns up to speed is there training is that this is where the certification comes in those where the certification is really going to come in I know when we we got together at reinvent one of the the questions that that we had with Stephen the team was what what should our certification look like you know she would just be teaching about what aviatrix troubleshooting brings to bear but what should that be like and I think Toby and I were like no no no that's going a little too high we need to get really low because the the better someone can get at actually understanding what actually happening in the network and and where to actually troubleshoot the problem how to step back each of those processes because without that it's just a big black box and they don't know you know because everything is abstracted in Amazon Internet and Azure and Google is substracted and they have these virtual gateways they have VPNs that you just don't have the logs on it's you just don't know and so then what tools can you put in front of them of where they can look because there are full logs well as long as they turned on the flow logs when they built it you know and there's like each one of those little things that well if they'd had decided to do that when they built it it's there but if you can come in later to really supplement that with training to actual troubleshoot and do a packet capture here as it's going through then teaching them how to read that even yeah Toby we were talking before he came on up on stage about your career you've been networking all your time and then you know you're now mentoring a lot of younger people how is that going because the people who come in fresh they don't have all the old war stories they don't know you talk about you know that's dimmer fault I walk in Mayr feet in the snow when I was your age I mean it's so easy now right they say what's your take on how you train the young P so I've noticed two things one is that they are up to speed a lot faster in generalities of networking they can tell you what a network is in high school level now where I didn't learn that too midway through my career and they're learning it faster but they don't necessarily understand why it's that way or you know everybody thinks that it's always slash 24 for a subnet and they don't understand why you can break it down smaller why it's really necessary so the the ramp up speed is much faster for these guys that are coming in but they don't understand why and they need some of that background knowledge to see where it's coming from and why is it important and that's old guys that's where we thrive Jennifer you mentioned you you got in from the Marines health spa when you got into networking how what was it like then and compare it now most like we've heard earlier static versus dynamic don't be static cuz back then you just said the network you got a perimeter yeah no there was no such thing ya know so back in the day I mean I mean we had banyan vines for email and you know we had token ring and I had to set up token ring networks and figure out why that didn't work because how many of things were actually sharing it but then actually just cutting fiber and running fiber cables and dropping them over you know shelters to plug them in and oh crap they swung it too hard and shattered it now I gotta be great polished this thing and actually shoot like to see if it works I mean that was the network current five cat 5 cables to run an Ethernet you know and then from that just said network switches dumb switches like those were the most common ones you had then actually configuring routers and you know logging into a Cisco router and actually knowing how to configure that and it was funny because I had gone all the way up and was a software product manager for a while so I've gone all the way up the stack and then two and a half three years ago I came across to to work with entity group that became Victor Davis but we went to help one of our customers Avis and it was like okay so we need to fix the network okay I haven't done this in 20 years but all right let's get to it you know because it really fundamentally does not change it's still the network I mean I've had people tell me well you know when we go to containers we will not have to worry about the network and I'm like yeah you don't I do and then with this within the program abilities it really interesting so I think this brings up the certification what are some of the new things that people should be aware of that come in with the aviatrix ace certification what are some of the highlights can you guys share some of the some of the highlights around the certifications I think some of the importance is that it's it doesn't need to be vendor specific for network generality or basic networking knowledge and instead of learning how Cisco does something or how Palo Alto does something we need to understand how and why it works as a basic model and then understand how each vendor has gone about that problem and solved it in a general that's true in multi cloud as well you can't learn how cloud networking works without understanding how AWS integer and GCP are all slightly the same but slightly different and some things work and some things don't I think that's probably the number one take I think having a certification across clouds is really valuable because we heard the global si you help the business issues what does it mean to do that is it code is that networking is it configuration is that aviatrix what is the amine oxy aviatrix is a certification but what is it about the multi cloud that makes it multi networking and multi vendor and easy answer is yes so you got to be a general let's go to your hands and all you have to be it takes experience because it's every every cloud vendor has their own certification whether that's hops and [Music] advanced networking and advanced security or whatever it might be yeah they can take the test but they have no idea how to figure out what's wrong with that system and the same thing with any certification but it's really getting your hands in there and actually having to troubleshoot the problems you know actually work the problem you know and calm down it's going to be okay I mean because I don't know how many calls I've been on or even had aviatrix join me on it's like okay so everyone calm down let's figure out what's happening it's like we've looked at that screen three times looking at it again it's not going to solve that problem right but at the same time you know remaining calm but knowing that it really is I'm getting a packet from here to go over here it's not working so what could be the problem you know and actually stepping them through those scenarios but that's like you only get that by having to do it you know and seeing it and going through it and then I have a question so we you know I just see it we started this program maybe six months ago we're seeing a huge amount of interest I mean we're oversubscribed on all the training sessions we've got people flying from around the country even with coronavirus flying to go to Seattle to go to these events were oversubscribed a good is that watching leader would put there yeah something that you see in your organizations are you recommending that to people do you see I mean I'm just I would guess I'm surprised I'm not surprised but I'm really surprised by the demand if you would of this multi-cloud network certification because it really isn't anything like that is that something you guys can comment on or do you see the same things in your organization's I say from my side because we operate in the multi cloud environment so it really helps an official for us I think I would add that networking guys have always needed to use certifications to prove that they know what they know it's not good enough to say yeah I know IP addresses or I know how a network works and a couple little check marks or a little letters buying helps give you validity so even in our team we can say hey you know we're using these certifications to know that you know enough of the basics enough of the understandings that you have the tools necessary right so okay I guess my final question for you guys is why an eighth certification is relevant and then second part is share what the livestream folks who aren't yet a certified or might want to jump in to be AVH or certified engineers why is it important so why is it relevant and why shouldn't someone want to be an ace-certified I'm used to right engineer I think my views a little different I think certification comes from proving that you have the knowledge not proving that you get a certification to get no I mean they're backwards so when you've got the training and the understanding and the you use that to prove and you can like grow your certification list with it versus studying for a test to get a certification and have no understanding it okay so that who is the right person that look at this is saying I'm qualified is it a network engineer is it a DevOps person what's your view you know is it a certain you know I think cloud is really the answer it's the as we talked like the edge is getting eroded so is the network definition getting eroded we're getting more and more of some network some DevOps some security lots and lots of security because network is so involved in so many of them that's just the next progression I don't say I expend that to more automation engineers because we have those nails probably well I think that the training classes themselves are helpful especially the entry-level ones for people who may be quote-unquote cloud architects but I've never done anything and networking for them to understand why we need those things to really work whether or not they go through to eventually get a certification is something different but I really think fundamentally understanding how these things work it makes them a better architect makes some better application developer but even more so as you deploy more of your applications into the cloud really getting an understanding even from our people who've tradition down on prime networking they can understand how that's going to work in the cloud too well I know we got just under 30 seconds left but I want to get one more question than just one more for the folks watching that are you may be younger that don't have that networking training from your experiences each of you can answer why is it should they know about networking what's the benefit what's in it for them motivate them share some insights and why they should go a little bit deeper in networking Stacey we'll start with you we'll go down let's say it's probably fundamental right if you want to deliver solutions no we're going use the very top I would say if you fundamental of an operating system running on a machine how those machines talk together as a fundamental change is something that starts from the base and work your way up right well I think it's a challenge because you've come from top-down now you're gonna start looking from bottom up and you want those different systems to cross communicate and say you've built something and you're overlapping IP space not that that doesn't happen but how can I actually make that still operate without having to reappear e-platform it's like those challenges like those younger developers or sis engineers can really start to get their hands around and understand those complexities and bring that forward in their career they got to know the how the pipes are working you guys know what's going some plumbing that's right and they gotta know how it works I had a code it it's right awesome thank you guys for great insights ace certain ABS your certified engineers also known as aces give a round of applause thank you okay all right that concludes my portion thank you Steve thanks for have Don thank you very much that was fantastic everybody round of applause for John for you yeah so great event great event I'm not gonna take long we got we've got lunch outside for that for the people here just a couple of things just call to action right so we saw the aces you know for those of you out on the stream here become a certified right it's great for your career it's great for not knowledge is is fantastic it's not just an aviatrix thing it's gonna teach you about cloud networking multi-cloud networking with a little bit of aviatrix exactly what the Cisco CCIE program was for IP network that type of the thing that's number one second thing is is is is learn right so so there's a there's a link up there for the four to join the community again like I started this this is a community this is the kickoff to this community and it's a movement so go to what a v8 community aviatrix comm starting a community a multi cloud so you know get get trained learn I'd say the next thing is we're doing over a hundred seminars in across the United States and also starting into Europe soon will come out and will actually spend a couple hours and talk about architecture and talk about those beginning things for those of you on the you know on the livestream in here as well you know we're coming to a city near you go to one of those events it's a great way to network with other people that are in the industry as well as to start to learn and get on that multi-cloud journey and then I'd say the last thing is you know we haven't talked a lot about what aviatrix does here and that's intentional we want you you know leaving with wanting to know more and schedule get with us in schedule a multi our architecture workshop session so we we sit out with customers and we talk about where they're at in that journey and more importantly where they're going and define that end state architecture from networking compute storage everything and everything you heard today every panel kept talking about architecture talking about operations those are the types of things that we solve we help you define that canonical architecture that system architecture that's yours so for so many of our customers they have three by five plotted lucid charts architecture drawings and it's the customer name slash aviatrix arc network architecture and they put it on their whiteboard that's what what we and that's the most valuable thing they get from us so this becomes their twenty-year network architecture drawing that they don't do anything without talking to us and look at that architecture that's what we do in these multi hour workshop sessions with customers and that's super super powerful so if you're interested definitely call us and let's schedule that with our team so anyway I just want to thank everybody on the livestream thank everybody here hopefully it was it was very useful I think it was and joined the movement and for those of you here join us for lunch and thank you very much [Applause] [Music] you

[Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] you you you you [Music] [Music] [Music] [Music] ladies and gentlemen please take your seats good morning ladies and gentlemen this is your captain speaking we will soon be taking off on our way to altitude please keep your seatbelts fastened and remain in your seats we will be experiencing turbulence until we are above the clouds ladies and gentlemen we are now cruising at altitude sit back and enjoy the ride [Music] altitude is a community of thought leaders and pioneers cloud architects and enlightened network engineers who have individually and are now collectively leading their own IT teams and the industry on a path to lift cloud networking above the clouds empowering Enterprise IT to architect design and control their own cloud network regardless of the turbulent clouds beneath them it's time to gain altitude ladies and gentlemen Steve Mulaney president and CEO of aviatrix the leader of multi cloud networking [Music] [Applause] all right good morning everybody here in Santa Clara as well as to the what millions of people watching the livestream worldwide welcome to altitude 2020 alright so we've got a fantastic event today I'm really excited about the speakers that we have today and the experts that we have and really excited to get started so one of the things I wanted to just share was this is not a one-time event it's not a one-time thing that we're gonna do sorry for the aviation analogy but you know sherry way aviatrix means female pilot so everything we do as an aviation theme this is a take-off for a movement this isn't an event this is a takeoff of a movement a multi-cloud networking movement and community that we're inviting all of you to become part of and-and-and why we're doing that is we want to enable enterprises to rise above the clouds so to speak and build their network architecture regardless of which public cloud they're using whether it's one or more of these public clouds so the good news for today there's lots of good news but this is one good news is we don't have any PowerPoint presentations no marketing speak we know that marketing people have their own language we're not using any of that in those sales pitches right so instead what are we doing we're going to have expert panels we've got some owners chart of Gartner here we've got 10 different network architects cloud architects real practitioners they're going to share their best practices and there are real-world experiences on their journey to the multi cloud so before we start and everybody know what today is in the US it's Super Tuesday I'm not gonna get political but Super Tuesday there was a bigger Super Tuesday that happened 18 months ago and maybe eight six employees know what I'm talking about 18 months ago on a Tuesday every Enterprise said I'm gonna go to the cloud and so what that was was the Cambrian explosion for cloud for the price so Franco Bree you know what a Cambrian explosion is he had to look it up on Google 500 million years ago what happened there was an explosion of life where it went from very simple single-cell organisms to very complex multi-celled organisms guess what happened 18 months ago on a Tuesday I don't really know why but every enterprise like I said all woke up that day and said now I'm really gonna go to cloud and that Cambrian explosion of cloud went meant that I'm moving from very simple single cloud single use case simple environment to a very complex multi cloud complex use case environment and what we're here today is we're gonna go and dress that and how do you handle those those those complexities and when you look at what's happening with customers right now this is a business transformation right people like to talk about transitions this is a transformation and it's actually not just the technology transformation it's a business transformation it started from the CEO and the boards of enterprise customers where they said I have an existential threat to the survival of my company if you look at every industry who they're worried about is not the other 30 year old enterprise what they're worried about is the three year old enterprise that's leveraging cloud that's leveraging AI and that's where they fear that they're going to actually get wiped out right and so because of this existential threat this is CEO lead this is board led this is not technology led it is mandated in the organization's we are going to digitally transform our enterprise because of this existential threat and the movement to cloud is going to enable us to go do that and so IT is now put back in charge if you think back just a few years ago in cloud it was led by DevOps it was led by the applications and it was like I said before their Cambrian explosion is very simple now with this Cambrian explosion and enterprises getting very serious and mission-critical they care about visibility they care about control that about compliance conformance everything governance IT is in charge and and and that's why we're here today to discuss that so what we're going to do today is much of things but we're gonna validate this journey with customers did they see the same thing we're going to validate the requirements for multi-cloud because honestly I've never met an enterprise that is not going to be multi-cloud many are one cloud today but they all say I need to architect my network for multiple clouds because that's just what the network is there to support the applications and the applications will run and whatever cloud it runs best in and you have to be prepared for that the second thing is is is architecture again with the IT in charge you architecture matters whether it's your career whether it's how you build your house it doesn't matter horrible architecture your life is horrible forever good architecture your life is pretty good so we're going to talk about architecture and how the most fundamental and critical part of that architecture and that basic infrastructure is the network if you don't get that right nothing works right way more important and compute way more important than storm dense storage network is the foundational element of your infrastructure then we're going to talk about day two operations what does that mean well day 1 is one day of your life who you wire things up they do and beyond I tell everyone in networking and IT it's every day of your life and if you don't get that right your life is bad forever and so things like operations visibility security things like that how do I get my operations team to be able to handle this in an automated way because it's not just about configuring it in the cloud it's actually about how do i operationalize it and that's a huge benefit that we bring as aviatrix and then the last thing we're going to talk and it's the last panel we have I always say you can't forget about the humans right so all this technology all these things that we're doing it's always enabled by the humans at the end of the day if the humans fight it it won't get deployed and we have a massive skills gap in cloud and we also have a massive skill shortage you have everyone in the world trying to hire cloud network architects right there's just not enough of them going around so at aviatrix we as leaders ooh we're gonna help address that issue and try to create more people we created a program and we call the ACE program again an aviation theme it stands for aviatrix certified engineer very similar to what Cisco did with CCI es what Cisco taught you about IP networking a little bit of Cisco we're doing the same thing we're gonna teach network architects about multi-cloud networking and architecture and yeah you'll get a little bit of aviatrix training in there but this is the missing element for people's careers and also within their organization so we're gonna we're gonna go talk about that so great great event great show when to try to keep it moving I'd next want to introduce my my host he's the best in the business you guys have probably seen him multiple million times he's the co CEO and co-founder of joob John Ferrier [Applause] okay awesome great great speech they're awesome I totally agree with everything you said about the explosion happening and I'm excited here at the heart of Silicon Valley to have this event it's a special digital event with the cube and aviatrix where we live streaming to millions of people as you said maybe not a million maybe not really take this program to the world this is a little special for me because multi-cloud is the hottest wave and cloud and cloud native networking is fast becoming the key engine of the innovation so we got an hour and a half of action-packed programming we have a customer panel to customer panels before that Gartner is going to come out and talk about the industry we have a global system integrators they talk about how they're advising and building these networks and cloud native networking and then finally the Aces the aviatrix certified engineer is gonna talk more about their certifications and the expertise needed so let's jump right in and let's ask some own rashard to come on stage from Gartner we'll kick it all up [Applause] [Music] okay so kicking things off certain started gardener the industry experts on cloud really kind of more to your background talk about your background before you got the gardener yeah before because gardener was a chief network architect of a fortune five companies with thousands of sites over the world and I've been doing everything and IT from a C programmer the ninety-two a security architect to a network engineer to finally becoming a network analyst so you rode the wave now you're covering in the marketplace with hybrid cloud and now moving quickly to multi cloud is really was talking about cloud natives been discussed but the networking piece is super important how do you see that evolving well the way we see Enterprise adapt in cloud first thing you do about networking the initial phases they either go in a very ad hoc way is usually led by non non IT like a shadow IT or application people are sometime a DevOps team and it's it just goes as it's completely unplanned decreed VP sees left and right as with different account and they create mesh to manage them and they have direct connect or Express route to any of them so that's what that's a first approach and on the other side again it within our first approach you see what I call the lift and shift way we see like Enterprise IT trying to basically replicate what they have in a data center in the cloud so they spend a lot of time planning doing Direct Connect putting Cisco routers and f5 and Citrix and any checkpoint Palo Alto divides that the atoms that are sent removing that to that cloud they ask you the aha moments gonna come up a lot of our panels is where people realize that it's a multi cloud world I mean they either inherit clouds certainly they're using public cloud and on-premises is now more relevant than ever when's that aha moment that you're seeing where people go well I got to get my act together and get on this well the first but even before multi-cloud so these two approach the first one like the ad hoc way doesn't scale at some point idea has to save them because they don't think about the - they don't think about operations we have a bunch of VPC and multiple clouds the other way that if you do the left and shift week they cannot take any advantages of the cloud they lose elasticity auto-scaling pay by the drink these feature of agility features so they both realize okay neither of these words are good so I have to optimize that so I have to have a mix of what I call the cloud native services within each cloud so they start adapting like other AWS constructor is your construct or Google construct and that's what I call the optimal phase but even that they realize after that they are very different all these approaches different the cloud are different identities is completely difficult to manage across clouds I mean for example AWS as accounts there's subscription and in as ER and GCP their projects it's a real mess so they realize well I can't really like concentrate used the cloud the cloud product and every cloud that doesn't work so I have I'm doing multi cloud I like to abstract all of that still wanna manage the cloud from an epi xx view I don't necessarily want to bring my incumbent data center products but I have to do that in a more API driven cloud they're not they're not scaling piece and you were mentioning that's because there's too many different clouds yes that's the piece there so what are they doing whether they read they building different development teams as its software what's the solution well this the solution is to start architecting the cloud that's the third phase I call that the multi cloud architect phase where they have to think about abstraction that works across cloud fact even across one cloud it might not scale as well if you start having like 10,000 security group in AWS that doesn't scale you have to manage that if you have multiple VPC it doesn't scale you need a third-party identity provider so it barely scales within one cloud if you go multiple cloud it gets worse and worse see way in here what's your thoughts I thought we said this wasn't gonna be a sales pitch for aviatrix you just said exactly what we do so anyway up just a joke what do you see in terms of where people are in that multi cloud like a lot of people you know everyone I talked to started in one cloud right but then they look and they say okay but I'm now gonna move to adjourn I'm gonna move do you see a similar thing well yes they are moving but they're not there's not a lot of application that use a tree cloud at once they move one app in Azure one app in individuals one get app in Google that's what we see so far okay yeah I mean one of the mistakes that people think is they think multi-cloud no one is ever gonna go multi-cloud for arbitrage they're not gonna go and say well today I might go into Azure because I got a better rate of my instance that's never do you agree with that's never gonna happen what I've seen with enterprise is I'm gonna put the work load and the app the app decides where it runs best that may be a sure maybe Google and for different reasons and they're gonna stick there and they're not gonna move let me ask you infrastructure has to be able to support from a networking King be able to do that do you agree with that yes I agree and one thing is also very important is connecting to that cloud is kind of the easiest thing so though while I run network part of the cloud connectivity to the cloud is kind of simple you know I agree IPSec VPN and I reckon Express route that's a simple part what's difficult and even a provisioning part is easy you can use terraform and create v pieces and v nets across which we cloud providers right what's difficult is the day-to-day operations so it's what to find a to operations what is that what does that actually mean it's just the day-to-day operations after you know the natural let's add an app that's not a server let's troubleshoot a problem so what ending so your life if something changes now what do you do so what's the big concerns I want to just get back to this cloud native networking because everyone kind of knows with cloud native apps are that's the hot trend what is cloud native networking how do you how do you guys define that because that seems to be the oddest part of the multi cloud wave that's coming as cloud native networking well there's no you know official gardener definition but I can create one on another spot is do it I just want to leverage the cloud construct and a cloud epi I don't want to have to install like like for example the first version was let's put a virtual router that doesn't understand and then the cloud environment right if I have if I have to install a virtual machine it has to be cloud aware it has to understand the security group if it's a router it has to be programmable to the cloud API and and understand the cloud environment you know one things I hear a lot from either see Saussure CIOs or CXOs in general is this idea of I'm definitely on going API so it's been an API economy so API is key on that point but then they say okay I need to essentially have the right relationship with my suppliers aka clouds you call it above the clouds so the question is what do i do from an architecture standpoint do I just hire more developers and have different teams because you mentioned that's a scale point how do you solve this this problem of okay I got AWS I got GCP or Azure or whatever do I just have different teams or just expose API guys where is that optimization where's the focus well I think what you need from an android point of view is a way a control plane across the three clouds and be able to use the api of that cloud to build networks but also to troubleshoot them and do they to operation so you need a view across a three cloud that takes care of routing connectivity that's you know that's the aviatrix plug of view right there so so how do you see so again your Gartner you you you you see the industry you've been a network architect how do you see this this plan out what are the what are the legacy incumbent client-server on-prem networking people gonna do well these versus people like aviatrix well how do you see that playing out well obviously all the incumbent like Arista cisco juniper NSX right they want to basically do the lift and chip are they want to bring and you know VM I want to bring in a section that cloud they call that NSX everywhere and cisco wants bring you star in the cloud they call that each guy anywhere right so everyone what and and then there's cloud vision for my red star and Khan trailers in a cloud so they just want to bring the management plain in the cloud but it's still based most of them it's still based on putting a VM them in controlling them right you you extend your management console to the cloud that's not really cloud native right cloud native you almost have to build it from scratch we like to call that cloud naive well not so close one letter yeah so that was a big culture to reinvent take the tea out of cloud native it's cloud naive that went super viral you guys got t-shirts now I know you love yeah but yeah but that really ultimately is kind of a double-edged sword you got to be you can be naive on the on the architecture side and rolling up but also suppliers are can be naive so how would you define who's naive and who's not well in fact they're evolving as well so for example in Cisco you it's a little bit more native than other ones because they're really scr in the cloud you can't you you really like configure API so the cloud and NSX is going that way and so is Arista but they're incumbent they have their own tools is difficult for them they're moving slowly so it's much easier to start from scratch Avenue like and you know a network happiness started a few years ago there's only really two aviatrix was the first one they've been there for at least three or four years and there's other ones like Al Kyra for example that just started now that doing more connectivity but they want to create an overlay network across the cloud and start doing policies and trying abstracting all the clouds within one platform so I gotta ask you I interviewed an executive at VMware Sanjay Pune and he said to me at RSA last week I was only be two networking vendors left Cisco and VMware what's your respect what's your response to that obviously I mean when you have these waves as new brands that emerge like aviation others though I think there'll be a lot of startups coming out of the woodwork how do you respond to that comment well there's still a data center there's still like a lot of action on campus and there's the one but from the cloud provisioning and clown networking in general I mean they're behind I think you know in fact you don't even need them to start to it you can if you're small enough you can just keep if you're in a table us you can use it with us construct they have to insert themselves I mean they're running behind they're all certainly incumbents I love the term Andy Jesse's that Amazon Web Services uses old guard new guard to talk about the industry what does the new guard have to do the new and new brands that emerge in is it be more DevOps oriented neck net sec Ops is that net ops is the programmability these are some of the key discussions we've been having what's your view on how you see this ability their most important part is they have to make the network's simple for the dev teams and from you cannot have that you cannot make a phone call and get it V line in two weeks anymore so if you move to that cloud you have to make the cloud construct as simple enough so that for example a dev team could say okay I'm going to create this V PC but this V PC automatically being your associate your account you cannot go out on the internet you have to go to the transit VPC so there's a lot of action in terms of the I am part and you have to put the control around them too so to make it as simple as possible you guys both I mean you're the COC aviatrix but also you guys a lot of experience going back to networking going back to I call the OSI days which for us old folks know what that means but you guys know this means I want to ask you the question as you look at the future of networking here a couple of objections oh the cloud guys they got networking we're all set with them how do you respond to the fact that networking is changing and the cloud guys have their own networking what some of the pain points that's going on premises and these enterprises so are they good with the clouds what needs what are the key things that's going on in networking that makes it more than just the cloud networking what's your take on well as I said earlier that once you you could easily provision in the cloud you can easily connect to the cloud is when you start troubleshooting application in the cloud and try to scale so this that's what the problem occurs see what you're taking on it and you'll hear from the from the customers that that we have on stage and I think what happens is all the cloud the clouds by definition designed to the 80/20 rule which means they'll design 80% of the basic functionality and they'll lead to 20% extra functionality that of course every Enterprise needs they'll leave that to ISVs like aviatrix because why because they have to make money they have a service and they can't have huge instances for functionality that not everybody needs so they have to design to the common and that's they all do it right they have to and then the extra the problem is that can be an explosion that I talked about with enterprises that's holy that's what they need that they're the ones who need that extra 20% so that's that's what I see is is there's always going to be that extra functionality that in an automated and simple way that you talked about but yet powerful with up with the visible in control that they expect of on prep that that's that kind of combination that yin and the yang that people like us are providing some I want to ask you were gonna ask some of the cloud architect customer panels it's the same question this pioneers doing some work here and there's also the laggers who come in behind the early adopters what's gonna be the tipping point what are some of those conversations that the cloud architects are having out there or what's the signs that they need to be on this multi cloud or cloud native networking trend what are some of the signals that are going on their environment what are some of the thresholds or things that are going on that there can pay attention to well one once they have application and multiple cloud and they have they get wake up at 2:00 in the morning to troubleshoot them they don't know it's important so I think that's the that's where the robbery will hit the road but as I said it's easier to prove it it's okay it's a TBS it's easy use a transit gateway put a few V PCs and you're done and you create some presents like equinox and do Direct Connect and Express route with Azure that looks simple as the operations that's when they'll realize okay now I need to understand our car networking works I also need a tool that give me visibility and control not but I'm telling you that I need to understand a basic underneath it as well what are some of the day in the life scenarios that you envision happening with multi cloud because you think about what's happening it kind of has that same vibe of interoperability choice multi vendor because you have multi clouds essentially multi vendor these are kind of old paradigms that we've lived through the client-server an internet working wave what are some of those scenarios of success and that might be possible it would be possible with multi cloud and cloud native networking well I think once you have good enough visibility to satisfy your customers you know you not only like to keep the service running an application running but to be able to provision fast enough I think that's what you want to achieve small final question advice for folks watching on the live stream if they're sitting there as a cloud architect or a CXO what's your advice to them right now in this because honestly public cloud check hybrid cloud they're working on that that kids on premise is done now multi class right behind it what's your advice the first thing they should do is really try to understand cloud networking for each of their cloud providers and then understand the limitation and is what there's cloud service provider offers enough or you need to look to a third party but you don't look at a third party to start with especially an incumbent one so it's tempting to say I have a bunch of f5 experts nothing against f5 I'm going to bring my five in a cloud when you can use a needle be that automatically understand is ease and auto scaling and so on and you understand that's much simpler but sometimes you need you have five because you have requirements you have like AI rules and that kind of stuff that you use for years you cannot do it's okay I have requirement and that met I'm going to use legacy stuff and then you have to start taking okay what about visibility control about the three cloud but before you do that you have to understand the limitation of the existing cloud providers so first try to be as native as possible until things don't work after that you can start taking multi-cloud great insight somewhat thank you for coming summit in charge with Gardner thanks for sharing thank you appreciate it thanks [Applause] informatica is known as the leading enterprise cloud data management company we are known for being the top in our industry in at least five different products over the last few years especially we've been transforming into a cloud model which allows us to work better with the trends of our customers in order to see agile and effective in a business you need to make sure that your products and your offerings are just as relevant in all these different clouds than what you're used to and what you're comfortable with one of the most difficult challenges we've always had is that because we're a data company we're talking about data that a customer owns some of that data may be in the cloud some of that data may be on Prem some of that data may be actually in their data center in another region or even another country and having that data connect back to our systems that are located in the cloud has always been a challenge when we first started our engagement myth aviatrix we only had one plan that was Amazon it wasn't till later that a jerk came up and all of a sudden we found hey the solution we already had in place for her aviatrix already working in Amazon and now works in Missouri as well before we knew what GCP came up but it really wasn't a big deal for us because we already had the same solution in Amazon and integer now just working in GCP by having a multi cloud approach we have access to all three of them but more commonly it's not just one it's actually integrations between multiple we have some data and ensure that we want to integrate with Amazon we have some data in GCP that we want to bring over to a data Lake measure one of the nice things about aviatrix is that it gives a very simple interface that my staff can understand and use and manage literally hundreds of VPNs around the world and while talking to and working with our customers who are literally around the world now that we've been using aviatrix for a couple years we're actually finding that even problems that we didn't realize we had were actually solved even before we came across the problem and it just worked cloud companies as a whole are based on reputation we need to be able to protect our reputation and part of that reputation is being able to protect our customers and being able to protect more importantly our customers data aviatrix has been helpful for us in that we only have one system that can manage this whole huge system in a simple easy direct model aviatrix is directly responsible for helping us secure and manage our customers not only across the world but across multiple clouds users don't have to be VPN or networking experts in order to be able to use the system all the members on my team can manage it all the members regardless of their experience can do different levels of it one of the unexpected two advantages of aviatrix is that I don't have to sell it to my management the fact that we're not in the news at three o'clock in the morning or that we don't have to get calls in the middle of the night no news is good news especially in networking things that used to take weeks to build or done in hours I think the most important thing about a matrix is it provides me consistency aviatrix gives me a consistent model that I can use across multiple regions multiple clouds multiple customers okay welcome back to altitude 2020 for the folks on the livestream I'm John for Steve Mulaney with CEO of aviatrix for our first of two customer panels on cloud with cloud network architects we got Bobby Willoughby they gone Luis Castillo of National Instruments David should Nick with fact set guys welcome to the stage for this digital event come on up [Applause] [Music] hey good to see you thank you okay okay customer pal this is my favorite part we get to hear the real scoop against a gardener given this the industry overview certainly multi clouds very relevant and cloud native networking is the hot trend with a live stream out there and the digital event so guys let's get into it the journey is you guys are pioneering this journey of multi cloud and cloud native networking and the soon gonna be a lot more coming so I want to get into the journey what's it been like is it real you got a lot of scar tissue and what are some of the learnings yeah absolutely so multi cloud is whether or not we we accepted as a network engineers is a reality like Steve said about two years ago companies really decided to to just to just bite the bullet and and and move there whether or not whether or not we we accept that fact we need to now create a consistent architecture across across multiple clouds and that that is challenging without orchestration layers as you start managing different different tool sets and different languages across different clouds so that's it's really important that to start thinking about that guys on the other panelists here there's different phases of this journey some come at it from a networking perspective some come in from a problem troubleshooting what's what's your experiences yeah so from a networking perspective it's been incredibly exciting it's kind of a once-in-a-generation --all opportunity to look at how you're building out your network you can start to embrace things like infrastructure as code that maybe your peers on the systems teams have been doing for years but it just never really worked on bram so it's really it's really exciting to look at all the opportunities that we have and then all the interesting challenges that come up that you that you get to tackle an effect said you guys are mostly AWS right yep right now though we're we are looking at multiple clouds we have production workloads running in multiple clouds today but a lot of the initial work has been with Amazon and you've seen it from a networking perspective that's where you guys are coming at it from yep yeah we evolved more from a customer requirement perspective started out primarily as AWS but as the customer needed more resources to measure like HPC you know as your ad things like that even recently Google at Google Analytics our journey has evolved into more of a multi cloud environment Steve weigh in on the architecture because this has been the big conversation I want you to lead this second yeah so I mean I think you guys agree the journey you know it seems like the journey started a couple years ago got real serious the need for multi cloud whether you're there today of course it's gonna be there in the future so that's really important I think the next thing is just architecture I'd love to hear what you had some comments about architecture matters it all starts I mean every Enterprise I talk to maybe talk about architecture and the importance of architecture maybe Bobby it's a particular perspective we sorted a journey five years ago Wow okay and we're just now starting our fourth evolution of our network architect and we'll call it networking security net sec yep versus Justice Network and that fourth generation architectures be based primarily upon Palo Alto Networks an aviatrix I have a trick to in the orchestration piece of it but that journey came because of the need for simplicity ok the need for a multi cloud orchestration without us having to go and do reprogramming efforts across every cloud as it comes along right I guess the other question I also had around architectures also Louis maybe just talk about I know we've talked a little bit about you know scripting right and some of your thoughts on that yeah absolutely so so for us we started we started creating the network constructs with cloud formation and we've we've stuck with that for for the most part what's interesting about that is today on premise we have a lot of a lot of automation around around around how we provision networks but cloud formation has become a little bit like the new manual for us so we're now having issues with having the to automate that component and making it consistent with our on premise architecture making it consistent with Azure architecture and Google cloud so it's really interesting to see to see companies now bring that layer of abstraction that sty and brought to the do the web side now it's going up into into the into the cloud networking architecture so on the fourth generation of you mentioned you're in the fourth gen architecture what do you guys what have you learned is there any lessons scar tissue what to avoid what worked what was the middle it was a path that's probably the biggest lesson there is that when you think you finally figured it out you have it right Amazon will change something as you change something you know transit gateways a game changer so in listening to the business requirements is probably the biggest thing we need to do up front but I think from a simplicity perspective we like I said we don't want to do things four times we want to do things one time we won't be able to write to an API which aviatrix has and have them do the orchestration for us so that we don't have to do it four times how important is architecture in the progression is it you guys get thrown in the deep end to solve these problems or you guys zooming out and looking at it it's a I mean how are you guys looking at the architecture I mean you can't get off the ground if you don't have the network there so all of those now we've gone through similar evolutions we're on our fourth or fifth evolution I think about what we started off with Amazon without a direct connect gateway about a trans a gateway without a lot of the things that are available today kind of the 80/20 that Steve was talking about just because it wasn't there doesn't mean we didn't need it so we needed to figure out a way to do it we couldn't say oh you need to come back to the network team in a year and maybe Amazon will have a solution for it right you need to do it now and it evolved later and maybe optimized for change the way you're doing things in the future but don't sit around and wait you can't I'd love to have you guys each individually answer this question for the live stream because it comes up a lot a lot of cloud architects out in the community what should they be thinking about the folks that are coming into this proactively and/or realizing the business benefits are there what advice would you guys give them an architecture what should be they be thinking about and what are some guiding principles you could share so I would start with looking at an architecture model that that can that can spread and and give consistency they're different to different cloud vendors that you will absolutely have to support cloud vendors tend to want to pull you into using their native toolset and that's good if only it was realistic to talk about only one cloud but because it doesn't it's it's it's super important to talk about and have a conversation with the business and with your technology teams about a consistent model so that's David yeah talking as we prepare about a day to operations so how do I design how do I do my day one work so that I'm not you know spending eighty percent of my time troubleshooting or managing my network because I'm doing that then I'm missing out on ways that I can make improvements or embrace new technologies so it's really important early on to figure out how do I make this as low maintenance as possible so that I can focus on the things that the team really should be focusing on Bobby your advice to the architect I don't know what else I can do that simplicity of operations is key right all right so the holistic view of j2 operation you mentioned let's could jump in day one is you're you're you're getting stuff set up day two is your life after all right this is kind of what you're getting at David so what does that look like what are you envisioning as you look at that 20 miles their outpost multi-cloud world what are some of the things then you want in a day to operations yeah infrastructure is code is really important to us so how do we how do we design it so that we can fit start making network changes and fitting them into like a release pipeline and start looking at it like that rather than somebody logging into a router seoi and troubleshooting things on in an ad hoc nature so moving more towards a DevOps model there's anything on that day - yeah I would love to add something so in terms of date to operations you can you can either sort of ignore the day - operations for a little while where you get well well you get your feet wet or you can start approaching it from the beginning the fact is that the the cloud native tools don't have a lot of maturity in that space and when you run into an issue you're gonna end up having a bad day going through millions and millions of logs just to try to understand what's going on so that's something that that the industry just now is beginning to to realize it's it's such as such a big gap I think that's key because for us we're moving to more of an event-driven operations in the past monitoring got the job done it's impossible to modern monitor something that it's nothing there when the event happens all right so the event-driven application and then detection is important yeah I think Gardner was all about the cloud native wave coming into networking that's gonna be a serious thing I want to get you guys perspectives I know you have different views of how you come into the journey and how you're executing and I always say the beauties in the eye of the beholder and that kind of applies how the network's laid out so Bobby you guys do a lot of high-performance encryption both on AWS and Azure that's kind of a unique thing for you how are you seeing that impact with multi cloud yeah and that's a new requirement for us to where we we have an equipment to encrypt and they they never get the question should i encryption and I'll encrypt the answer is always yes you should encrypt when you can encrypt for our perspective we we need to migrate a bunch of data from our data centers we have some huge data centers and then getting that data to the cloud is the timely experiencing some cases so we have been mandated that we have to encrypt everything leaving the data center so we're looking at using the aviatrix insane mode appliances to be able to encrypt you know 10 20 gigabits of data as it moves to the cloud itself David you're using terraform you got fire Ned you got a lot of complexity in your network what do you guys look at the future for your environment yeah so something exciting that or yeah now is fire net so for our security team they obviously have a lot of a lot of knowledge base around Palo Alto and with our commitments to our clients you know it's it's it's not very easy to shift your security model to a specific cloud vendor right so there's a lot of stuck to compliance or things like that where being able to take some of what you've you know you've worked on for years on Bram and put it in the cloud and have the same type of assurance that things are gonna work and be secure in the same way that they are on prem helps make that journey into the cloud a lot easier and Louis you guys got scripting you got a lot of things going on what's your what's your unique angle on this yeah no absolutely so full disclosure I'm not a not not an aviatrix customer yet it's ok wanna hear the truth that's good Ellis what are you thinking about what's on your mind no really when you when you talk about implementing the tool like this it's really just really important to talk about automation and focus on on value so when you talk about things like encryption and things like so yeah encrypting tunnels and encrypting the paths and those things are it should it should should be second nature really when you when you look at building those backends and managing them with your team it becomes really painful so tools like aviatrix that that add a lot of automation it's out of out of sight out of mind you can focus on the value and you don't have to focus on so I gotta ask you guys I'll see aviatrix is here they're their supplier to the sector but you guys are customers everyone's pitching you stuff these people are not gonna here to buy my stuff how do you guys have that conversation with the suppliers like the cloud vendors and other folks what's the what's it like we're API all the way you got to support this what are some of the what are some of your requirements how do you talk to and evaluate people that walk in and want to knock on your door and pitch you something what's the conversation like it's definitely it's definitely API driven we we definitely look at the at the PAP i structure of the vendors provide before we select anything that that is always first of mine and also what a problem are we really trying to solve usually people try to sell or try to give us something that isn't really valuable like implementing a solution on the on the on the cloud isn't really it doesn't really add a lot of value that's where we go David what's your conversation like with suppliers you have a certain new way to do things as as becomes more agile and essentially the networking and more dynamic what are some of the conversation is with the either incumbents or new new vendors that you're having what do what do you require yeah so ease of use is definitely definitely high up there we've had some vendors come in and say you know hey you know when you go to set this up we're gonna want to send somebody on-site and they're gonna sit with you for a day to configure it and that's kind of a red flag what wait a minute you know do we really if one of my really talented engineers can't figure it out on his own what's going on there and why is that so you know having having some ease-of-use and the team being comfortable with it and understanding it is really important probably how about you I mean the old days was do a bake-off and you know the winner takes all I mean is it like that anymore what's involving take off last year first you win so but that's different now because now you and you when you get the product you can install the product in AWS energy or have it up and running a matter of minutes and so key is is that it can you be operational you know within hours or days instead of weeks right but do we also have the flexibility to customize it to meet your needs could you want to be you want to be put into a box with the other customers we have needs that surpassed or cut their needs yeah I almost see the challenge of you guys are living where you've got the cloud immediate value depending on roll-up any solutions but then you have might have other needs so you've got to be careful not to buy into stuff that's not shipping so you're trying to be proactive at the same time deal with what you got I mean how do you guys see that evolving because multi-cloud to me is definitely relevant but it's not yet clear how to implement across how do you guys look at this baked versus you know future solutions coming how do you balance that so again so right now we we're we're taking the the ad hoc approach and and experimenting with the different concepts of cloud and really leveraging the the native constructs of each cloud but but there's it there's a breaking point for sure you don't you don't get to scale this I like like Seamon said and you have to focus on being able to deliver a developer they're their sandbox or their play area for the for the things that they're trying to build quickly and the only way to do that is with the with with some sort of consistent orchestration layer that allows you to so you've spent a lot more stuff to be coming pretty quickly IDEs area I do expect things to start to start maturing quite quite quickly this year and you guys see similar trend new stuff coming fast yeah you know part of the biggest challenge we've got now is being able to segment within the network being able to provide segmentation between production on production workloads even businesses because we support many businesses worldwide and and isolation between those is a key criteria there so the ability to identify and quickly isolate those workloads is key so the CIOs that are watching or that are saying hey take that he'll do multi cloud and then you know the bottoms up organization take pause you're kind of like off it's not how it works I mean what is the reality in terms of implementing you know in as fast as possible because the business benefits are clear but it's not always clear in the technology how to move that fast yeah what are some of the barriers what are the blockers what are the enablers I think the reality is is that you may not think your multi-cloud but your business is right so I think the biggest barriers there is understanding what the requirements are and how best to meet those requirements Inc and then secure manner because you need to make sure that things are working from a latency perspective that things work the way they did and get out of the mind shift that you know it was a cheery application in the data center it doesn't have to be a Tier three application in the cloud so lift and shift is is not the way to go scale is a big part of what I see is the competitive advantage to lot of these clouds and they used to be proprietary network stacks in the old days and then open systems came that was a good thing but as clouds become bigger there's kind of an inherent lock in there with the scale how do you guys keep the choice open how're you guys thinking about interoperability what are some of the conversations and you guys are having around those key concepts well when we look at when we look at the problem from a networking perspective it it's really key for you to just enable enable all the all the clouds to be to be able to communicate between them developers will will find a way to use the cloud that best suits their their business need and and like like you said it's whether whether you're in denial or not of the multi cloud fact that then your company is in already that's it becomes really important for you to move quickly yeah and a lot of it also hinges on how well is the provider embracing what that specific cloud is doing so are they are they swimming with Amazon or Azure and just helping facilitate things they're doing the you know the heavy lifting API work for you or are they swimming upstream and they're trying to hack it all together in a messy way and so that helps you you know stay out of the lock-in because they're you know if they're doing if they're using Amazon native tools to help you get where you need to be it's not like Amazon's gonna release something in the future that completely you know you have designed yourself into a corner so the closer they're more than cloud native they are the more the easier it is to to deploy but you also need to be aligned in such a way that you can take advantage of those cloud native technologies will they make sense tgw is a game changer in terms of cost and performance right so to completely ignore that would be wrong but you know if you needed to have encryption you know teach Adobe's not encrypted so you need to have some type of a gateway to do the VPN encryption you know so the aviatrix tool gives you the beauty of both worlds you can use tgw or the Gateway Wow real quick in the last minute we have I want to just get a quick feedback from you guys I hear a lot of people say to me hey the I picked the best cloud for the workload you got and then figure out multi cloud behind the scenes so that seems to be do you guys agree with that I mean is it do I go mole to one cloud across the whole company or this workload works great on AWS that work was great on this from a cloud standpoint you agree with that premise and then witness multi-cloud stitch them all together yeah from from an application perspective it it can be per workload but it can also be an economical decision certain enterprise contracts will will pull you in one direction to add value but the the network problem is still the same go away yeah yeah I mean you don't want to be trying to fit a square into a round Hall right so if it works better on that cloud provider then it's our job to make sure that that service is there and people can use it agree you just need to stay ahead of the game make sure that the then they're working for structure is there secure is available and is multi cloud capable yeah I'm at the end the day you guys just validating that it's the networking game now cloud storage compute check networking is where the action is awesome thanks for your insights guys appreciate you coming on the panel appreciate Thanks thank you [Applause] [Music] [Applause] okay welcome back on the live feed I'm John for its Dee Mulaney my co-host with aviatrix I'm with the cube for the special digital event our next customer panel got great another set of cloud network architects Justin Smith was aura Justin broadly with Ellie Mae and Amit Oh tree job with Koopa Pokemon stage [Applause] all right thank you thank you oK you've got all the cliff notes from the last session welcome rinse and repeat yeah yeah we're going to go under the hood a little bit I think I think they nailed the what we've been reporting and we've been having this conversation around networking is where the action is because that's the end of the day you got a move attack from A to B and you get work gloves exchanging data so it's really killer so let's get started Amit what are you seeing as the journey of multi cloud as you go under the hood and say okay I got to implement this I have to engineer the network make it enabling make it programmable make it interoperable across clouds I mean that's like I mean almost sounds impossible to me what's your taking yeah I mean it it seems impossible but if you are running an organization which is running infrastructure as a cordon all right it is easily doable like you can use tools out there that's available today you can use third-party products that can do a better job but but put your architecture first don't wait architecture may not be perfect put the best architecture that's available today and be agile to iterate and make improvements over the time we got to Justin's over here so I have to be careful when I point a question adjusting they both have to answer but okay journeys what's the journey been like I mean is there phases we heard that from Gardner people come into multi cloud and cloud native networking from different perspectives what's your take on the journey Justin yeah I mean from Mars like to we started out very much focused on one cloud and as we started doing Atkins we started doing new products the market the need for multi cloud comes very apparent very quickly for us and so you know having an architecture that we can plug in play into and be able to add and change things as it changes is super important for what we're doing in the space just in your journey yes for us we were very ad hoc oriented and the idea is that we were reinventing all the time trying to move into these new things and coming up with great new ideas and so rather than it being some iterative approach with our deployments that became a number of different deployments and so we shifted that tour and the network has been a real enabler of this is that it there's one network and it touches whatever cloud we want it to touch and it touches the data centers that we need it to touch and it touches the customers that we need it to touch our job is to make sure that the services that are available and one of those locations are available in all of the locations so the idea is not that we need to come up with this new solution every time it's that we're just iterating on what we've already decided to do before we get the architecture section I want to ask you guys a question I'm a big fan of you know let the app developers have infrastructure as code so check but having the right cloud run that workload I'm a big fan of that if it works great but we just heard from the other panel you can't change the network so I want to get your thoughts what is cloud native networking and is that the engine really got the enabler for this multi cloud trend but you guys taken we'll start with a mint what do you think about that yeah so you are gonna have workloads running in different clouds and the workloads would have affinity to one cloud over other but how you expose that it's matter of how you are going to build your networks how we are going to run security how we are going to do egress ingress out of it so it means the big problem how do you split says what's the solution what's the end the key pain points and problem statement I mean the key pain point for most companies is how do you take your traditional on-premise network and then blow that out to the cloud in a way that makes sense you know IP conflicts you have IP space you pub public eye peas and premise as well as in the cloud and how do you kind of make a sense of all of that and I think that's where tools like aviatrix make a lot of sense in that space from our site it's it's really simple it's a latency and bandwidth and availability these don't change whether we're talking about cloud or data center or even corporate IT networking so our job when when these all of these things are simplified into like s3 for instance and our developers want to use those we have to be able to deliver that and for a particular group or another group that wants to use just just GCP resources these aren't we have to support these requirements and these wants as opposed to saying hey that's not a good idea our job is to enable them not to disable them do you think I do you guys think infrastructure has code which I love that I think that's the future it is we saw that with DevOps but I just start getting the networking is it getting down to the network portion where it's network is code because stores and compute working really well is seeing all kubernetes and service master and network is code reality is that there is got work to do it's absolutely there I mean you mentioned net DevOps and it's it's very real I mean in Cooper we build our networks through terraform and on not only just out of fun build an API so that we can consistently build V nets and VPC all across in the same way three guys do it yeah and even security groups and then on top an aviatrix comes in we can peer the networks bridge bridge all the different regions through code same with you guys but yeah think about this everything we deploy is done with automation and then we also run things like lambda on top to make changes in real time we don't make manual changes on our network in the data center funny enough it's still manual but the cloud has enabled us to move into this automation mindset and and all my guys that's what they focus on is is bringing what now what they're doing in the cloud into the data center which is kind of opposite of what it should be that's full or what it used to be it's full DevOps then yes yeah I mean for us was similar on premise still somewhat very manual although we're moving more Norton ninja and terraform concepts but everything in the production environment is colored confirmation terraform code and now coming into the datacenter same I just wanted to jump in on a Justin Smith one of the comment that you made cuz it's something that we always talk about a lot is that the center of gravity of architecture used to be an on-prem and now it's shifted in the cloud and once you have your strategic architecture what you--what do you do you push that everywhere so what you used to see at the beginning of cloud was pushing the architecture on prem into cloud now i want to pick up on what you said to you others agree that the center of architect of gravity is here i'm now pushing what i do in the cloud back into on-prem and what and then so first that and then also in the journey where are you at from 0 to 100 of actually in the journey to cloud do you 50% there are you 10% are you vacuum datacenters next year I mean were you guys at yeah so there's there's two types of gravity that you typically are dealing with with no migration first is data gravity and your data set and where that data lives and then the second is the network platform that interrupts all that together in our case the data gravity sold mostly on Prem but our network is now extend out to the app tier that's gonna be in cloud right eventually that data gravity will also move to cloud as we start getting more sophisticated but you know in our journey we're about halfway there about halfway through the process we're taking a handle of lift and shift and when did that start and we started about three years ago okay okay cool bye it's a very different story it started from a garage and 100% on the clock it's a business spend management platform as a software as a service 100% on the cloud it was like 10 years ago right yes yeah you guys are riding the wave love that architecture Justin I want to ask you is or you guys mentioned DevOps I mean honestly we saw the huge observability wave which is essentially network management for the cloud in my opinion right yeah it's more dynamic but this is about visibility we heard from the last panel you don't know what's being turned on or turned off from a services standpoint at any given time how is all this playing out when you start getting into the DevOps down well this this is the big challenge for all of us as visibility when you talk transport within a cloud you know we very interesting we have moved from having a backbone that we bought that we owned that would be data center connectivity we now I work for as or as a subscription billing company so we want to support the subscription mindset so rather than going and buying circuits and having to wait three months to install and then coming up with some way to get things connected and resiliency and redundancy I my backbone is in the cloud I use the cloud providers interconnections between regions to transport data across and and so if you do that with their native solutions you you do lose visibility there there are areas in that that you don't get which is why controlling you know controllers and having some type of management plane is a requirement for us to do what we're supposed to do and provide consistency while doing it a great conversation I loved when you said earlier latency bandwidth I think availability with your sim pop3 things guys SLA I mean you just do ping times between clouds it's like you don't know what you're getting for round-trip times this becomes a huge kind of risk management black hole whatever you want to call blind spot how are you guys looking at the interconnects between clouds because you know I can see that working from you know ground to cloud I'm per cloud but when you start doing with multi clouds workloads SLA is will be all of the map won't they just inherently but how do you guys view that yeah I think we talked about workload and we know that the workloads are going to be different in different clouds but they are going to be calling each other so it's very important to have that visibility that you can see how data is flowing at what latency and what our ability is hour is there and our authority needs to operate on that so it's solely use the software dashboard look at the times and look at the latency in the old day is strong so on open so on you try to figure it out and then your day is you have to figure out just what's your answer to that because you're in the middle of it yeah I mean I think the key thing there is that we have to plan for that failure we have to plan for that latency in our applications that's starting start tracking your SLI something you start planning for and you loosely couple these services and a much more micro services approach so you actually can handle that kind of failure or that type of unknown latency and unfortunately the cloud has made us much better at handling exceptions a much better way you guys are all great examples of cloud native from day one and you guys had when did you have the tipping point moment or the Epiphany of saying a multi clouds real I can't ignore it I got to factor it into all my design design principles and and everything you're doing what's it was there a moment over that was it from day one now there are two divisions one was the business so in business there was some affinity to not be in one cloud or to be in one cloud and that drove from the business side so as a cloud architect our responsibility was to support that business and other is the technology some things are really running better in like if you are running dot network load or you are going to run machine learning or AI so that you have you would have that reference of one cloud over other so it was the bill that we got from AWS I mean that's that's what drives a lot of these conversations is the financial viability of what you're building on top of it which is so we this failure domain idea which is which is fairly interesting how do I solve our guarantee against a failure domain you have methodologies with you know back-end direct connects or interconnect with GCP all of these ideas are something that you have to take into account but that transport layer should not matter to whoever we're building this for our job is to deliver the frames in the packets what that flows across how you get there we want to make that seamless and so whether it's a public Internet API call or it's a back-end connectivity through Direct Connect it doesn't matter it just has to meet a contract that you signed with your application folks yeah that's the availability piece just on your thoughts on that I think any comment on that so actually multi clouds become something much more recent in the last six to eight months I'd say we always kind of had a very much an attitude of like moving to Amazon from our private cloud is hard enough why complicate it further but the realities of the business and as we start seeing you know improvements in Google and Asia and different technology spaces the need for multi cloud becomes much more important as well as our acquisition strategies I matured we're seeing that companies that used to be on premise that we typically acquire are now very much already on a cloud and if they're on a cloud I need to plug them into our ecosystem and so that's really change our multi cloud story in a big way I'd love to get your thoughts on the clouds versus the clouds because you know you compare them Amazon's got more features they're rich with features I see the bills are hiking people using them but Google's got a great network he googles networks pretty damn good and then you got Asher what's the difference between the clouds who where they evolve something where they peak in certain areas better than others what what are the characteristics which makes one cloud better do they have a unique feature that makes as you're better than Google and vice versa what do you guys think about the different clouds yeah to my experience I think there is the approach is different in many places Google has a different approach very DevOps friendly and you can run your workload like the your network can span regions time I mean but our application ready to accept that MS one is evolving I mean I remember 10 years back Amazon's Network was a flat network we will be launching servers and 10.0.0.0 so so the VP sees concept came out multi-account came out so they are evolving as you are at a late start but because they have a late start they saw the pattern and they they have some mature set up on the I mean I think they're all trying to say they're equal in their own ways I think they all have very specific design philosophies that allow them to be successful in different ways and you have to kind of keep that in mind as you architect your own solution for example Amazon has a very much a very regional affinity they don't like to go cross region in their architecture whereas Google is very much it's a global network we're gonna think about as a global solution I think Google also has a banjo it's third to market and so it has seen what a sure did wrong it's seen what AWS did wrong and it's made those improvements and I think that's one of their big advantage at great scale to Justin thoughts on the cloud so yeah Amazon built from the system up and Google built from the network down so their ideas and approaches are from a global versus or regional I agree with you completely that that is the big number one thing but the if you look at it from the outset interestingly the the inability or the ability for Amazon to limit layer two broadcasting and and what that really means from a VPC perspective changed all the routing protocols you can use all the things that we have built inside of a data center to provide resiliency and and and make things seamless to users all of that disappeared and so because we had to accept that at the VPC level now we have to accept it at the LAN level Google's done a better job of being able to overcome those things and provide those traditional network facilities to us just great panel can go all day here's awesome so I heard we could we'll get to the cloud native naive questions so kind of think about what's not even what's cloud is that next but I got to ask you had a conversation with a friend he's like Wayne is the new land so if you think about what the land was at a datacenter when is the new link you get talking about the cloud impact so that means st when the old st winds kind of changing into the new land how do you guys look at that because if you think about it what lands were for inside a premises was all about networking high speed but now when you take a win and make the essentially a land do you agree with that and how do you view this trend and is it good or bad or is it ugly and what's what you guys take on this yeah i think it's a it's a thing that you have to work with your application architect so if you are managing networks and if you're a sorry engineer you need to work with them to expose the unreliability that would bring in so the application has to hand a lot of this the difference in the latencies and and the reliability has to be worked through the application there land when same concept as that BS I think we've been talking about for a long time the erosion of the edge and so is this is just a continuation of that journey we've been on for the last several years as we get more and more cloud native and we start about API is the ability to lock my data in place and not be able to access it really goes away and so I think this is just continuation that thing I think it has challenges we start talking about weighing scale versus land scale the tooling doesn't work the same the scale of that tooling is much larger and the need to automation is much much higher in a way and than it was in a land that's what you're seeing so much infrastructure as code yeah yeah so for me I'll go back again to this its bandwidth and its latency right that that define those two land versus when but the other thing that comes up more and more with cloud deployments is where is our security boundary and where can I extend this secure aware appliance or set of rules to protect what's inside of it so for us we're able to deliver VRS or route forwarding tables for different segments wherever we're at in the world and so they're they're trusted to talk to each other but if they're gonna go to someplace that's outside of their their network then they have to cross a security boundary and where we enforce policy very heavily so for me there's it's not just land when it's it's how does environment get to environment more importantly that's a great point and security we haven't talked to yet but that's got to be baked in from the beginning that's architecture thoughts on security are you guys are dealing with it yeah start from the base have app to app security built-in have TLS have encryption on the data a transit data at rest but as you bring the application to the cloud and they are going to go multi-cloud talking to over the Internet in some places well have apt web security I mean I mean our principals day security is day zero every day and so we we always build it into our design we want our architecture into our applications its encrypt everything its TLS everywhere it's make sure that that data is secured at all times yeah one of the cool trends at RSA just as a side note was the data in use encryption piece which is a homomorphic stuff was interesting all right guys final question you know we heard on the earlier panel was also trending at reinvent we take the tea out of cloud native it spells cloud naive okay they got shirts now aviatrix kind of got this trend going what does that mean to be naive so if you're to your peers out there watching a live stream and also the suppliers that are trying to supply you guys with technology and services what's naive look like and what's native look like when is someone naive about implementing all this stuff so for me it's because we are in hundred-percent cloud for us it's main thing is ready for the change and you will you will find new building blocks coming in and the network design will evolve and change so don't be naive insane that it's static you wall with the change I think the big naivety that people have is that well I've been doing it this way for 20 years and been successful it's going to be successful in cloud the reality is that's not the case you have to think some of the stuff a little bit differently and you need to think about it early enough so that you can become cloud native and really enable your business on cloud yeah for me it's it's being open minded right the the our industry the network industry as a whole has been very much I am smarter than everybody else and we're gonna tell everybody how it's going to be done and we had we fell into a lull when it came to producing infrastructure and and and so embracing this idea that we can deploy a new solution or a new environment in minutes as opposed to hours or weeks or four months in some cases is really important and and so you know it's not me being closed-minded native being open minded exactly and and it took a for me it was that was a transformative kind of where I was looking to solve problems in a cloud way as opposed to looking to solve problems in this traditional old-school way all right I know we're out of time but I ask one more question so you guys so good it could be a quick answer what's the BS language when you the BS meter goes off when people talk to you about solutions what's the kind of jargon that you hear that's the BS meter going off what are people talking about that in your opinion you here you go that's total B yes but what triggers use it so that I have two lines out of movies that are really I can if I say them without actually thinking them it's like 1.21 jigowatts are you out of your mind from Back to the Future right somebody's giving you all these and then and then Martin Mull and and Michael Keaton and mr. mom when he goes to 22 21 whatever it takes yeah those two right there if those go off in my mind somebody's talking to me I know they're full of baloney so a lot of speech would be a lot of speeds and feeds a lot of data did it instead of talking about what you're actually doing and solutioning for you're talking about well I does this this this and any time I start seeing the cloud vendor start benchmarking against each other it's your workload is your workload you need a benchmark yourself don't don't listen to the marketing on that that's that's all what triggers you and the bsp I think if somebody explains you and not simple they cannot explain you in simplicity then that's good all right guys thanks for the great insight great pen how about a round of applause DX easy solutions integrating company that we service customers from all industry verticals and we're helping them to move to the digital world so as a solutions integrator we interface with many many customers that have many different types of needs and they're on their IT journey to modernize their applications into the cloud so we encounter many different scenarios many different reasons for those migrations all of them seeking to optimize their IT solutions to better enable their business we have our CPS organization it's cloud platform services we support AWS does your Google Alibaba porco will help move those workloads to wherever it's most appropriate no one buys the house for the plumbing equally no one buys the solution for the networking but if the plumbing doesn't work no one likes the house and if this network doesn't work no one likes a solution so network is ubiquitous it is a key component of every solution we do the network connectivity is the lifeblood of any architecture without network connectivity nothing works properly planning and building a scalable robust network that's gonna be able to adapt with the application needs its critical when encountering some network design and talking about speed the deployment aviatrix came up in discussion and we then further pursued an area DHT products that incorporated aviatrix is part of a new offering that we are in the process of developing that really enhances our ability to provide cloud connectivity for the lance cloud connectivity there's a new line of networking services that we're getting into as our clients moving the hybrid cloud networking it is much different than our traditional based services an aviatrix provides a key component in that service before we found aviatrix we were using just native peering connections but there wasn't a way to visualize all those peering connections and with multiple accounts multiple contacts for security with a v8 church we were able to visualize those different peering connections of security groups it helped a lot especially in areas of early deployment scenarios were quickly able to then take those deployment scenarios and turn them into scripts that we can then deploy repeatedly their solutions were designed for work with the cloud native capabilities first and where those cloud native capabilities fall short they then have solution sets that augment those capabilities I was pleasantly surprised number one with the aviatrix team as a whole in their level of engagement with us you know we weren't only buying the product we were buying a team that came on board to help us implement and solution that was really good to work together to learn both what aviatrix had to offer as well as enhancements that we had to bring that aviatrix was able to put into their product and meet our needs even better aviatrix was a joy to find because they really provided us the technology that we needed in order to provide multi cloud connectivity that really added to the functionality that you can't get from the basically providing services we're taking our customers on a journey to simplify and optimize their IT infrastructure baby Atrix certainly has made my job much easier okay welcome back to altitude 2020 for the digital event for the live feed welcome back I'm John fray with the cube with Steve Mulaney CEO aviatrix for the next panel from global system integrators the folks who are building and working with folks on their journey to multi cloud and cloud native networking we've got a great panel George Buckman with dxc and Derek Monahan with wwt welcome to the stage [Applause] [Music] okay you guys are the ones out there advising building and getting down and dirty with multi cloud and cloud native network and we start from the customer panel you can see the diversity of where people come into the journey of cloud it kind of depends upon where you are but the trends are all clear cloud native networking DevOps up and down the stack this has been the main engine what's your guys take of the disk Jerry to multi cloud what do you guys seeing yep yeah it's it's critical I mean we're seeing all of our enterprise customers enter into this they've been through the migrations of the easy stuff you know now they're trying to optimize and get more improvement so now the tough stuffs coming on right and you know they need their data processing near where their data is so that's driving them to a multi cloud environment okay we heard some of the edge stuff I mean you guys are you've seen this movie before but now it's a whole new ballgame what's your take yeah so I'll give you a hint so our practice it's not called the cloud practice it's the multi cloud practice and so if that gives you a hint of how we approach things it's very consultative and so when we look at what the trends are let's look a little year ago about a year ago we were having conversations with customers let's build a data center in the cloud let's put some VP C's let's throw some firewalls with some DNS and other infrastructure out there and let's hope it works this isn't a science project so what we're trying we're starting to see is customers are starting to have more of a vision and we're helping with that consultative nature but it's totally based on the business and you got to start understanding how the lines of business are using the apps and then we evolved into that next journey which is a foundational approach to what are some of the problem statements customers are solving when they come to you what are the top things that are on their my house or the ease of use of Julie all that stuff but what specifically they did digging into yeah some complexity I think when you look at a multi cloud approach in my view is network requirements are complex you know I think they are but I think the approach can be let's simplify that so one thing that we try to do this is how we talk to customers is let's just like you simplify an aviatrix simplifies the automation orchestration of cloud networking we're trying to simplify the design the planning implementation of infrastructure across multiple workloads across multiple platforms and so the way we do it is we sit down we look at not just use cases and not just the questions in common we anticipate we actually build out based on the business and function requirements we build out a strategy and then create a set of documents and guess what we actually build in the lab and that lab that we platform we built proves out this reference architecture actually works absolutely we implement similar concepts I mean we they're proven practices they work great so well George you mentioned that the hard parts now upon us are you referring to networking what is specifically were you getting at Tara says the easy parts done that so for the enterprises themselves migrating their more critical apps or more difficult apps into the environments you know they've just we've just scratched the surface I believe on what enterprises that are doing to move into the cloud to optimize their environments to take advantage of the scale and speed to deployment and to be able to better enable their businesses so they're just now really starting the >> so do you get you guys see what I talked about them in terms of their Cambrian explosion I mean you're both monster system integrators with you know top fortune enterprise customers you know really rely on you for for guidance and consulting and so forth and boy they're networks is that something that you you've seen I mean - does that resonate did you notice a year and a half ago and all of a sudden the importance of cloud for enterprise shoot up yeah I mean we're seeing it okay in our internal environment as you know we're a huge company or as customers are in 30 so we're experiencing that internal okay and every one of our other customers so I I have another question oh but I don't know the answer to this and the lawyer never asks a question that you don't know the answer to but I'm gonna ask it anyway DX c @ w WT massive system integrators why aviatrix yep so great question Steve so I think the way we approach things I think we have a similar vision a similar strategy how you approach things how we approach things that world by technology number one we want to simplify the complexity and so that's your number one priorities let's take the networking but simplify it and I think part of the other point I'm making is we have we see this automation piece as not just an afterthought anymore if you look at what customers care about visibility and automation is probably the at the top three maybe the third on the list and I think that's where we see the value and I think the partnership that we're building and what I what I get excited about is not just putting yours in our lab and showing customers how it works is Co developing a solution with you figuring out hey how can we make this better Bank visibily is a huge thing jump in security alone network everything's around visibility what automation you see happening in terms of progression order of operations if you will it's the low-hanging fruit what are people working on now and what are what are some of the aspirational goals around when you start thinking about multi cloud an automation yep so I wanted to get back to answer that question I want to answer your question you know what led us there and why aviatrix you know in working some large internal IT projects and and looking at how we were going to integrate those solutions you know we like to build everything with recipes where network is probably playing catch-up in the DevOps world but with a DevOps mindset looking to speed to deploy support all those things so when you start building your recipes you take a little of this a little of that and you mix it all together well when you look around you say wow look there's this big bag of athe let me plop that in that solves a big part of my problems that I have to speed to integrate speed to deploy and the operational views that I need to run this so that was 11 years about reference architectures yeah absolutely so you know they came with a full slate of reference architectures already the out there and ready to go that fit our needs so it's very very easy for us to integrate those into our recipes what do you guys think about all the multi vendor interoperability conversations that have been going on choice has been a big part of multi cloud in terms of you know customers want choice didn't you know they'll put a workload in the cloud that works but this notion of choice and interoperability is become a big conversation it is and I think our approach and that's why we talk to customers is let's let's speed and D risk of that decision making process and how do we do that because the interoperability is key you're not just putting it's not just a single vendor we're talking you know many many vendors I mean think about the average number of cloud application as a customer uses a business and enterprise business today you know it's it's above 30 it's it's skyrocketing and so what we do and we look at it from an Billee approach is how do things interoperate we test it out we validate it we build a reference architecture says these are the critical design elements now let's build one with aviatrix and show how this works with aviatrix and I think the the important part there though is the automation piece that we add to it invisibility so I think the visibility is what's what I see lack in cross industry today and the cloud needed that's been a big topic okay in terms of aviatrix as you guys see them coming in there one of the ones that are emerging and the new brands emerging with multi cloud you still got the old guard incumbent with huge footprints how our customers dealing with that that kind of component and dealing with both of them yeah I mean where we have customers that are ingrained with a particular vendor and you know we have partnerships with many vendors so our objective is to provide the solution that meets that client and you they all want multi vendor they all want interoperability correct all right so I got to ask you guys a question what we were defining day to operations what does that mean I mean you guys are looking at the big business and technical components of architecture what does day to Operations mean what's the definition of that yeah so I think from our perspective my experience we you know day to operations whether it's it's not just the you know the orchestration piece and setting up and let it a lot of automate and have some you know change control you're looking at this from a data perspective how do I support this ongoing and make it easy to make changes as we evolve that the the cloud is very dynamic the the nature of how the fast is expanding the number of features is astonishing trying to keep up to date with a number of just networking capabilities and services that are added so I think day to operation starts with a fundable understanding of you know building out supporting a customer's environments and making it the automation piece easy from from you know a distance I think yeah and you know taking that to the next level of being able to enable customers to have catalog items that they can pick and choose hey I need this network connectivity from this cloud location back to this on pram and being able to have that automated and provisioned just simply by ordering it for the folks watching out there guys take a minute to explain as you guys are in the trenches doing a lot of good work what are some of the engagement that you guys get into how does that progress what is the what's what happens there they call you up and say hey I need multi-cloud or you're already in there I mean take us through why how someone can engage to use a global si to come in and make this thing happen what's typical engagement look like yeah so from our perspective we typically have a series of workshops in a methodology that we kind of go along the journey number one we have a foundational approach and I don't mean foundation meaning the network foundation that's a very critical element we got a factor in security we've got to factor in automation so we think about foundation we do a workshop that starts with education a lot of times we'll go in and we'll just educate the customer what does VPC sharing you know what is a private link and asher how does that impact your business you know customers I want to share services out in an ecosystem with other customers and partners well there's many ways to accomplish that so our goal is to you know understand those requirements and then build that strategy with them thoughts Georgia yeah I mean I'm one of the guys that's down in the weeds making things happen so I'm not the guy on the front line interfacing with the customers every day but we have a similar approach you know we have a consulting practice that will go out and and apply their practices to see what those and when do you parachute in yeah and when I've been is I'm on the back end working with our offering development leads for the networking so we understand or seeing what customers are asking for and we're on the back end developing the solutions that integrate with our own offerings as well as enable other customers to just deploy quickly to meet their connectivity needs it so the patterns are similar right final question for you guys I want to ask you to paint a picture of what success looks like and you know the name customers didn't again reveal kind of who they are but what does success look like in multi-cloud as you as you paint a picture for the folks here and watching on the live stream it's someone says hey I want to be multi-cloud I got to have my operations agile I want full DevOps I want programmability security built in from day zero what does success look like yeah I think success looks like this so when you're building out a network the network is a harder thing to change than some other aspects of cloud so what we think is even if you're thinking about that second cloud which we have most of our customers are on to public clouds today they might be dabbling in is you build that network foundation at architecture that takes in consideration where you're going and so once we start building that reference architecture out that shows this is how to sit from a multi-cloud perspective not a single cloud and let's not forget our branches let's not forget our data centers let's not forget how all this connects together because that's how we define multi-cloud it's not just in the cloud it's on Prem and it's off Prem and so collectively I think the key is also is that we provide them an hld you got to start with a high level design that can be tweaked as you go through the journey but you got to give a solid structural foundation and that networking which we think most customers think as not not the network engineers but as an afterthought we want to make that the most critical element before you start the journey Jorge from your seed how do you success look for you so you know it starts out on these journeys often start out people not even thinking about what is gonna happen with what their network needs are when they start their migration journey to the cloud so I want this success to me looks like them being able to end up not worrying about what's happening in the network when they move to the cloud good guys great insight thanks for coming on share and pen I've got a round of applause the global system integrators [Applause] [Music] okay welcome back from the live feed I'm chef for with the q Steve Valenti CEO of aviatrix my co-host our next panel is the aviatrix certified engineer is also known as aces this is the folks that are certified their engineering they're building these new solutions please welcome Toby Foss from informatica Stacy linear from Teradata and Jennifer Reed with Victor Davis to the stage I was just gonna I was just gonna rip you guys see where's your jackets and Jen's got the jacket on okay good love the aviatrix aces pile of gear they're above the clouds story to new heights that's right so guys aviatrix aces love the name I think it's great certified this is all about getting things engineered so there's a level of certification I want to get into that but first take us through the day in the life of an ace and just to point out Stacey's a squad leader so he's like it Squadron Leader Roger and leader yeah Squadron Leader he's got a bunch of aces underneath him but share your perspective day-in-the-life Jennifer we'll start with you sure so I have actually a whole team that works for me both in the in the North America both in the US and in Mexico and so I'm really working to get them certified as well so I can become a squad leader myself but it's important because one of the the critical gaps that we've found is people having the networking background because they're you graduate from college and you have a lot of computer science background you can program you've got Python but networking in packets they just don't get and so just taking them through all the processes that it's really necessary to understand when you're troubleshooting is really critical mm-hm and because you're gonna get an issue where you need to figure out where exactly is that happening on the network you know is my my issue just in the V PC is and on the instant side is a security group or is it going on print and is this something actually embedded within Amazon itself I mean I should troubleshot an issue for about six months going back and forth with Amazon and it was the vgw VPN because they were auto-scaling on two sides and we ended up having to pull out the Cisco's and put in aviatrix so I could just say okay it's fixed and actually actually helped the application teams get to that and get it solved yeah but I'm taking a lot of junior people and getting them through that certification process so they can understand and see the network the way I see the network I mean look I've been doing this for 25 years when I got out when I went in the Marine Corps that's what I did and coming out the network is still the network but people don't get the same training they get they got in the 90s it's just so easy just write some software they work takes care of itself yes he'll be will good I'll come back to that I want to come back to that problem solve with Amazon but Toby I think the only thing I have to add to that is that it's always the network fault as long as I've been in never I've always been the network's fault and I'm even to this day you know it's still the network's fault and part of being a network guy is that you need to prove when it is and when it's not your fault and that means you need to know a little bit about a hundred different things to make that and now you've got a full stack DevOps you got to know a lot more times another 100 and these times are changing yeah they say you're Squadron Leader I get that right what is what is the squadron leader first can you describe what it is I think probably just leading all the network components of it but not they from my perspective when to think about what you ask them was it's about no issues and the escalation soft my day is a good outcome that's a good day it's a good day again every mission the Amazon this brings up a good point you know when you have these new waves come in you have a lot of new things new we use cases a lot of the finger-pointing it's that guys problem that girls problem so what how do you solve that and how do you get the young guns up to speed is there training is that this is where the certification comes in was where the certification is really going to come in I know when we we got together at reinvent one of the the questions that that we had with Steve and the team was what what should our certification look like you know she would just be teaching about what aviatrix troubleshooting brings to bear like what should that be like and I think Toby and I were like no no no that's going a little too high we need to get really low because the the better someone can get at actually understanding what actually happening in the network and and where to actually troubleshoot the problem how to step back each of those processes because without that it's just a big black box and they don't know you know because everything is abstracted in Amazon Internet and Azure and Google is substracted and they have these virtual gateways they have VPNs that you just don't have the logs on it's you just don't know and so then what tools can you put in front of them of where they can look because there are four logs well as long as they turned on the flow logs when they built it you know and there's like each one of those little things that well if they'd had decided to do that when they built it it's there but if you can come in later to really supplement that with training to actual troubleshoot and do a packet capture here as it's going through then teaching them how to read that even yeah Toby we were talking before he came on up on stage about your career you've been networking all your time and then you know you're now mentoring a lot of younger people how is that going because the people who come in fresh they don't have all the old war stories they don't know you talk about yeah that's never fault I walk in Mayr feet in the snow when I was your age I mean it's so easy now right they say what's your take on how you train the young piece so I've noticed two things one is that they are up to speed a lot faster in generalities of networking they can tell you what a network is in high school level now where I didn't learn that too midway through my career and they're learning it faster but they don't necessarily understand why it's that way here you know everybody thinks that it's always slash 24 for a subnet and they don't understand why you can break it down smaller why it's really necessary so the the ramp up speed is much faster for these guys that are coming in but they don't understand why and they need some of that background knowledge to see where it's coming from and why is it important and old guys that's where we thrive Jennifer you mentioned you got in from the Marines health spa when you got into networking how what was it like then and compare it now most like we've heard earlier static versus dynamic don't be static because back then you just said the network you got a perimeter yeah I know there was no such thing yeah no so back in the day I mean I mean we had banyan vines for email and you know we had token ring and I had to set up token ring networks and figure out why that didn't work because how many of things were actually sharing it but then actually just cutting fiber and running fiber cables and dropping them over you know shelters to plug them in and oh crap they swung it too hard and shattered it and how I gotta be great polished this thing and actually shoot like to see if it works I mean that was the network current five cat 5 cables to run an Ethernet you know and then from that just said network switches dumb switches like those were the most common ones you had then actually configuring routers and you know logging into a Cisco router and actually knowing how to configure that and it was funny because I had gone all the way up and was a software product manager for a while so I've gone all the way up the stack and then two and a half three years ago I came across to to work with entity group that became Victor Davis but we went to help one of our customers Avis and it was like okay so we need to fix the network okay I haven't done this in 20 years but all right let's get to it you know because it really fundamentally does not change it's still the network I mean I've had people tell me well you know when we go to containers we will not have to worry about the network and I'm like yeah you don't I do and then with this with and programmability is it really interesting so I think this brings up the certification what are some of the new things that people should be aware of that come in with the aviatrix ace certification what are some of the highlights can you guys share some of the some of the highlights around the certifications I think some of the importance is that it's it doesn't need to be vendor specific for network generality or basic networking knowledge and instead of learning how Cisco does something or how Palo Alto does something we need to understand how and why it works as a basic model and then understand how each vendor has gone about that problem and solved it in a general that's true in multi cloud as well you can't learn how cloud networking works without understanding how AWS integer and GCP are all slightly the same but slightly different and some things work and some things don't I think that's probably the number one take I think having a certification across clouds is really valuable because we heard the global s eyes cover the business issues what does it mean to do that is it code is that networking is the configuration is that aviatrix what is the I mean obviate races the ACE certifications but what is it about the multi cloud that makes it multi networking and multi vendor easy answer is yes so you got to be a general let's go to your hands and all you have to be it takes experience because it's every every cloud vendor has their own certification whether that is ops and [Music] advanced networking and advanced security or whatever it might be yeah they can take the test but they have no idea how to figure out what's wrong with that system and the same thing with any certification but it's really getting your hands in there and actually having to troubleshoot the problems you know actually work the problem you know and calm down it's going to be okay I mean because I don't know how many calls I've been on or even had aviatrix join me on it's like okay so everyone calm down let's figure out what's happening it's like we've looked at that screen three times looking at it again it's not gonna solve that problem right but at the same time you know remaining calm but knowing that it really is I'm getting a packet from here to go over here it's not working so what could be the problem you know and actually stepping them through those scenarios but that's like you only get that by having to do it you know and seeing it and going through it and then I have a question so we you know I just see it we started this program maybe six ago we're seeing a huge amount of interest I mean we're oversubscribed on all the training sessions we've got people flying from around the country even with coronavirus flying to go to Seattle to go to these events were oversubscribed good is that watching leader would put there yeah is that something that you see in your organization's are you recommending that to people do you see I mean I'm just I guess I'm surprised I'm not surprised but I'm really surprised by the demand if you would of this multi-cloud network certification because it really isn't anything like that is that something you guys can comment on or do you see the same things in your organization's I see from my side because we operate in the multi cloud environment so it really helps and it's beneficial for us yeah I think I would add that uh networking guys have always needed to use certifications to prove that they know what they know right it's not good enough to say yeah I know IP addresses or I know how a network works and a couple little check marks or a little letters by your name helps give you validity um so even in our team we can say hey you know we're using these certifications to know that you know enough of the basics and enough of the understandings that you have the tools necessary right so I guess my final question for you guys is why an eighth certification is relevant and then second part is share with the livestream folks who aren't yet a certified or might want to jump in to be AVH or certified engineers why is it important so why is it relevant and why should someone want to be an ace-certified I'm used to write engineer I think my view is a little different I think certification comes from proving that you have the knowledge not proving that you get a certification to get know I mean they're backwards so when you've got the training in the understanding and the you use that to prove and you can like grow your certification list with it versus studying for a test to get a certification and have no understanding of ok so that who is the right person that look at this is saying I'm qualified is it a network engineer is it a DevOps person what's your view you know is it a certain you know I think cloud is really the answer it's the as we talked like the edge is getting eroded so is the network initially eating eroded we're getting more and more of some network some DevOps some security lots and lots of security because network is so involved in so many of them that it's just the next progression I would say I expand that to more automation engineers because we have those nails probably extended as well well I think that the training classes themselves are helpful especially the entry-level ones for people who may be quote-unquote cloud architects but have never done anything and networking for them to understand why we need those things to really work whether or not they go through to eventually get a certification is something different but I really think fundamentally understanding how these things work it makes them a better architect makes some better application developer but even more so as you deploy more of your applications into the cloud really getting an understanding even from our people who have tradition down on Prem networking they can understand how that's going to work in the cloud - well I know we've got just under 30 seconds left but I want to get one more question and just one more for the folks watching that are you maybe younger that don't have that networking training from your experiences each of you can answer why is it should they know about networking what's the benefit what's in it for them motivate them share some insights and why they should go a little bit deeper in networking Stacy we'll start with you we'll go down let's say it's probably fundamental right if you want to deliver solutions networking use the very top I would say if you fundamental of an operating system running on a machine how those machines talk together as a fundamental change is something that starts from the base and work your way up right well I think it's a challenge because you you've come from top-down now you're gonna start looking from bottom-up and you want those different systems to cross communicate and say you built something and you're overlapping IP space not that that doesn't happen but how can I actually make that still operate without having to reappear e-platform it's like those challenges like those younger developers or sis engineers can really start to get their hands around and understand those complexities and bring that forward in their career they got to know the pilot pipes are working and some plumbing that's right works at how to code it that's right awesome thank you guys for great insights ace certain babies you're certified engineers also known as aces give a round of applause thank you okay all right that concludes my portion thank you Steve thanks for have Don thank you very much that was fantastic everybody round of applause for John for you yeah so great event great event I'm not going to take long we've got we've got lunch outside for that for the people here just a couple of things just call to action right so we saw the Aces you know for those of you out on the stream here become a certified right it's great for your career it's great for not knowledge is is fantastic it's not just an aviatrix thing it's gonna teach you about cloud networking multi-cloud networking with a little bit of aviatrix exactly what the cisco CCIE program was for IP network that type of the thing that's number one second thing is is is is learn right so so there's a there's a link up there for the four to join the community again like I started this this is a community this is the kickoff to this community and it's a movement so go to what a v8 community a bh6 comm was starting a community at multi cloud so you know get get trained learn I'd say the next thing is we're doing over a hundred seminars in across the United States and also starting into Europe soon will come out and will actually spend a couple hours and talk about architecture and talk about those beginning things for those of you on the you know on the livestream in here as well you know we're coming to a city near you go to one of those events it's a great way to network with other people that are in the industry as well as start to learn and get on that multi-cloud journey and then I'd say the last thing is you know we haven't talked a lot about what aviatrix does here and that's intentional we want you you know leaving with wanting to know more and schedule get with us in schedule a multi our architecture workshop session so we we sit out with customers and we talk about where they're at in that journey and more important where they're going and to find that end state architecture from networking compute storage everything and everything you heard today every panel kept talking about architecture talking about operations those are the types of things that we saw we help you cook define that canonical architecture that system architecture that's yours so for so many of our customers they have three by five plotted lucid charts architecture drawings and it's the customer name slash aviatrix arc network architecture and they put it on their whiteboard that's what what we and that's the most valuable thing they get from us so this becomes their 20-year network architecture drawing that they don't do anything without talking to us and look at that architecture that's what we do in these multi hour workshop sessions with customers and that's super super powerful so if you're interested definitely call us and let's schedule that with our team so anyway I just want to thank everybody on the livestream thank everybody here hopefully it was it was very useful I think it was and joined the movement and for those of you here join us for lunch and thank you very much [Applause] [Music] [Applause] [Music] you

>> Narrator: From New York City, it's theCUBE, covering New Relic FutureStack 2019, brought to you by New Relic. >> Hi, I'm Stu Miniman and this is theCUBE at New Relic FutureStack 2019 here in New York City. It's our first year of the event, but the event itself has been around for seven years and to help us end our coverage, no better person than the founder and CEO of New Relic, and the one who the name of the company came from, Lew Cirne. Of course, Lew Cirne is an anagram for New Relic. >> Indeed it is. >> Lew, thank you so much for having theCUBE at the event here and thanks for hosting us. >> I'm a huge fan of theCUBE. I've been watching it for a long time and it's such a pleasure to have you guys here. Thank you for coming. >> All right, so Lew, you're known as the coding CEO >> Lew: I am. >> And you come out with a vision of making software better. It's a great goal. Give us a little bit about the state of the industry. You know the internet challenge these days. It's going to fragment into a bunch of pieces and Open Source isn't what it used to be. There's so many changes going in the industry. Just kind of macro view before we get into New Relic. >> Yeah, from a macro view at New Relic we do this for the love of software. It's not just me, it's the whole company. We believe in software. We think it unquestionably is changing the world, transforming every industry. It's not enough just to build software that's great. You have to deliver more perfect software. That's now become almost obvious whereas when we first started out that was actually a bit of an evangelical sale where we had to convince people that they needed to observe their software. Now it's become a must-do thing, and that's why observability has become a household term. Everybody recognizes that anything that runs in production in internet scale needs to be observed, needs to be measured in real time. And so, that's been going on and has become a must-do thing for our customers. What we're so excited about is that we're delivering the first observability platform. What do we mean by that? Well, we see with this proliferation of tools, you might have metrics going to one place and logs going to another place and traces going to Zipkin or logs going to Elasticsearch. You want it all in one place, and more important, you want it to be connected so that you can see the relationship between the application and its server or infrastructure and the user experience all in one connected platform. That's what we're delivering with New Relic One today that's so exciting. >> Yeah. So, Lew, the IT industry in general is known for its fragmentation. >> Lew: Yeah, it is. >> When I want to build my application in the old days, I talk to the CIO. He's like, "Give me a million dollars and 18 months "and I will build you the Taj Mahal of my application." And we've got it beautifully designed and pull it out. Well, today things are moving much faster, but I've got everything from that Taj Mahal to the Kubernetes and Serverless, Microservice Architectures-- >> Lew: All that compartment-based stuff, yeah. >> There's usually a lot of different teams, and a lot of different tools in there. How does New Relic fit across that landscape and how are you helping to pull things together? >> Well, certainly the industry's moving from the monolithic application to the component-based application, often running in smaller and smaller services, usually running in something like Kubernetes or a containerized environment and with that comes a proliferation of things to monitor, and often a proliferation of tools. We have enterprise customers that have 20, 30 different monitoring and telemetry tools. It's not because they want it, it's because there might be one particular feature that one tool does that gives them the visibility they need. And what they want is a single platform. What people have historically used New Relic for is dropping our agents into their application or their infrastructure. Then our agents automatically put visibility in and then they report on the health of that system. We do that really well, but what we're announcing today is that we're opening up our platform to consume telemetry from Open Source, agentless sources. So that, if you've got something like Prometheus that's gathering data from Kubernetes, that can go straight into New Relic and be treated as first class data, so that you don't have to switch between a bunch of tools. None of our customers want that. They want it all in one place, but they need an open platform that's connected and most importantly programmable so that they can actually have one tool to see it all. And that's New Relic. >> A lot of the logging and tracing information out there isn't agent-led. What do you see as the future of agents, and what are some of the challenges of pulling all of these various data types together? >> Well, the most important thing for the future is that our customers have complete control in a choice. What we see particularly in large enterprises is they want both. They have a portfolio of more than a thousand applications. They want to observe them all. Most of them they'll want to drop an agent in because they don't have time to reinstrument them, but they still need to see them. Some of them they may want to manually instrument because they want a higher level of control or they want to adopt an Open Source API like OpenTelemetry. But then, if they're adopting that for some of their portfolio, when a transaction reaches across these different services, you don't want to lose visibility. We're delivering best of both worlds. You can manually instrument what you want. You can use OpenTelemetry in parts of your environment. And then you can also use our automatic instrumentation that comes from our agents. Our customers get to decide, and that's the future. >> So, Lew, you've laid out the case in a strong way as to why New Relic One should be the platform for the monitoring observability. I think you undersold a little bit the NRDB piece. When I look inside my business or I talk to customers, being able to see my data and act on my data can be challenging. You showed a demo of 10 terabytes and being able to change it in a snap. >> You know, NRDB is pretty magical. At some risk, let's see if this will show up on my phone right now. Just give you a sense of how fast NRDB is performing right now. Okay. One more time. So we've got-- >> Hold it up a little bit and show the camera this way. >> NRDB right at this moment is inserting 18 million events every second. Every second, 17.89 million pieces of data coming into NRDB in real time. And our customers are querying that in real time. Right now, in this moment, they're reading 24 billion pieces of data per second. Those pieces of data could be log messages. They could be someone pressing something on their app, could be a request going through a server. It's all in the same database. And the last one is a hundred millisecond response time on those queries, which is mind-blowing for these analytics queries. >> You actually showed the press an analyst this at lunch and it was over 20 million-- >> I think it was at 40 billion at that moment. >> 40 billion coming out and the same response time. A hundred milliseconds is Google good as to how fast I get a response. >> For this kind of data processing, it's mind-blowing. Now, the thing that our customers need to know is that all your metrics, all your events, all your logs, all your traces going into the same database with one query language. That's so much better than going to Elasticsearch and using its query language for logs, then using a totally different query language for getting at your metrics, and then trying to stitch it all together. We put it all not only in one cloud but in one database. That is the most powerful telemetry database in the world, which is NRDB. >> Lew, give us a little bit of the journey to the announcement today. Observability's been talked about in the industry for a while. VC money has been pouring into startups. There's been some acquisitions in this space already. Give us a little bit as to how we got to today. >> So how we got to today was when we started off as a company, we were championing the whole idea of observability, putting visibility into application code. As I said, that was a bit evangelical in the early days. People were wondering if they needed it. Now there's no question they need it. In fact, some people need it so badly they want complete control, and so they're manually instrumenting. OK, I've talked about that. Now where we see people going is now that all of this telemetry data is coming ideally into one place like New Relic, our customers are saying, "I need to go beyond dashboards. "Dashboards are good, but often dashboards are incomplete "to get the most out of the data we're collecting." That's why we're claiming we have the first and only platform for observability, with a capital P. What do I mean by that? It's only a platform if you can build software on it, and New Relic One is the first software development platform for observability applications. Our customers can take all this data and build real-time applications that leverage all the value out of it. When a customer buys something online, New Relic's database could be the first piece of, certainly, analytics database that sees that data. So you could a navigation that shows real-time sales for your business people all based on New Relic One. We can also solve all sorts of IT operations problems by building applications on this platform. And to prove it out, we're offering 12 free Open Source applications to anyone. They can download, they can clone them off of GitHub and push them into their New Relic account and they can use that as inspiration to build their own applications on top of our platform. >> Right. This is, if I understand, the first twelve, and you expect both New Relic and your customers will build many more. >> Yes, and actually it's thirteen already. We just added another one today. Some of those have been built by our customers already, and we're already seeing customers deploying these applications into their New Relic One accounts in production today. >> It really goes back to the promise of SaaS is that when customers need something and make a change or build on it, it's not just that customer that gets to be able to leverage that, but everybody else that is on the platform-- >> They can share and benefit. The way to think of it is, you're absolutely right, and without Force.com, Salesforce is just a CRM system. But with Force.com, companies could really leverage all the data inside Salesforce. Without programmability, ServiceNow is just a ticketing system, right? But how does ServiceNow become strategic? By allowing people to build applications tailored to their business. We believe the world needs an observability platform and the only one of its kind is New Relic One. >> All right. So, Lew, it sounds like this should be something that should accelerate growth for the company going forward. I read through your last earnings report. You're growing at 30, 35%, which is reasonable but less than the overall cloud marketplace itself is growing. So, how come the AWS, Azure, GCP tailwind isn't pushing New Relic faster? >> Well, it is a good tailwind for us, and I can't go into too much detail. We're a public company in a quiet period so I can't speak to specifics. What I can tell you is history has shown that people tend to adopt platforms at a certain rate and then, a few years later, they adopt the management technologies for those platforms. So we tend to be a little bit behind the adoption of cloud but then when people standardize and they go all in on it, then they really increase their investment in New Relic. I believe that things like our platform capabilities take our customers that might be spending... We have 850 plus customers that spend more than 100,000 a year with New Relic, and I believe when they start to adopt our platform and go strategic with us, many of them will be million-dollar customers, and that ought to be the basis of durable growth for the company. >> All right. So, Lew, there was some news leading up to the event. Some management changes. Let you speak a little bit of that, and you've got some history with, of course, Mike was already on the board, but-- >> We're so thrilled about Mike Christenson joining the company as President and COO. I've known Mike since 2006, when he acquired my last company, Wily Technology, which was really the very first APM company. Mike was the President and COO of CA, and so he had a similar role there to what he has here. Mike is, I think, one of the most brilliant operational minds I've ever met. He's been involved with New Relic for nine years. He's been one of the first investors in the company. He's been on our board of directors, and he's always had a keen mind for how to think about growing our business. I've been thinking for a long time on how to get him more involved as a member of the team and finally I convinced him to come join. Mike joined us as our President and COO. He's going to be my partner in growing the business. I think those that know me know that I love technology and products and thinking about where we are five years from now. Mike will be my partner to help make sure we're operating the company and growing the business on a day-to-day basis. >> Lew, you and your team helped create and democratize this wave of APM, Application Performance Management. As you look at it today, we talked about microservices. You talk about the dispersed nature of everything going on. How would you reframe the market today and New Relic, where it needs to be today and going forward? >> Phase 0 was people-monitored servers, back in the Stone Ages. Monitoring was just "Is the server up or down "and does it have enough CPU?" >>Blinking lights. >> Right. Then came APM. APM really was the precursor to observability. It was the notion that these are complex systems. They need to be observed at high granularity. APM gave birth to observability, so when New Relic first came along, we're "Let's democratize APM." And as observability came along, we saw this as an opportunity to open up the platform. Now where we are, if you look at our track record, first of all, my first company created the category of APM. New Relic then democratized APM, and now we're delivering the first observability platform. I believe that the future is programmable, and that New Relic is the future. >> Lew, you've always been enthusiastic when it comes to the vision that you put out, but it's been noted by some of my peers that your energy level and enthusiasm is even higher today than usual. So many things that you talked about, some of the things that you highlight, maybe behind the scenes, or things that might get missed beyond the headlines that you want to share. >> The idea for New Relic One was born two years ago. I took some of the brightest people in New Relic offsite and we fleshed out the thinking and the early prototype of what's become this. This is my life's work. This company's my life's work. I believe so much in this platform. I believe in its capabilities. I'm seeing our customers ripping it out of our hands, saying, "This is going to enable us "to fully achieve our goal of complete visibility "and completely tailored to the needs of our business." Why I'm so fired up and passionate is when you put your heart and soul into something that's new, that no one else has done before... There's been a handful of times I've done that in my life. The first time became APM. The second time became New Relic. The third was when I created NRDB. And now the fourth is New Relic One. And we're just getting started. >> Well, Lew, I want to let you have the final word as to what you want your customers taking away here from FutureStack 2019. >> My belief is that the future of observability is you need a platform. That platform needs to be open, connected, and programmable. We have such a beautiful, easy... It's a Heroku-like developer experience. So within seconds, you can be building an application that takes the telemetry data in New Relic and turns it into actionable business insights for your company. And if you want inspiration, there's 13 applications now up on GitHub that you can install right into your New Relic account, and maybe modify and tailor to your needs and republish to share with our other customers. >> I know you and your team are making sure that New Relic doesn't become a relic of the past. Thank you so much for having us here-- >> We're always in the future. >> And congratulations. I look forward to watching the progress going forward. >> Thank you, I enjoyed it. Thank you. All right, bye-bye. >> Thank you so much. And that's a wrap theCUBE's coverage of New Relic FutureStack 2019. I'm Stu Miniman, of course. Go to theCUBE.net for all of the coverage. A big thanks to the team here and everyone supporting and as always, thank you for watching theCUBE. (Electronic Music)

>> Reporter: From New York City, it's theCUBE, covering New Relic FutureStack 2019, brought to you by New Relic. >> I'm Stu Miniman, we're here in New York City right next door to Grand Central Station, at the Grand Hyatt. This first year of theCUBE, attending New Relic's Futurestack, the seventh year of the show, and happy to welcome to the program, Guy Fighel, who's the vice president and general manager of New Relic AI of course, CEO was up on stage this morning announcing New Relic AI, it's in beta, Lew said expect early 2020 for to come out, so thank you so much for joining us. >> Thank you for being here. >> All right, so Guy, you came to New Relic by way of the acquisition of signifAI. And that ends in AI of course, even though we pronounce it signify, so help us understand is this a repackaging, rebranding you know, New Relic-izing the product that was through the acquisition, tell us how we've gotten here. >> Yes, sure, so New Relic AI is a whole new set of capabilities, it's a suite of capabilities that we are launching today in beta that pretty much augments the site reliability engineers with AI and ML capabilities. It runs on top of the New Relic One platform, which is the first observability platform that is connected, open, and programmable so you have all of the existing information and data that you already have inside New Relic. And we've incorporated a lot of the technologies and the techniques that we have developed as part of signifAI with existing capabilities that New Relic already had, and pretty much integrated all of that into single user experience and single type of capabilities across the stack. >> All right so, Guy, AI is a really broad category you know, you got your AI and ML and cognitive and you know all these things, what was kind of the core IP of SignifAI when they came in. >> Sure, so we really focused on correlating and reducing the noise of all of your different alerts and incidents but not just that, we've actually built a recommendation engine on top of that, to provide you much faster context to get into potential root cause of all of your different information focused on events. And now we're combining that with all the time series data that New Relic as a platform has to offer, so you're getting a much broader capabilities for understanding. >> Yeah, you know, definitely there's that promise of AI as we know that humans alone or my traditional tooling just can't keep up, you know, talk about all the different sources of data, the volume of data. I just saw Lew talking about the amount of the millions of items being ingested into the New Relic database, and the billions of items that are being read basically per second. So, help us understand. You say we love, we talk about our videos or extracting the signal from the noise, so, did I hear it was like 80, 85% your early customers are helping to reduce that noise Bring us in a little bit more. >> True, yes, so definitely early results shows us over 80% noise reduction for some of the customers and it is important to understand this is automatic relations, so this is truly based on the engines with no human interaction. Now, we actually have even greater results when some user input is driven into the system and that raises the capabilities as well. In terms of the number of events, yes, we are dealing with huge amount of events and information in the platform and I think it's, all around, not replacing the humans, but actually augmenting the site reliability engineers, so you talked about how systems, you know, there is a great promise for those capabilities. We believe that applied intelligence is a much better term, because it gives really enabling the augmentation for the site reliability engineers. We don't believe that site reliability engineers needs to go away or can even be replaced anytime soon. We definitely think that we can help them understand better and faster, what is the type of problems that they see in their production environments, and then help them resolve that much faster and better. >> Yeah, absolutely, we're huge supporters of really, the best solutions are when you have the people plus machines, there are certain things the machines are going to do on their own, but it's the marrying, so help us understand who's going to be using New Relic AI how is it going to change their day-to-day life and maybe even kind of organizationally, what the impact will be. >> Sure, so if you're a site reliability engineer, or a DevOps themed depending on, how you want to call yourself and, you know, there's a big debate in the industry, whether it's DevOps or site reliability engineers. Pretty much anyone who is responsible for Op time in the digital production environments you're a relevant user, If you carry the pager, if you're on call, you're a relevant user, so you're going to be interacting with the system to be able to actually see what are the problems with potential recommendations and then, you can infuse the system with your own logic. Whether it's based on the logic, we also provide very easy user experience we'd like thumbs up, thumbs down, different types of feedbacks as part of the workflow and I think the most important piece is that we're connecting to users where they are. Meaning, we don't believe we need to change the workflows so, if you're a user and you're already using with a specific internet management providers and you've already connected some of the additional monitoring tools to those providers, we now offer you a streamline of syncing to those instant management platforms and then, in reaching them with all of the information that we already have on the platform. >> So Guy, we've talked about AI but, let's talk a little bit about AI Ops. So, you know I've talked to the number of the vendors I actually went to an AI ops conference earlier this year and some of the talk track was, APM is the old way, AI ops is going to replace what you were doing before Let's take all your scattered tools and consolidate them down. some of the messaging reminds me of what I heard this morning, the New Relic One platform is going to replace a number of tools, pull everything together. Help us kind of, you know, square that circle of APM and AI ops and where you see New Relic compared to some of those competitors out there today. >> Sure, so APM is application performance monitoring. it's all about monitor and have that visibility to your application layer, it has nothing to do with AI ops it has nothing to do with replacing the tools. We believe that everyone should have visibility into their application, and that's, a lot of that messaging came through Lew's key note this morning, and opening it up to any type of open source instrumentation so we can bring it to the platform whether you want to drop an agent, whether you want to use any other open source SDK, we allow you to do that. Pretty much opening up the platform and giving you the option. AI ops is a term coined by Gardner actually, and it is pretty much applying some automation, AI capabilities, ML capabilities, statistical analysis capabilities on huge amount of data that you have in a centralized place. It has nothing to do with the monitoring, per se, so, I definitely think that the industry's going into a new space, where there is a consolidation obviously with different vendors. I believe that New Relic is giving customers the choice to make, whether they want to go and continue using their old tools, and that's okay, and we are an open platform so we will sync up with their data as part of New Relic AI we'll be able to bring in the new data whether by, again inter-connecting with their incident management platform or through a rest API or native integrations or if customer choose to do that, they can just send us all of the data directly and then, we apply the AI ops capabilities on top of the existing platforms. So, it's really opening up for the choice of the customer. >> All right it's been less than a year since the acquisition of SignifAI we know that some of the things when you do an acquisition it's an area of investment, you're going to get more resources, more people but, you've mentioned customers a couple of times, maybe give us a little bit of insight as to how the customer conversations have changed now working for New Relic, as opposed to being a customer understanding that piece of the New Relic ecosystem. >> Oh absolutely, I think, you know, as you transition from a small start up into a company like New Relic you get much more exposure to enterprise customer, your scaling capabilities are much better so we're in serious conversations with a lot of the enterprises customers that have a lot of interest in what we do. A lot of it is part of the branding recognition and all of the great capabilities that New Relic has already, and then marinade that with all of the capabilities that we're bringing or that we brought into New Relic as a young start-up with all of the latest technologies and a lot of the AI capabilities which are truly innovative ones, so definitely see a lot of traction from the enterprise customers, the more sophisticated ones as well. >> All right, so the solution announced today is in beta give us a little bit of a look forward as to what we should expect to see and what feedback you're hoping to get from customers along the way and how they might get engaged if they want to. >> Yeah so definitely we are in beta today. We've engaged with customers prior to the beta, so, we already got a lot of feedback and great feedback and we make some tweaks to the product based on that. We're actually announcing AGI of a small feature today which is enhanced incident context, which provides you active detection for time series data all the way to your slack channels but the overall solution is currently in beta and as we are progressing, within every month we're going to get more and more customers engaging with the platform, and then we're going to release a much more advanced capabilities even than what we have today in GA coming early next year. >> All right great, last thing, big mention and push about observability this morning, help us understand where AI fits into the broader discussion of observability. >> So again, as I mentioned before the observability will allow you to see all of your data in a centralized place. So, it's combining matrix, events, logs and traces in a specific place that now algorithms and different techniques such as AI and ML based algorithms really, really be successful in gathering, understanding, because you have all of that different information for the human brain, it's very hard to actually go and crawl and kind of ingest all of that vast amount of different data points for machines, they're very good at that. They're starving for broad amount of data and so having that capability, building on top of a true observability platform is what makes the AI and ML so successful and drive value to customers in really understanding what the data means. >> All right well, Guy thank you so much for sharing best of luck on the journey towards GA for the the full New Relic AI in the future. We look forward to, launching it. >> Thank you so much. >> All right and once more here, walking through at the New Relic Futurestack 2019, here in New York City. I'm Stu Miniman and thanks for watching theCUBE. (upbeat music)