(energetic music) >> Welcome to the Silicon Angle News update Mobile World Congress theCUBE coverage live on the floor for four days. I'm John Furrier, in the studio here. Dave Vellante, Lisa Martin onsite. Intel in the news, Intel accelerates 5G network virtualization with radio access network boost for Xeon processors. Intel, well known for power and computing, they today announced their integrated virtual radio access network into its latest fourth gen Intel Xeon system on a chip. This move will help network operators gear up their efforts to deliver Cloud native features for next generation 5G core and edge networks. This announcement came today at MWC, formerly knows Mobile World Congress. In Barcelona, Intel is taking the latest step in its mission to virtualize the world's networks, including Core, Open RAN and Edge. Network virtualization is the key capability for communication service providers as they migrate from fixed function hardware to programmable software defined platforms. This provides greater agility and greater cost efficiency. According to Intel, this is the demand for agile, high performance, scalable networks requiring adoption. Fully virtualized software based platforms run on general purpose processors. Intel believes that network operators need to accelerate network virtualization to get the most out of these new architectures, and that's where it can be made its mark. With Intel vRAN Boost, it delivers twice the capability and capacity gains over its previous generation of silicon with the same power envelope with 20% in power savings that results from an integrated acceleration. In addition, Intel announced new infrastructure power manager for 5G core reference software that's designed to work with vRAN Boost. Intel also showcased its new Intel Converged Edge media platform designed to deliver multiple video services from a shared multi-tenant architecture. The platform leverages Cloud native scalability to respond to the shifting demands. Lastly, Intel announced a range of Agilex 7 Field Programmable Gate Arrays and eASIC N5X structured applications specific integrated circuits designed for individual cloud communications and embedded applications. Intel is targeting the power consumption which is energy and more horsepower for chips, which is going to power the industrial internet edge. That's going to be Cloud native. Big news happening at Mobile World Congress. theCUBE is there. Go to siliconangle.com for all the news and special report and live feed on theCUBE.net. (energetic music)

(inspirational music) (music ends) >> Okay, so now that we've heard Scott talk about smart data fabrics, it's time to see this in action. Right now we're joined by Jess Jowdy, who's the manager of Healthcare Field Engineering at InterSystems. She's going to give a demo of how smart data fabrics actually work, and she's going to show how embedding a wide range of analytics capabilities, including data exploration business intelligence, natural language processing and machine learning directly within the fabric makes it faster and easier for organizations to gain new insights and power intelligence predictive and prescriptive services and applications. Now, according to InterSystems, smart data fabrics are applicable across many industries from financial services to supply chain to healthcare and more. Jess today is going to be speaking through the lens of a healthcare focused demo. Don't worry, Joe Lichtenberg will get into some of the other use cases that you're probably interested in hearing about. That will be in our third segment, but for now let's turn it over to Jess. Jess, good to see you. >> Hi, yeah, thank you so much for having me. And so for this demo, we're really going to be bucketing these features of a smart data fabric into four different segments. We're going to be dealing with connections, collections, refinements, and analysis. And so we'll see that throughout the demo as we go. So without further ado, let's just go ahead and jump into this demo, and you'll see my screen pop up here. I actually like to start at the end of the demo. So I like to begin by illustrating what an end user's going to see, and don't mind the screen 'cause I gave you a little sneak peek of what's about to happen. But essentially what I'm going to be doing is using Postman to simulate a call from an external application. So we talked about being in the healthcare industry. This could be, for instance, a mobile application that a patient is using to view an aggregated summary of information across that patient's continuity of care or some other kind of application. So we might be pulling information in this case from an electronic medical record. We might be grabbing clinical history from that. We might be grabbing clinical notes from a medical transcription software, or adverse reaction warnings from a clinical risk grouping application, and so much more. So I'm really going to be simulating a patient logging in on their phone and retrieving this information through this Postman call. So what I'm going to do is I'm just going to hit send, I've already preloaded everything here, and I'm going to be looking for information where the last name of this patient is Simmons, and their medical record number or their patient identifier in the system is 32345. And so as you can see, I have this single JSON payload that showed up here of, just, relevant clinical information for my patient whose last name is Simmons, all within a single response. So fantastic, right? Typically though, when we see responses that look like this there is an assumption that this service is interacting with a single backend system, and that single backend system is in charge of packaging that information up and returning it back to this caller. But in a smart data fabric architecture, we're able to expand the scope to handle information across different, in this case, clinical applications. So how did this actually happen? Let's peel back another layer and really take a look at what happened in the background. What you're looking at here is our mission control center for our smart data fabric. On the left we have our APIs that allow users to interact with particular services. On the right we have our connections to our different data silos. And in the middle here, we have our data fabric coordinator which is going to be in charge of this refinement and analysis, those key pieces of our smart data fabric. So let's look back and think about the example we just showed. I received an inbound request for information for a patient whose last name is Simmons. My end user is requesting to connect to that service, and that's happening here at my patient data retrieval API location. Users can define any number of different services and APIs depending on their use cases. And to that end, we do also support full life cycle API management within this platform. When you're dealing with APIs, I always like to make a little shout out on this, that you really want to make sure you have enough, like a granular enough security model to handle and limit which APIs and which services a consumer can interact with. In this IRIS platform, which we're talking about today we have a very granular role-based security model that allows you to handle that, but it's really important in a smart data fabric to consider who's accessing your data and in what context. >> Can I just interrupt you for a second, Jess? >> Yeah, please. >> So you were showing on the left hand side of the demo a couple of APIs. I presume that can be a very long list. I mean, what do you see as typical? >> I mean you could have hundreds of these APIs depending on what services an organization is serving up for their consumers. So yeah, we've seen hundreds of these services listed here. >> So my question is, obviously security is critical in the healthcare industry, and API securities are like, really hot topic these days. How do you deal with that? >> Yeah, and I think API security is interesting 'cause it can happen at so many layers. So, there's interactions with the API itself. So can I even see this API and leverage it? And then within an API call, you then have to deal with all right, which end points or what kind of interactions within that API am I allowed to do? What data am I getting back? And with healthcare data, the whole idea of consent to see certain pieces of data is critical. So, the way that we handle that is, like I said, same thing at different layers. There is access to a particular API, which can happen within the IRIS product, and also we see it happening with an API management layer, which has become a really hot topic with a lot of organizations. And then when it comes to data security, that really happens under the hood within your smart data fabric. So, that role-based access control becomes very important in assigning, you know, roles and permissions to certain pieces of information. Getting that granular becomes the cornerstone of the security. >> And that's been designed in, it's not a bolt on as they like to say. >> Absolutely. >> Okay, can we get into collect now? >> Of course, we're going to move on to the collection piece at this point in time, which involves pulling information from each of my different data silos to create an overall aggregated record. So commonly, each data source requires a different method for establishing connections and collecting this information. So for instance, interactions with an EMR may require leveraging a standard healthcare messaging format like Fire. Interactions with a homegrown enterprise data warehouse for instance, may use SQL. For a cloud-based solutions managed by a vendor, they may only allow you to use web service calls to pull data. So it's really important that your data fabric platform that you're using has the flexibility to connect to all of these different systems and applications. And I'm about to log out, so I'm going to (chuckles) keep my session going here. So therefore it's incredibly important that your data fabric has the flexibility to connect to all these different kinds of applications and data sources, and all these different kinds of formats and over all of these different kinds of protocols. So let's think back on our example here. I had four different applications that I was requesting information for to create that payload that we saw initially. Those are listed here under this operations section. So these are going out and connecting to downstream systems to pull information into my smart data fabric. What's great about the IRIS platform is, it has an embedded interoperability platform. So there's all of these native adapters that can support these common connections that we see for different kinds of applications. So using REST, or SOAP, or SQL, or FTP, regardless of that protocol, there's an adapter to help you work with that. And we also think of the types of formats that we typically see data coming in as in healthcare we have HL7, we have Fire, we have CCDs, across the industry, JSON is, you know, really hitting a market strong now, and XML payloads, flat files. We need to be able to handle all of these different kinds of formats over these different kinds of protocols. So to illustrate that, if I click through these when I select a particular connection on the right side panel, I'm going to see the different settings that are associated with that particular connection that allows me to collect information back into my smart data fabric. In this scenario, my connection to my chart script application in this example, communicates over a SOAP connection. When I'm grabbing information from my clinical risk grouping application I'm using a SQL based connection. When I'm connecting to my EMR, I'm leveraging a standard healthcare messaging format known as Fire, which is a REST based protocol. And then when I'm working with my health record management system, I'm leveraging a standard HTTP adapter. So you can see how we can be flexible when dealing with these different kinds of applications and systems. And then it becomes important to be able to validate that you've established those connections correctly, and be able to do it in a reliable and quick way. Because if you think about it, you could have hundreds of these different kinds of applications built out and you want to make sure that you're maintaining and understanding those connections. So I can actually go ahead and test one of these applications and put in, for instance my patient's last name and their MRN, and make sure that I'm actually getting data back from that system. So it's a nice little sanity check as we're building out that data fabric to ensure that we're able to establish these connections appropriately. So turnkey adapters are fantastic, as you can see we're leveraging them all here, but sometimes these connections are going to require going one step further and building something really specific for an application. So why don't we go one step further here and talk about doing something custom or doing something innovative. And so it's important for users to have the ability to develop and go beyond what's an out-of-the box or black box approach to be able to develop things that are specific to their data fabric, or specific to their particular connection. In this scenario, the IRIS data platform gives users access to the entire underlying code base. So you not only get an opportunity to view how we're establishing these connections or how we're building out these processes, but you have the opportunity to inject your own kind of processing, your own kinds of pipelines into this. So as an example, you can leverage any number of different programming languages right within this pipeline. And so I went ahead and I injected Python. So Python is a very up and coming language, right? We see more and more developers turning towards Python to do their development. So it's important that your data fabric supports those kinds of developers and users that have standardized on these kinds of programming languages. This particular script here, as you can see actually calls out to our turnkey adapters. So we see a combination of out-of-the-box code that is provided in this data fabric platform from IRIS, combined with organization specific or user specific customizations that are included in this Python method. So it's a nice little combination of how do we bring the developer experience in and mix it with out-of-the-box capabilities that we can provide in a smart data fabric. >> Wow. >> Yeah, I'll pause. (laughs) >> It's a lot here. You know, actually- >> I can pause. >> If I could, if we just want to sort of play that back. So we went to the connect and the collect phase. >> Yes, we're going into refine. So it's a good place to stop. >> So before we get there, so we heard a lot about fine grain security, which is crucial. We heard a lot about different data types, multiple formats. You've got, you know, the ability to bring in different dev tools. We heard about Fire, which of course big in healthcare. And that's the standard, and then SQL for traditional kind of structured data, and then web services like HTTP you mentioned. And so you have a rich collection of capabilities within this single platform. >> Absolutely. And I think that's really important when you're dealing with a smart data fabric because what you're effectively doing is you're consolidating all of your processing, all of your collection, into a single platform. So that platform needs to be able to handle any number of different kinds of scenarios and technical challenges. So you've got to pack that platform with as many of these features as you can to consolidate that processing. >> All right, so now we're going into refinement. >> We're going into refinement. Exciting. (chuckles) So how do we actually do refinement? Where does refinement happen? And how does this whole thing end up being performant? Well the key to all of that is this SDF coordinator, or stands for Smart Data Fabric coordinator. And what this particular process is doing is essentially orchestrating all of these calls to all of these different downstream systems. It's aggregating, it's collecting that information, it's aggregating it, and it's refining it into that single payload that we saw get returned to the user. So really this coordinator is the main event when it comes to our data fabric. And in the IRIS platform we actually allow users to build these coordinators using web-based tool sets to make it intuitive. So we can take a sneak peek at what that looks like. And as you can see, it follows a flow chart like structure. So there's a start, there is an end, and then there are these different arrows that point to different activities throughout the business process. And so there's all these different actions that are being taken within our coordinator. You can see an action for each of the calls to each of our different data sources to go retrieve information. And then we also have the sync call at the end that is in charge of essentially making sure that all of those responses come back before we package them together and send them out. So this becomes really crucial when we're creating that data fabric. And you know, this is a very simple data fabric example where we're just grabbing data and we're consolidating it together. But you can have really complex orchestrators and coordinators that do any number of different things. So for instance, I could inject SQL logic into this or SQL code, I can have conditional logic, I can do looping, I can do error trapping and handling. So we're talking about a whole number of different features that can be included in this coordinator. So like I said, we have a really very simple process here that's just calling out, grabbing all those different data elements from all those different data sources and consolidating it. We'll look back at this coordinator in a second when we introduce, or we make this data fabric a bit smarter, and we start introducing that analytics piece to it. So this is in charge of the refinement. And so at this point in time we've looked at connections, collections, and refinements. And just to summarize what we've seen 'cause I always like to go back and take a look at everything that we've seen. We have our initial API connection, we have our connections to our individual data sources and we have our coordinators there in the middle that are in charge of collecting the data and refining it into a single payload. As you can imagine, there's a lot going on behind the scenes of a smart data fabric, right? There's all these different processes that are interacting. So it's really important that your smart data fabric platform has really good traceability, really good logging, 'cause you need to be able to know, you know, if there was an issue, where did that issue happen in which connected process, and how did it affect the other processes that are related to it? In IRIS, we have this concept called a visual trace. And what our clients use this for is basically to be able to step through the entire history of a request from when it initially came into the smart data fabric, to when data was sent back out from that smart data fabric. So I didn't record the time, but I bet if you recorded the time it was this time that we sent that request in and you can see my patient's name and their medical record number here, and you can see that that instigated four different calls to four different systems, and they're represented by these arrows going out. So we sent something to chart script, to our health record management system, to our clinical risk grouping application, into my EMR through their Fire server. So every request, every outbound application gets a request and we pull back all of those individual pieces of information from all of those different systems, and we bundle them together. And from my Fire lovers, here's our Fire bundle that we got back from our Fire server. So this is a really good way of being able to validate that I am appropriately grabbing the data from all these different applications and then ultimately consolidating it into one payload. Now we change this into a JSON format before we deliver it, but this is those data elements brought together. And this screen would also be used for being able to see things like error trapping, or errors that were thrown, alerts, warnings, developers might put log statements in just to validate that certain pieces of code are executing. So this really becomes the one stop shop for understanding what's happening behind the scenes with your data fabric. >> Sure, who did what when where, what did the machine do what went wrong, and where did that go wrong? Right at your fingertips. >> Right. And I'm a visual person so a bunch of log files to me is not the most helpful. While being able to see this happened at this time in this location, gives me that understanding I need to actually troubleshoot a problem. >> This business orchestration piece, can you say a little bit more about that? How people are using it? What's the business impact of the business orchestration? >> The business orchestration, especially in the smart data fabric, is really that crucial part of being able to create a smart data fabric. So think of your business orchestrator as doing the heavy lifting of any kind of processing that involves data, right? It's bringing data in, it's analyzing that information it's transforming that data, in a format that your consumer's not going to understand. It's doing any additional injection of custom logic. So really your coordinator or that orchestrator that sits in the middle is the brains behind your smart data fabric. >> And this is available today? It all works? >> It's all available today. Yeah, it all works. And we have a number of clients that are using this technology to support these kinds of use cases. >> Awesome demo. Anything else you want to show us? >> Well, we can keep going. I have a lot to say, but really this is our data fabric. The core competency of IRIS is making it smart, right? So I won't spend too much time on this, but essentially if we go back to our coordinator here, we can see here's that original, that pipeline that we saw where we're pulling data from all these different systems and we're collecting it and we're sending it out. But then we see two more at the end here, which involves getting a readmission prediction and then returning a prediction. So we can not only deliver data back as part of a smart data fabric, but we can also deliver insights back to users and consumers based on data that we've aggregated as part of a smart data fabric. So in this scenario, we're actually taking all that data that we just looked at, and we're running it through a machine learning model that exists within the smart data fabric pipeline, and producing a readmission score to determine if this particular patient is at risk for readmission within the next 30 days. Which is a typical problem that we see in the healthcare space. So what's really exciting about what we're doing in the IRIS world, is we're bringing analytics close to the data with integrated ML. So in this scenario we're actually creating the model, training the model, and then executing the model directly within the IRIS platform. So there's no shuffling of data, there's no external connections to make this happen. And it doesn't really require having a PhD in data science to understand how to do that. It leverages all really basic SQL-like syntax to be able to construct and execute these predictions. So, it's going one step further than the traditional data fabric example to introduce this ability to define actionable insights to our users based on the data that we've brought together. >> Well that readmission probability is huge, right? Because it directly affects the cost for the provider and the patient, you know. So if you can anticipate the probability of readmission and either do things at that moment, or, you know, as an outpatient perhaps, to minimize the probability then that's huge. That drops right to the bottom line. >> Absolutely. And that really brings us from that data fabric to that smart data fabric at the end of the day, which is what makes this so exciting. >> Awesome demo. >> Thank you! >> Jess, are you cool if people want to get in touch with you? Can they do that? >> Oh yes, absolutely. So you can find me on LinkedIn, Jessica Jowdy, and we'd love to hear from you. I always love talking about this topic so we'd be happy to engage on that. >> Great stuff. Thank you Jessica, appreciate it. >> Thank you so much. >> Okay, don't go away because in the next segment, we're going to dig into the use cases where data fabric is driving business value. Stay right there. (inspirational music) (music fades)

>> Okay, so now that we've heard Scott talk about smart data fabrics, it's time to see this in action. Right now we're joined by Jess Jowdy, who's the manager of Healthcare Field Engineering at InterSystems. She's going to give a demo of how smart data fabrics actually work, and she's going to show how embedding a wide range of analytics capabilities including data exploration, business intelligence natural language processing, and machine learning directly within the fabric, makes it faster and easier for organizations to gain new insights and power intelligence, predictive and prescriptive services and applications. Now, according to InterSystems, smart data fabrics are applicable across many industries from financial services to supply chain to healthcare and more. Jess today is going to be speaking through the lens of a healthcare focused demo. Don't worry, Joe Lichtenberg will get into some of the other use cases that you're probably interested in hearing about. That will be in our third segment, but for now let's turn it over to Jess. Jess, good to see you. >> Hi. Yeah, thank you so much for having me. And so for this demo we're really going to be bucketing these features of a smart data fabric into four different segments. We're going to be dealing with connections, collections, refinements and analysis. And so we'll see that throughout the demo as we go. So without further ado, let's just go ahead and jump into this demo and you'll see my screen pop up here. I actually like to start at the end of the demo. So I like to begin by illustrating what an end user's going to see and don't mind the screen 'cause I gave you a little sneak peek of what's about to happen. But essentially what I'm going to be doing is using Postman to simulate a call from an external application. So we talked about being in the healthcare industry. This could be for instance, a mobile application that a patient is using to view an aggregated summary of information across that patient's continuity of care or some other kind of application. So we might be pulling information in this case from an electronic medical record. We might be grabbing clinical history from that. We might be grabbing clinical notes from a medical transcription software or adverse reaction warnings from a clinical risk grouping application and so much more. So I'm really going to be assimilating a patient logging on in on their phone and retrieving this information through this Postman call. So what I'm going to do is I'm just going to hit send, I've already preloaded everything here and I'm going to be looking for information where the last name of this patient is Simmons and their medical record number their patient identifier in the system is 32345. And so as you can see I have this single JSON payload that showed up here of just relevant clinical information for my patient whose last name is Simmons all within a single response. So fantastic, right? Typically though when we see responses that look like this there is an assumption that this service is interacting with a single backend system and that single backend system is in charge of packaging that information up and returning it back to this caller. But in a smart data fabric architecture we're able to expand the scope to handle information across different, in this case, clinical applications. So how did this actually happen? Let's peel back another layer and really take a look at what happened in the background. What you're looking at here is our mission control center for our smart data fabric. On the left we have our APIs that allow users to interact with particular services. On the right we have our connections to our different data silos. And in the middle here we have our data fabric coordinator which is going to be in charge of this refinement and analysis those key pieces of our smart data fabric. So let's look back and think about the example we just showed. I received an inbound request for information for a patient whose last name is Simmons. My end user is requesting to connect to that service and that's happening here at my patient data retrieval API location. Users can define any number of different services and APIs depending on their use cases. And to that end we do also support full lifecycle API management within this platform. When you're dealing with APIs I always like to make a little shout out on this that you really want to make sure you have enough like a granular enough security model to handle and limit which APIs and which services a consumer can interact with. In this IRIS platform, which we're talking about today we have a very granular role-based security model that allows you to handle that, but it's really important in a smart data fabric to consider who's accessing your data and in what contact. >> Can I just interrupt you for a second? >> Yeah, please. >> So you were showing on the left hand side of the demo a couple of APIs. I presume that can be a very long list. I mean, what do you see as typical? >> I mean you can have hundreds of these APIs depending on what services an organization is serving up for their consumers. So yeah, we've seen hundreds of these services listed here. >> So my question is, obviously security is critical in the healthcare industry and API securities are really hot topic these days. How do you deal with that? >> Yeah, and I think API security is interesting 'cause it can happen at so many layers. So there's interactions with the API itself. So can I even see this API and leverage it? And then within an API call, you then have to deal with all right, which end points or what kind of interactions within that API am I allowed to do? What data am I getting back? And with healthcare data, the whole idea of consent to see certain pieces of data is critical. So the way that we handle that is, like I said, same thing at different layers. There is access to a particular API, which can happen within the IRIS product and also we see it happening with an API management layer, which has become a really hot topic with a lot of organizations. And then when it comes to data security, that really happens under the hood within your smart data fabric. So that role-based access control becomes very important in assigning, you know, roles and permissions to certain pieces of information. Getting that granular becomes the cornerstone of security. >> And that's been designed in, >> Absolutely, yes. it's not a bolt-on as they like to say. Okay, can we get into collect now? >> Of course, we're going to move on to the collection piece at this point in time, which involves pulling information from each of my different data silos to create an overall aggregated record. So commonly each data source requires a different method for establishing connections and collecting this information. So for instance, interactions with an EMR may require leveraging a standard healthcare messaging format like FIRE, interactions with a homegrown enterprise data warehouse for instance may use SQL for a cloud-based solutions managed by a vendor. They may only allow you to use web service calls to pull data. So it's really important that your data fabric platform that you're using has the flexibility to connect to all of these different systems and and applications. And I'm about to log out so I'm going to keep my session going here. So therefore it's incredibly important that your data fabric has the flexibility to connect to all these different kinds of applications and data sources and all these different kinds of formats and over all of these different kinds of protocols. So let's think back on our example here. I had four different applications that I was requesting information for to create that payload that we saw initially. Those are listed here under this operations section. So these are going out and connecting to downstream systems to pull information into my smart data fabric. What's great about the IRIS platform is it has an embedded interoperability platform. So there's all of these native adapters that can support these common connections that we see for different kinds of applications. So using REST or SOAP or SQL or FTP regardless of that protocol there's an adapter to help you work with that. And we also think of the types of formats that we typically see data coming in as, in healthcare we have H7, we have FIRE we have CCDs across the industry. JSON is, you know, really hitting a market strong now and XML, payloads, flat files. We need to be able to handle all of these different kinds of formats over these different kinds of protocols. So to illustrate that, if I click through these when I select a particular connection on the right side panel I'm going to see the different settings that are associated with that particular connection that allows me to collect information back into my smart data fabric. In this scenario, my connection to my chart script application in this example communicates over a SOAP connection. When I'm grabbing information from my clinical risk grouping application I'm using a SQL based connection. When I'm connecting to my EMR I'm leveraging a standard healthcare messaging format known as FIRE, which is a rest based protocol. And then when I'm working with my health record management system I'm leveraging a standard HTTP adapter. So you can see how we can be flexible when dealing with these different kinds of applications and systems. And then it becomes important to be able to validate that you've established those connections correctly and be able to do it in a reliable and quick way. Because if you think about it, you could have hundreds of these different kinds of applications built out and you want to make sure that you're maintaining and understanding those connections. So I can actually go ahead and test one of these applications and put in, for instance my patient's last name and their MRN and make sure that I'm actually getting data back from that system. So it's a nice little sanity check as we're building out that data fabric to ensure that we're able to establish these connections appropriately. So turnkey adapters are fantastic, as you can see we're leveraging them all here, but sometimes these connections are going to require going one step further and building something really specific for an application. So let's, why don't we go one step further here and talk about doing something custom or doing something innovative. And so it's important for users to have the ability to develop and go beyond what's an out of the box or black box approach to be able to develop things that are specific to their data fabric or specific to their particular connection. In this scenario, the IRIS data platform gives users access to the entire underlying code base. So you cannot, you not only get an opportunity to view how we're establishing these connections or how we're building out these processes but you have the opportunity to inject your own kind of processing your own kinds of pipelines into this. So as an example, you can leverage any number of different programming languages right within this pipeline. And so I went ahead and I injected Python. So Python is a very up and coming language, right? We see more and more developers turning towards Python to do their development. So it's important that your data fabric supports those kinds of developers and users that have standardized on these kinds of programming languages. This particular script here, as you can see actually calls out to our turnkey adapters. So we see a combination of out of the box code that is provided in this data fabric platform from IRIS combined with organization specific or user specific customizations that are included in this Python method. So it's a nice little combination of how do we bring the developer experience in and mix it with out of the box capabilities that we can provide in a smart data fabric. >> Wow. >> Yeah, I'll pause. >> It's a lot here. You know, actually, if I could >> I can pause. >> If I just want to sort of play that back. So we went through the connect and the collect phase. >> And the collect, yes, we're going into refine. So it's a good place to stop. >> Yeah, so before we get there, so we heard a lot about fine grain security, which is crucial. We heard a lot about different data types, multiple formats. You've got, you know the ability to bring in different dev tools. We heard about FIRE, which of course big in healthcare. >> Absolutely. >> And that's the standard and then SQL for traditional kind of structured data and then web services like HTTP you mentioned. And so you have a rich collection of capabilities within this single platform. >> Absolutely, and I think that's really important when you're dealing with a smart data fabric because what you're effectively doing is you're consolidating all of your processing, all of your collection into a single platform. So that platform needs to be able to handle any number of different kinds of scenarios and technical challenges. So you've got to pack that platform with as many of these features as you can to consolidate that processing. >> All right, so now we're going into refine. >> We're going into refinement, exciting. So how do we actually do refinement? Where does refinement happen and how does this whole thing end up being performant? Well the key to all of that is this SDF coordinator or stands for smart data fabric coordinator. And what this particular process is doing is essentially orchestrating all of these calls to all of these different downstream systems. It's aggregating, it's collecting that information it's aggregating it and it's refining it into that single payload that we saw get returned to the user. So really this coordinator is the main event when it comes to our data fabric. And in the IRIS platform we actually allow users to build these coordinators using web-based tool sets to make it intuitive. So we can take a sneak peek at what that looks like and as you can see it follows a flow chart like structure. So there's a start, there is an end and then there are these different arrows that point to different activities throughout the business process. And so there's all these different actions that are being taken within our coordinator. You can see an action for each of the calls to each of our different data sources to go retrieve information. And then we also have the sync call at the end that is in charge of essentially making sure that all of those responses come back before we package them together and send them out. So this becomes really crucial when we're creating that data fabric. And you know, this is a very simple data fabric example where we're just grabbing data and we're consolidating it together. But you can have really complex orchestrators and coordinators that do any number of different things. So for instance, I could inject SQL Logic into this or SQL code, I can have conditional logic, I can do looping, I can do error trapping and handling. So we're talking about a whole number of different features that can be included in this coordinator. So like I said, we have a really very simple process here that's just calling out, grabbing all those different data elements from all those different data sources and consolidating it. We'll look back at this coordinator in a second when we introduce or we make this data fabric a bit smarter and we start introducing that analytics piece to it. So this is in charge of the refinement. And so at this point in time we've looked at connections, collections, and refinements. And just to summarize what we've seen 'cause I always like to go back and take a look at everything that we've seen. We have our initial API connection we have our connections to our individual data sources and we have our coordinators there in the middle that are in charge of collecting the data and refining it into a single payload. As you can imagine, there's a lot going on behind the scenes of a smart data fabric, right? There's all these different processes that are interacting. So it's really important that your smart data fabric platform has really good traceability, really good logging 'cause you need to be able to know, you know, if there was an issue, where did that issue happen, in which connected process and how did it affect the other processes that are related to it. In IRIS, we have this concept called a visual trace. And what our clients use this for is basically to be able to step through the entire history of a request from when it initially came into the smart data fabric to when data was sent back out from that smart data fabric. So I didn't record the time but I bet if you recorded the time it was this time that we sent that request in. And you can see my patient's name and their medical record number here and you can see that that instigated four different calls to four different systems and they're represented by these arrows going out. So we sent something to chart script to our health record management system, to our clinical risk grouping application into my EMR through their FIRE server. So every request, every outbound application gets a request and we pull back all of those individual pieces of information from all of those different systems and we bundle them together. And for my FIRE lovers, here's our FIRE bundle that we got back from our FIRE server. So this is a really good way of being able to validate that I am appropriately grabbing the data from all these different applications and then ultimately consolidating it into one payload. Now we change this into a JSON format before we deliver it, but this is those data elements brought together. And this screen would also be used for being able to see things like error trapping or errors that were thrown alerts, warnings, developers might put log statements in just to validate that certain pieces of code are executing. So this really becomes the one stop shop for understanding what's happening behind the scenes with your data fabric. >> Etcher, who did what, when, where what did the machine do? What went wrong and where did that go wrong? >> Exactly. >> Right in your fingertips. >> Right, and I'm a visual person so a bunch of log files to me is not the most helpful. Well, being able to see this happened at this time in this location gives me that understanding I need to actually troubleshoot a problem. >> This business orchestration piece, can you say a little bit more about that? How people are using it? What's the business impact of the business orchestration? >> The business orchestration, especially in the smart data fabric is really that crucial part of being able to create a smart data fabric. So think of your business orchestrator as doing the heavy lifting of any kind of processing that involves data, right? It's bringing data in, it's analyzing that information, it's transforming that data, in a format that your consumer's not going to understand it's doing any additional injection of custom logic. So really your coordinator or that orchestrator that sits in the middle is the brains behind your smart data fabric. >> And this is available today? This all works? >> It's all available today. Yeah, it all works. And we have a number of clients that are using this technology to support these kinds of use cases. >> Awesome demo. Anything else you want to show us? >> Well we can keep going. 'Cause right now, I mean we can, oh, we're at 18 minutes. God help us. You can cut some of this. (laughs) I have a lot to say, but really this is our data fabric. The core competency of IRIS is making it smart, right? So I won't spend too much time on this but essentially if we go back to our coordinator here we can see here's that original that pipeline that we saw where we're pulling data from all these different systems and we're collecting it and we're sending it out. But then we see two more at the end here which involves getting a readmission prediction and then returning a prediction. So we can not only deliver data back as part of a smart data fabric but we can also deliver insights back to users and consumers based on data that we've aggregated as part of a smart data fabric. So in this scenario, we're actually taking all that data that we just looked at and we're running it through a machine learning model that exists within the smart data fabric pipeline and producing a readmission score to determine if this particular patient is at risk for readmission within the next 30 days. Which is a typical problem that we see in the healthcare space. So what's really exciting about what we're doing in the IRIS world is we're bringing analytics close to the data with integrated ML. So in this scenario we're actually creating the model, training the model, and then executing the model directly within the IRIS platform. So there's no shuffling of data, there's no external connections to make this happen. And it doesn't really require having a PhD in data science to understand how to do that. It leverages all really basic SQL like syntax to be able to construct and execute these predictions. So it's going one step further than the traditional data fabric example to introduce this ability to define actionable insights to our users based on the data that we've brought together. >> Well that readmission probability is huge. >> Yes. >> Right, because it directly affects the cost of for the provider and the patient, you know. So if you can anticipate the probability of readmission and either do things at that moment or you know, as an outpatient perhaps to minimize the probability then that's huge. That drops right to the bottom line. >> Absolutely, absolutely. And that really brings us from that data fabric to that smart data fabric at the end of the day which is what makes this so exciting. >> Awesome demo. >> Thank you. >> Fantastic people, are you cool? If people want to get in touch with you? >> Oh yes, absolutely. So you can find me on LinkedIn, Jessica Jowdy and we'd love to hear from you. I always love talking about this topic, so would be happy to engage on that. >> Great stuff, thank you Jess, appreciate it. >> Thank you so much. >> Okay, don't go away because in the next segment we're going to dig into the use cases where data fabric is driving business value. Stay right there.

>>Hey everyone, welcome back. It's the Cube live in Las Vegas. We've been here since Monday covering the event wall to coverage on the cube at AWS Reinvent 22, Lisa Martin here with Dave Ante. Dave, we're hearing consistently north of 50,000 people here. I'm hearing close to 300,000 online. People are back. They are ready to hear from AWS and its ecosystem. Yeah, >>I think 55 is the number I'm hearing. I've been using 50 for 2019, but somebody the other day told me, no, no, it was way more than that. Right, right. Well this feels bigger in >>2019. It does feel bigger. It does feel bigger. And we've had such great conversations as you know, because you've been watching the Cube since Monday night. We're pleased to welcome from Sumo Logic. Lynn Doherty, the president of Worldwide Field Operations. Lynn, welcome to the program. >>Thank you for having me. I'm glad to be here. Talk >>To us about what's going on at Sumo Logic. We cover them. We've been following them for a long time, but what's what's new? >>We have a lot going on at Sumo Logic. What we do is provide solutions for both observability and security. And if you think about the challenges that our customers are facing today, everybody as they're doing this digital transformation is in a situation where the data and the digital exhausts that they have is growing faster than their budgets and especially in what looks like potentially uncertain economic times. And so what we do is enable them to bring that together on a platform so that they can solve both of those problems in a really cost effective way. >>What are some of the things that you're hearing from customers in the field where it relates to Sumo logic and aws? What are they asking for? >>They continue to ask for security and, and I think as everybody goes on that journey of digital transformation and, and I think what's going on now is that there are people who are kind of in wave two of that digital transformation, but security continues to be top of mind. And again, as as our customers are moving into potentially uncertain economic times and they're saying, Hey, I've gotta shore up and, and maybe do smarter things with my budget, cybersecurity is one piece of that that is not falling off the table. That their requirements around security, around audits, around compliance don't go away regardless of what else happens. >>How do you fit in the cloud ecosystem generally? AWS specifically? I think AWS is generally perceived as a more friendly environment for the ecosystem partners. We saw CrowdStrike yesterday, you know, stock got crushed. They had a great quarter, but not as great as they thought it could be. Yeah. And one, some of the analysts were saying, well, it could be Microsoft competition at the low end of the market. Okay. AWS is like the ecosystem partners are really strong in security, lot of places to add value. Where does Sumo Logic >>Fit? Yeah, we are all in with aws. So AWS is our platform of choice. It's the platform that we're built on. It's the only platform that we use. And so we work incredibly closely with aws. In fact, last year we were the first ever AWS ISV partner of the year for as Sumo Logic, which we're not as big as some of the other players, but it just is a testament to the partnership that we have with aws. >>When you're out in the field talking with customers, we talked about some of the challenges there, but where are your customer conversations? You talked about security and cyber as is not falling off the table. In fact, it's, it's rising up the stock, it's a board level conversation. So where are the customer conversations that you're having? Are they, are they at the developer level? Are they higher? Are they at the C-suite? What does that look like? >>Yeah, it's, it's actually at both the developer and the C-suite. And so there's really two motions. The first is around developers and practitioners and people that run security operation centers. And they need tools that are easy to use that integrate in their environment. And so we absolutely work with them as a starting point because if, if they aren't happy with the tools that they have, you know, the customer can't go on that digital transformation, can't have effective application usage. But we also need to talk to C-Suite and that to CIO or a CISO who's really thinking often more broadly about how do we do things as a platform and how do we consolidate some of our tools to rationalize what we're using and really make the most of the budget that we have. And so we come at it from both angles. We call it selling above the line and below the line because both of those are really important people for us to work with. >>Above the line being sort of the business executives, >>Business executives and C-suite executives. And then, but below the line are the actual people who are using the product and using a day to day interacting with the tools. >>So how are those above the line and below the line conversations, you know, different? What, what are the, what are the above the line conversations? What are the sort of keywords that, you know, that resonate? Let's start there. >>Yeah, above the line, there's a lot that's around how do we make the most of the investments that we're making. And so there are no shortage of tools, right? You can look around this AWS floor and see that there are no shortage of tools and software products out there. And so above the line it's how do we make use of the budget that we have and get the most out of the investments we've made and do that in a really smart way. Often thinking about platforms and consolidating tools and, and using the tools and getting full value of what they have below the line. I think it's really how do they have really strong ease of use? How do they get the fastest time to value? Because time to value is really important when you're a practitioner, when you're developing an application, when you're migrating and modernizing an application, having tools that are easy to use and not just give you data but give you insights. And so that's what a conversation with a practitioner for us is, is taking data and turning it into insights that they can use. >>You know, and it seems like we never get rid of stuff in it, but there's a big conversation now when you talk to practitioners, okay, well you got some budget pressures, your sales cycles are elongating. What are you doing about, a lot of 'em are saying, well, we're consolidating and nowhere is that more needed probably than insecurity. So how, how are you seeing that play out in the market? Are you able to take advantage of that as Sumo? >>I think there's the old joke that says there is no ciso. Whoever says, if I just had one more tool, I'd be secure. >>And >>Nobody ever says that it's not one more tool. It's having effective tools and having tools that integrate. And so when I think of Sumo Logic in that space, it's number one, we really integrate with so many different tools out there that give, again, not just security information, but security insights. And so that becomes a really important part of the conversation. What, when you talk about tool consolidation, that's absolutely, I think something that has been a journey that a lot of our customers have been on and probably will be on for the foreseeable future. And so that's a place that we can really help because we have a platform that you can leverage our tool on the DevOps side and on the security side. And that's a conversation that we have a lot with our customers. Are >>You helping bridge those two, the security folks, the dev folks? Cause we talk about Shift left and CISO being involved now. Is Sumo Logic helping from a cultural perspective to bridge those two? >>Yeah, well I think it's a really good point that you make. It's, there's part of it that's a technology challenge and then there's part of it that's a cultural challenge and an organization silo challenge that happens. And so it is something that we try to bring our customers together and often start in one area of the business and help move into other areas and bring them together. It, it also comes down to that data growing faster than budgets and customers can no longer afford to keep multiple copies of the same data, the same metrics, and all of that digital exhaust that comes as they move to the cloud and modernize their applications. And so we bring that together and help them get the most use out of it. >>There are a lot of, we've been talking all week in the cube about sort of adjacencies to security. We've talking about data protections now becoming an adjacency. You know, you talk about resilience within an organization, everybody was sort of caught off guard, obviously with the pandemic, not as resilient as they could have been. So it seems like the scope of security is really expanding. You know, they always say it's, it's a team sport, okay, it's a pro mine, but it's true. Right? Whereas it used to be that guy's problem. Yeah. What are you seeing in terms of that evolution? >>Yeah, I think you're absolutely right. I think the pandemics force some of that faster than was happening, but it's absolutely something that is going on that cybersecurity is now built in from the ground up and I've been in cyber security for years and it's moved from an afterthought or something that comes after the fact, Hey, let's build the application and then we'll worry about security to, it needs to be a secure application from the ground up. And so that is bringing together that dev and SEC ops a lot because it needs to be built in, the security piece needs to be built in from the ground up on the development side. >>Absolutely. The, the threat landscape has changed so much in the last couple of years. Has the fraudsters, bad actors, whatever you wanna call 'em, are getting far more sophisticated. Yeah. So security can't be an afterthought. Can't be a built on. Yeah, it's gotta be integrated, built in from the ground up for organizations to be able to be, as they've said, resilient. We're hearing a lot about resiliency and the importance of it. For any business. >>For any business, it's important for every business. And if you think about how we interact with companies now, our view of a bank isn't the branch, it's the app, our view of office, it's this, right? It's, it's on the phone, it's on digital devices, it's on a website. And so that is your interaction, that is your experience. And so that plays into, is it up, is it running, is it responsive? That application performance piece, but also the security piece of is it secure? Is my data protected? You know, do I have any vulnerability? >>Yeah, you must have, being in field operations, a favorite customer story that you really think defines the value proposition beautifully of Sumo Logic. What story is that? >>Wow, that's a good question. I have a lot of favorite stories. You know, we have customers, for example, gaming customers that maybe aren't able to predict what their usage looks like. And that's something that we really help our customers with is the peaks and valleys. And so we have gaming customers or retail customers that we're able to take their data sources and they may be at one level and go to 10 x in a day without any notice. And we're able to handle that for them. And I think that's something that I'm really proud of is that we don't make that the customer's problem. They're, they're peaks and valleys, they're spikes that may happen seasonally in retail. It's Black Friday sales that are coming up. It's a new game that gets released. It's a new music piece that gets released and they are going to see that, but they don't have to worry about that because of us. And so that really makes me proud that we handle that and take that problem off of their shoulders. I >>See Pokemon on the website, that's a hugely popular >>Game, Pokemon now. Yes. >>Last question for you, we've got about 30 seconds left. If you had a billboard to put up in Denver where you live about Sumo Logic and its impact like an elevator pitch or a phrase that you think really summarizes the impact, what would it >>Say? Yeah, well it's a really good question. I've got it on my shirt. I dunno, it's not for the G-rated, but we fix things faster. Fix shit faster. And so for us that's really, ultimately, it's not just about having information, it's not just about having the data, it's about being able to resolve your problems quickly. And whether that's an application or a security issue, we've gotta be able to fix it faster for our customers and that's what we enable them to do. >>Fix bleep faster. Lynn, it's been a pleasure having you on the program. Thank you so much. Thank you for joining us. Awesome step at Sumo Logic. For our guest and for Dave Ante. I'm Lisa Martin. You're watching The Cube Live from Las Vegas, the leader in live enterprise and emerging tech coverage.

(upbeat music) >> It's theCUBE live in Las Vegas, covering AWS re:Invent 2022. This is the first full day of coverage. We will be here tomorrow and Thursday but we started last night. So hopefully you've caught some of those interviews. Lisa Martin here in Vegas with Paul Gillin. Paul, it's great to be back. We just saw a tweet from a very reliable source saying that there are upwards of 70,000 people here at rei:Invent '22 >> I think there's 70,000 people just in that aisle right there. >> I think so. It's been great so far we've gotten, what are some of the things that you have been excited about today? >> Data, I just see data everywhere, which very much relates to our next guest. Companies realizing the value of data and the strategic value of data, beginning to treat it as an asset rather than just exhaust. I see a lot of focus on app development here and building scalable applications now. Developers have to get over that, have to sort of reorient themselves toward building around the set of cloud native primitives which I think we'll see some amazing applications come out of that. >> Absolutely, we will. We're pleased to welcome back one of our alumni to the program. Shinji Kim joins us, the CEO and founder of Select Star. Welcome back Shinji. It's great to have you. >> Thanks Lisa, great to be back. >> So for the audience who may not know much about Select Star before we start digging into all of the good stuff give us a little overview about what the company does and what differentiates you. >> Sure, so Select Star is an automated data discovery platform. We act like it's Google for data scientists, data analysts and data engineers to help find and understand their data better. Lot of companies today, like what you mentioned, Paul, have 100s and 1000s of database tables now swimming through large volumes of data and variety of data today and it's getting harder and harder for people that wants to utilize data make decisions around data and analyze data to truly have the full context of where this data came from, who do you think that's inside the company or what other analysis might have been done? So Select Star's role in this case is we connect different data warehouses BI tools, wherever the data is actually being used inside the company, bringing out all the usage analytics and the pipeline and the models in one place so anyone can search through what's available and how the data has been created, used and being analyzed within the company. So that's why we call it it's kind of like your Google for data. >> What are some of the biggest challenges to doing that? I mean you've got data squirreled away in lots of corners of the organization, Excel spreadsheets, thumb drives, cloud storage accounts. How granular do you get and what's the difficulty of finding all this data? >> So today we focus primarily on lot of cloud data warehouses and data lakes. So this includes data warehouses like Redshift, Snowflake (indistinct), Databricks, S3 buckets, where a lot of the data from different sources are arriving. Because this is a one area where a lot of analysis are now being done. This is a place where you can join other data sets within the same infrastructural umbrella. And so that is one portion that we always integrate with. The other part that we also integrate a lot with are the BI tools. So whether that's (indistinct) where you are running analysis, building reports, and dashboards. We will pull out how those are, which analysis has been done and which business stakeholders are consuming that data through those tools. So you also mentioned about the differentiation. I would say one of the biggest differentiation that we have in the market today is that we are more in the cloud. So it's very cloud native, fully managed SaaS service and it's really focused on user experience of how easily anyone can really search and understand data through Select Star. In the past, data catalogs as a sector has been primarily focused on inventorizing all your enterprise data which are in many disciplinary forces. So it was more focused on technical aspect of the metadata. At the same time now this enterprise data catalog is important and is needed for even smaller companies because they are dealing with ton of data. Another part that we also see is more of democratization of data. Many different types of users are utilizing data whether they are fully technical or not. So we had basically emphasis around how to make our user interface as intuitive as possible for business users or non-technical users but also bring out as much context as possible from the metadata and the laws that we have access to, to bring out these insights for our customers. >> Got it. What was the impetus or the catalyst to launch the business just a couple of years ago? >> Yeah, so prior to this I had another data startup called Concord Systems. We focused on distributed stream processing framework. I sold the company to Akamai which is now called ... and the product is now called IoT Edge Connect. Through Akamai I started working with a lot of enterprises in automotive and consumer electronics and this is where I saw lot of the issues starting to happen when enterprises are starting to try to use the data. Collection of data, storage of data, processing of data with the help of lot of cloud providers, scaling that is not going to be a challenge as much anymore. At the same time now lot of enterprises, what I realized is a lot of enterprises were sitting on top of ton of data that they may not know how to utilize it or know even how to give the access to because they are not 100% sure what's really inside. And more and more companies, as they are building up their cloud data warehouse infrastructure they're starting to run into the same issue. So this is a part that I felt like was missing gap in the market that I wanted to fulfill and that's why I started the company. >> I'm fascinated with some of the mechanics of doing that. In March of 2020 when lockdowns were happening worldwide you're starting new a company, you have to get funding, you have to hire people, you don't have a team in place presumably. So you have to build that as free to core. How did you do all that? (Shinji laughs) >> Yeah, that was definitely a lot of work just starting from scratch. But I've been brewing this idea, I would say three four months prior. I had a few other ideas. Basically after Akamai I took some time off and then when I decided I wanted to start another company there were a number of ideas that I was toying around with. And so late 2019 I was talking to a lot of different potential customers and users to learn a little bit more about whether my hypothesis around data discovery was true or not. And that kind of led into starting to build prototypes and designs and showing them around to see if there is an interest. So it's only after all those validations and conversations in place that I truly decided that I was going to start another company and it just happened to be at the timing of end of February, early March. So that's kind of how it happened. At the same time, I'm very lucky that I was able to have had number of investors that I kept in touch with and I kept them posted on how this process was going and that's why I think during the pandemic it was definitely not an easy thing to raise our initial seed round but we were able to close it and then move on to really start building the product in 2020. >> Now you were also entering a market that's there's quite a few competitors already in that market. What has been your strategy for getting a foot in the door, getting some name recognition for your company other than being on the queue? >> Yes, this is certainly part of it. So I think there are a few things. One is when I was doing my market research and even today there are a lot of customers out there looking for an easier, faster, time to value solution. >> Yes. >> In the market. Today, existing players and legacy players have a whole suite of platform. However, the implementation time for those platforms take six months or longer and they don't necessarily are built for lot of users to use. They are built for database administrators or more technical people to use so that they end up finding their data governance project not necessarily succeeding or getting as much value out of it as they were hoping for. So this is an area that we really try to fill the gaps in because for us from day one you will be able to see all the usage analysis, how your data models look like, and the analysis right up front. And this is one part that a lot of our customers really like and also some of those customers have moved from the legacy players to Select Star's floor. >> Interesting, so you're actually taking business from some of the legacy guys and girls that may not be able to move as fast and quickly as you can. But I'd love to hear, every company these days has to be a data company, whether it's a grocery store or obviously a bank or a car dealership, there's no choice anymore. As consumers, we have this expectation that we're going to be able to get what we want, self-service. So these companies have to figure out where all the data is, what's the insides, what does it say, how can they act on that quickly? And that's a big challenge to enable organizations to be able to see what it is that they have, where's the value, where's the liability as well. Give me a favorite customer story example that you think really highlights the value of what Select Star is delivering. >> Sure, so one customer that we helped and have been working with closely is Pitney Bowes. It's one of the oldest companies, 100 year old company in logistics and manufacturing. They have ton of IoT data they collect from parcels and all the tracking and all the manufacturing that they run. They have recently, I would say a couple years ago moved to a cloud data warehouse. And this is where their challenge around managing data have really started because they have many different teams accessing the data warehouses but maybe different teams creating different things that might have been created before and it's not clear to the other teams and there is no single source of truth that they could manage. So for them, as they were starting to look into implementing data mesh architecture they adopted Select Star. And they have a, as being a very large and also mature company they have considered a lot of other legacy solutions in the market as well. But they decided to give it a try with select Star mainly because all of the automated version of data modeling and the documentation that we were able to provide upfront. And with all that, with the implementation of Select Star now they claim that they save more than 30 hours a month of every person that they have in the data management team. And we have a case study about that. So this is like one place where we see it save a lot of time for the data team as well as all the consumers that data teams serve. >> I have to ask you this as a successful woman in technology, a field that has not been very inviting to women over the years, what do you think this industry has to do better in terms of bringing along girls and young women, particularly in secondary school to encourage them to pursue careers in science and technology? >> Like what could they do better? >> What could this industry do? What is this industry, these 70,000 people here need to do better? Of which maybe 15% are female. >> Yeah, so actually I do see a lot more women and minority in data analytics field which is always great to see, also like bridging the gap between technology and the business point of view. If anything as a takeaway I feel like just making more opportunities for everyone to participate is always great. I feel like there has been, or you know just like being in the industry, a lot of people tends to congregate with people that they know or more closed groups but having more inclusive open groups that is inviting regardless of the level or gender I think is definitely something that needs to be encouraged more just overall in the industry. >> I agree. I think the inclusivity is so important but it also needs to be intentional. We've done a lot of chatting with women in tech lately and we've been talking about this very topic and that they all talk about the inclusivity, diversity, equity but it needs to be intentional by companies to be able to do that. >> Right, and I think in a way if you were to put it as like women in tech then I feel like that's also making it more explosive. I think it's better when it's focused on the industry problem or like the subject matter, but then intentionally inviting more women and minority to participate so that there's more exchange with more diverse attendees in the AWS. >> That's a great point and I hope to your 0.1 day that we're able to get there, but we don't have to call out women in tech but it is just so much more even playing field. And I hope like you that we're on our way to doing that but it's amazing that Paul brought up that you started the company during the pandemic. Also as a female founder getting funding is incredibly difficult. So kudos to you. >> Thank you. >> For all the successes that you've had. Tell us what's next for Select Star before we get to that last question. >> Yeah, we have a lot of exciting features that have been recently released and also coming up. First and foremost we have an auto documentation feature that we recently released. We have a fairly sophisticated data lineage function that parses through activity log and sequel queries to give you what the data pipeline models look like. This allows you to tell what is the dependency of different tables and dashboards so you can plan what your migration or any changes that might happen in the data warehouse so that nothing breaks whenever these changes happen. We went one step further to that to understand how the data replication actually happens and based on that we are now able to detect which are the duplicated data sets and how each different field might have changed their data values. And if the data actually stays the same then we can also propagate the same documentation as well as tagging. So this is particularly useful if you are doing like a PII tagging, you just mark one thing once and based on the data model we will also have the rest of the PII that it's associated with. So that's one part. The second part is more on the security and data governance front. So we are really seeing policy based access control where you can define who can see what data in the catalog based on their team tags and how you want to define the model. So this allows more enterprises to be able to have different teams to work together. And last one at least we have more integrations that we are releasing. We have an upgraded integration now with Redshift so that there's an easy cloud formation template to get it set up, but we now have not added Databricks, and power BI as well. So there are lots of stuff coming up. >> Man, you have accomplished a lot in two and a half years Shinji, my goodness! Last question for you, describing Select Star in a bumper sticker, what would that bumper sticker say? >> So this is on our website, but yes, automated data catalog in 15 minutes would be what I would call. >> 15 minutes. That's awesome. Thank you so much for joining us back on the program reintroducing our audience to Select Star. And again, congratulations on the successes that you've had. You have to come back because what you're creating is a flywheel and I can't wait to see where it goes. >> Awesome, thanks so much for having me here. >> Oh, our pleasure. Shinji Kim and Paul Gillin, I'm Lisa Martin. You're watching theCUBE, the leader in live enterprise and emerging tech coverage. (upbeat music)

(upbeat music) >> Welcome back to theCUBE, everyone. This is Lisa Martin, live in Miami. I'm at IFS Unleashed 2022. We've had a great day talking with IFS executives, customers, partners. We're going to be having another great conversation next. I have two guests here on set with me, Sarah Nicastro joins us, the founder Future Field of Service, and VP of Customer Engagement at IFS, and Roel Rentmeeters, the VP of Digital Transformation at Munters. Welcome to the program. >> Thanks for having us. >> So, here we are surrounded by about 1500 or so people. The buzz in here is, people are ready to come back. They're just ready to come back, have these conversations with their peers and their colleagues at IFS which is great to to see and to feel, right? Sarah, let's start with you, your role, founder Future of Field Service. Talk to me about what that is and what the genesis was. >> Yeah, absolutely. So, a lot of what I do is actually what you're doing and interviewing folks, creating content. I was in the media before I joined IFS, almost four years ago in service specifically. So service, you've probably heard a lot today about moment of service. Service is a huge focus area for IFS and Future of field service is thought leadership resource that IFS allowed me to come on board and create, not only for customers, but for the broader service community. So, I write articles related to service trends host a weekly podcast. Over time with the company as I got to engage with more and more customers, and there's so much value in them connecting with one another. You see that here, like you said, people are so excited to be together, but fostering those connections within our customer community, allowing them to get to know each other, share our best practices, as well as making sure that we're bringing the voice of customer always into IFS. So, that's what I do on the customer engagement side. >> I love it. The voice of the customer is invaluable. And of all the conversations that I've had today, it's so clear how strategic and strong the relationships are that IFS has with its customers. Roel, talk to us a little bit about Munters, you're a customer and talk about the relationship that you've established with IFS and the team. >> Yeah, with pleasure. So, Munters is a Swedish company. We are a global leader in sustainable air treatment solutions. So, think about deunification, cooling, but in big industrial applications. I am the VP of digital services or digital transformation. Prior to that, until very recently, I was a VP of services. And we started that standardization roadmap five years ago, six years ago. We work very closely with IFS. We're implementing a new apps version as an ERP for Munters. And so that servitization moving from additional services to outcome-based services has the digital aspect. So, my move is a natural flow with that. >> How long has Munters been in business? >> It's founded in 1955. >> Oh wow. >> It's a Swedish company, quite traditional still in their manufacturing and delivering services. But the shift is there. >> Talk to me about that shift and how IFS has been an accelerant of that. It's challenging for legacy businesses to evolve and transform. Obviously in this day and age, you don't have a choice. But talk to us about the digital transformation of the business so that you can deliver more to your customers and how IFS has been foundational to that. >> Yeah. So, so that servitization roadmap eventually it is something that our customers want. We captured it. Customers want remote management, they want connected devices, but that alone will not bring you servitization. You need to have your strong foundation in the back with a good process, a good system that can support that process. And that's where IFS came in for us. We are a long time IFS user, so, we are on the eighth version in Europe of app eight, but we are doing a new implementation to 10, and this way, a global implementation with clean data that needs to be cleansed, new processes, end to end processes. And so IFS is our partner to support us in this roadmap along with other developments and things IFS is doing, think about remote management, something we've implemented during COVID and that perfectly aligns with that road towards servitization. >> Yeah, I was just going to say Roel and I were on a panel discussion earlier today with two other customers, and all different industries, but when we said what is the focus of the business they all said servitization or outcomes based services. Me too. Me too, me too, right? So, it's a journey that a lot of our customers are on looking at how they differentiate through service, how they move away from being a provider of products or things, and someone that their customers can trust to provide peace of mind, uptime, outcomes, experiences, things like that. >> It's all about outcomes. And we're hearing more and more about servitization. It's not a new concept. The term is somewhat newer to some of these conversations. But we're seeing a lot of businesses especially in light of COVID pivot in that direction and they need a partner that they can trust like IFS to help them get there. Sarah, let's talk more about customer engagement. What are some of the different facets that need to be considered? You guys, IFS has expertise in five verticals which I love the vertical specialization there. But talk to us about some of those facets that make customer engagement successful. >> Yeah, so I think you're absolutely right. So we have our five industries that we focus heavily on, and that is where most of our customer engagement has and does reside, right? So each industry has its own group of customers that get together weigh in on how IFS is innovating, what they need from the company and their respective industries, etc. What I'm focused on, and probably a lot of it is just based on my background. I mentioned on the panel there was a lot of head nods and me-too, me-too. That's because there are also elements of innovation and change that are happening across industries that our customers care a lot about. So what I'm working on at the moment is introducing sort of another layer of customer engagement where we're also fostering those cross industry more innovation-centered conversations so that we can not only better understand what our customers are focused on there, but also allow them to connect and learn from one another. >> I love that. There's so much power and potential. Roel, talk to us about that from your perspective, the opportunity. You mentioned, Sarah, the panel that you guys were on earlier today, but talk to us about the opportunity that IFS is giving you to engage with your peers in other industries, but also for you to learn and get takeaways from them. That's got to be pretty unique from a technology partner perspective. >> That definitely is. And the Future of Field Service, it's one of those four where I think we share so much knowledge, not just while we are sitting together and having our talks with Sarah, also individually we connected with each other. Companies that are also Swedish based like Tetra Park, etc, So, there's kind of bonds that we can see. But it's true, we are learning from each other also because some are maybe a bit more advanced than others in this area. So we can learn, not just around how they do their processes, how they find technicians on the market which is very scarce today and very difficult. How do you retain them? But also, what are you experiencing during your implementation?? What is your partner that are... What are pitfalls that you have discovered since you were there? Would you go to cloud or would you still wait in APP 10? So we share that knowledge to each other and we learn a lot from each other, which is something I like. I also like the fact that IFS is a very customer-centric company, as we mentioned before, the fact that you have changed advisory boards where the voice of the customer is going to be important, where you can feed back or IFS feeds back trends and things they see going forward where we can also say, but, "Would it not be better that the user interface for a technician who just wants to do this and this and this is simpler than what you offer today. So, it's a win-win situation for both of us. >> It's a collaboration. >> Yeah, I like it. >> It should be. And I'm really passionate about what what I do, but to be on sessions with a group of customers and have them say, "I'm going to call you later because I want to know more about how you did this, or can we connect?" And to see those connections happen, it's great to have events like this and they have been on hold, but ideally happen every year or year and a half. But to keep those connections going continuously is really important to me. >> Well, the innovations that IFS can span from just those connections alone is infinite, right? I mean, your mind can wander with all of the different things that can come out of that. Sarah, talk a little bit more about... We often talk about the voice of the customer. It's incredibly powerful. I always think it's the most objective opinion, but one of the things that I think I was learning earlier today is it's not just about the voice of the customer. It's taking the insights from those customers into the company, into the development of the technologies to then be able to fuel customer-driven changes. Talk about that as a one of the focuses that IFS has. >> Yeah, I mean, not only we, but our customers are talking a lot more about outside in innovation, right? An inside out model does not work today. And so, that's really what the focus is. And there's so many parallels between what we're focused on, what our customers are focused on, right? And so, I think voice of the customer, it's always good to have a quantitative measure where you're doing surveys, you're understanding what is your NBS, how do your customers feel, are they satisfied, etc? But it's also very important to have more of a qualitative or more intimate forum to have those deeper discussions to really get into some of the details that, to Roel's point, can then influence. Okay, well, we haven't quite thought about it that way. The more you have those discussions, the more you can notice what those common challenges or opportunities are so that when you are putting effort into our own evolution and modernization, we can make sure that's geared toward the the impact our customers need. >> Right. That's critical. It's all about outcomes. Customers need to move faster and faster and faster these days, right? I think one of the things that was in very short supply during the pandemic was patients and tolerance. And I don't know that it's going to come back. I think we are... >> I've never had it personally. (Lisa and Sarah laugh) >> I had a little bit of it, but I think the consumerization of tech, we expect these experiences in our professional world to be as easy as going on Amazon and buying whatever we want. We also want the brands to know enough about us where it's not creepy, but make it personalized to some degree, have that intimate relationship with me that's good enough to get me the outcome that I'm looking for. We all have that in our personal lives, but it flows into our business lives as well. So you're dealing with customers that probably have gotten more demanding as a result. >> I think you're absolutely right. And at the same time, not all customers want to go into that entire outcome-based direction. So, but what I like about it is, if you can do outcome-based service, you can also accommodate those customers and the service they want without having the outcome, think about as a lay based service or those kind of things because your organization and your systems and your processes are ready to do this. It's actually part of it. So, that voice of the customer is for us important enough to know it's not one thing that we should create. It's not one service offering. It depends on what kind of customers you are. Look at data center customers for which we do a lot of cooling, they are scared to hell that that thing would be brought down because it would endanger their entire data center. They don't want to connect, but they want to have certain data that they can see inside their environment and that they can pass on to us. So, you need to accommodate all those things. So, your voice of customer is extremely important. >> You mentioned, Lisa, that we've been talking about servitization for quite a while, right? And it's because it involves so many layers of change within a business, right? And so, it's really more of a journey, a continuum. And to Roel's point, companies need to be able to address what their customers need at different points. Some may want to remain on a CapEx model and some may want to move to an outcomes model. We also need to be able to address what our customers need on a bit of a continuum, which is what we're working toward with IFS cloud, is being able to meet people where they are and give them what they need that can grow with them as they grow with their customers. >> And that's absolutely essential for a good partnership and that makes for those moments of service to happen at the end of the day to that end user, whether it's an airline or whatnot. IFS cloud, and we have a couple minutes left, but IFS cloud was launched only 18 months ago and I was in the keynote this morning and Christian was actually here on the show with me too, 400,000 plus users in 18 months, that's growing pretty quickly. What's been some of the feedback from the customer side, and we'll get your perspective, Roel, as well? >> I don't have cloud yet, so we are implementing APP 10. Why? Because we signed up with IFS two years ago. At that time it was not yet there. And we think now let's first do this and then we can move to cloud. But it's not that we will not move to cloud. It's something we will do eventually. I like the fact that IFS thinks of having everything in one rather than having the different pieces, which made it also for me personally very difficult to make a choice. Do I go for the standalone version of the field service, or do I take the one that is embedded in the ERP? What is the difference between those two? Is there functionalities that I'm going to miss if I choose one or the other? So, the fact that it will be all together, it makes it easier also to add on later on like customer service or the customer ports or all those kind of things. So, I like that concept. So, I'm very curious to hear from peers here that have done the implementation like the Tetre Pack, how's it going? What is their feeling? I'm very curious. >> Well, I imagine at this kind of event, you're going to learn just that. >> Yep. (Lisa chuckles) >> You were going to say something, Sarah. >> Yeah, I was just going to say, I think it's a really good point that you mentioned with all of the things we're used to in our consumer lives, we want simplicity. Having complex technology stacks is at odds with delivering simplicity to the customer, right? And so, so that's the goal really. I was just in a session before this with Yotin who's on the journey to Evergreen with IFS cloud. And it's really the idea of eliminating some of the manual effort that exists in maintaining a system, making it a lot easier and faster for organizations to adopt innovation that comes out and give them more agility really in focusing on meeting their customer needs instead of focusing on managing their technology. >> Absolutely. Nobody wants to be doing that. Thank you so much, both of you for joining me on the program today, talking about what IFS is doing, the Future of Field Service, how you're partnering, truly partnering with customers. It's impressive. We talked to a lot of vendors and a lot of customers and I definitely am seeing some unique differentiation here. So, thank you so much for sharing your insights with me today. >> Thanks, Lisa. >> Thank you. >> Appreciate it. For my guests, I'm Lisa Martin. You've been watching theCUBE live from Miami. We've been here all day. We thank you so much for watching. We will see you next time. (soft music)

>>The Cube presents UI Path Forward five. Brought to you by UI Path. >>We're back the cube's coverage of UI path forward. Five. And we're live. Dave Velante with Dave Nicholson. AJ Gupta is here. He's the Chief Digital Transformation Officer at the Motor Vehicles of California dmv. Welcome Jay. Good to see you. >>Thank you. >>Good to see you. Wow, you, you have an interesting job. I would just say, you know, I've been to going to conferences for a long time. I remember early last decade, Frank Sluman put up a slide. People ho hanging out, waiting outside the California dmv. You were the butt of many jokes, but we have a happy customer here, so we're gonna get it to your taste >>Of it. Yeah, very happy >>Customer, obviously transform the organization. I think it's pretty clear from our conversations that that automation has played a role in that. But first of all, tell us about yourself, your role and what's going on at the dmv. >>Sure. Myself, a j Gupta, I am the Chief Digital Transformation Officer at the dmv. Somewhat of i, one would say a made up title, but Governor's office asked me, Okay, we need help. And that's what >>Your title though? >>Yeah, yeah. So I'm like, well we are doing business and technology transformation. So that's, that's what I've been doing for the last three years at the dmv. Before that I was in private sector for 25 years, decided first time to give back cuz I was mostly doing public sector consulting. So here I am. >>Okay. So you knew the industry and that's cool that you wanted to give back because I mean obviously you just, in talking off camera, you're smart, you're very cogent and you know, a lot of times people in the private sector, they don't want to go work in the, in the public sector unless they're, unless they're power crazy, you know? Anyway, so speaking with David Nicholson, the experience has gone from really crappy to really great. I mean, take >>It from here. Yeah. Well, am I gonna be, I'm, because I'm from California, I was just, I was just, you know, we >>Got a dual case study >>Eloquently about, about the, the, the change that's happened just in, just in terms of simple things like a registration renewal. It used to be go online and pray and weed through things and now it's very simple, very, very fast. Tell us more about, about some of the things that you've done in the area of automation that have increased the percentage of things that could be done online without visiting a field office. Just as an >>Example. Yeah, what's the story? >>Yeah, so first of all, thank you for saying nice things about dmv, you as a customer. It means a lot because we have been very deliberately working towards solving all customer po pain points, whether it's in person experiences, online call centers, kiosks, so all across the channels. So we started our journey, myself and director Steve Gordon about three years ago, almost at the same time with the goal of making Department of Mo no motor vehicles in California as the best retail experience in the nation across industries. So that's our goal, right? Not there yet, but we are working towards it. So for, for our in person channels, which is what you may be familiar with, first of all, we wanna make sure brick and click and call all the customer journeys can be done across the channels. You can decide to start journey at one place, finish at another place. >>All that is very deliberate. We are also trying to make sure you don't have to come to field office at all. We would welcome you to come, we love you, but we don't want you to be there. You have better things to do for the economy. We want you to do that instead of showing up in the field office, being in the weight line. So that's number one. Creating more digital channels has been the key. We have created virtual field office. That's something that you would become familiar with if you are not as a DMV customer. During Covid, the goal was we provide almost all the services. We connect our technicians to the customer who are in need of a live conversation or a email or a text or a, or a SMS conversation or chat conversation in multiple languages or a video call, right? >>So we were able to accomplish that while Covid was going on, while the riots were going on. Those of your, you know about that, we, our offices were shut down. We created this channel, which we are continuing because it's a great disaster recovery business continuity channel, but also it can help keep people away from field office during peak hours. So that's been very deliberate. We have also added additional online services using bots. So we have created these web and process bots that actually let you do the intake, right? You, we could set up a new service in less than four weeks, a brand new service online. We have set up a brand new IVR service on call centers in less than a month for our seniors who didn't want to come to the field office and they were required certain pieces of information and we were able to provide that for our customers by creating this channel in less than less than four. >>And the pandemic was an accelerant to this was, was it the catalyst really? And then you guys compressed it? Or were, had you already started on the >>Well, we were >>Ready. I mean you, but you came on right? Just about just before the pandemic. >>Yeah. Yeah. So I came on in 2019, pandemic started in 2020 early. So we got lucky a little bit because we had a head start at, I was already working with u UI paths and we had come up with design patterns that we gonna take this journey for all DMV channels with using UiPath. So it was about timing that when it happened, it accelerated the need and it accelerated the actual work. I was thinking, I'll have a one year plan. I executed all of the one year plan items in less than two months out of necessity. So it accelerated definitely the execution of my plan. >>So when you talk about the chat channel, is that bots, is that humans or a combination? Yeah, >>It's a, it's a combination of it. I would say more AI than bots. Bots to the service fulfillment. So there is the user interaction where you have, you're saying something, the, the chat answers those questions, but then if you want something, hey, I want my, my registration renewed, right? It would take you to the right channel. And this is something we do today on our IVR channel. If you call in the DMV number in California, you'll see that your registration renewal is all automatic. You also have a AI listening to it. But also when you are saying, Yep, I wanna do it, then bot triggers certain aspects of the service fulfillment because our legacy is still sitting about 60 years old and we are able to still provide this modern facade for our customers with no gap and as quickly as possible within a month's time. How >>Many DMVs are in the state? >>Okay, so we have 230 different field locations out of which 180 are available for general public services. >>Okay. So and then you're, you're creating a digital overlay that's right >>To all of >>That, right? >>Yeah, it's digital and virtual overlay, right? Digital is fully self-service. Bots can do all your processing automation, can do all the processing. AI can do all the processing, but then you have virtual channels where you have customer interacting with the technicians or technicians virtually. But once a technician is done solving the problem, they click a button and bot does rest of the work for the technician. So that's where we are able to get some back office efficiency and transaction reduction. >>When was the last time you walked into a bank? >>Oh man. >>I mean, is that where we're going here where you just don't have to >>Go into the branch and that is the goal. In fact, we already have a starting point. I mean, just like you have ATM machines, we have kiosks already that do some of this automation work for us today. The goal is to not have to have to, unless you really want to, We actually set up these personas. One of them was high touch Henry. He likes to go to the field office and talk to people. We are there for them. But for the millennials, for the people who are like, I don't have time. I wanna like quickly finish this work off hours 24 by seven, which is where bots come in. They do not have weekends, HR complaint, they don't have overtime. They're able to solve these problems for me, 24 >>By seven. And what's the scope of your, like how many automations, how many bots? Can you give us a sense? >>Sure. So right now we are sitting at 36 different use cases. We have collected six point of eight point, well, we have saved 8.8 million just using the bots overall savings. If you were to look at virtual field office, which bots are part of, we have collected 388 million so far in that particular channel bots. I've also saved paper. I've saved a million sheets of paper through the bot, which I'm trying to remember how many trees it equates to, but it's a whole lot of trees that I've saved. And >>How many bots are we talking about? >>So it's 36 different use cases. So 36 >>Bots? >>Well, no, there's more bots I wanna say. So we are running at 85% efficiency, 50 bots. Oh wow. Yeah. >>Wow. Okay. So you, you asked the question about, you know, when was the last time someone was in a bank? The last time I was in a bank it was to deposit, you know, more than $10,000 in cash because of a cash transaction. Someone bought a car from me. It was more of a nuisance. I felt like I was being treated like a criminal. I was very clear what I was doing. I had just paid off a loan with that bank and I was giving them the cash for that transaction as opposed to the DMV transaction transferring title. That was easy. The DMV part was easier than the bank. And you're trying to make it even easier and it shouldn't, it shouldn't be that way. Yes. Right. But, but I, I have a, I have a question for you on, on that bot implementation. Can you give us, you've sort of give it us examples of how they interact. Yeah. But as your kind of prototypical California driver's license holder, how has that improved a specific transaction that I would be involved with? Can >>You, so well you as a Californian and you as a taxpayer, you as a Californian getting services and you as a taxpayer getting the most out of the money Okay. That the DMV spending on providing services, Right. Both are benefits to you. Sure. So bots have benefited in both of those areas. If you were used to the DMV three years ago, there was a whole lot of paper involved. You gotta fill this form out, you gotta fill this other form out and you gotta go to dmv. Oh by the way, your form, you didn't bring this thing with you. Your form has issues. We are calculated that about 30% of paper workloads are wasted because they just have bad data, right? There is no control. There's nobody telling you, hey, do this. Right. Even dates could be wrong, names could be wrong fields, maybe incomplete and such. >>So we were able to automate a whole lot of that by creating self-service channels, which are accelerated by bot. So we have these web acceleration platforms that collect the data, bots do the validation, they also verify the information, give you real time feedback or near real time feedback that hey, this is what you need to change. This is when you need to verify. So all the business rules are in the bot. And then once you're done, it'll commit the information to our legacy systems, which wouldn't have been possible unless a technician was punching it in manually. So there is a third cohort of Californians, which is our employees. We have 10,000 of those. They, I don't want them to get carpal tunnel. I want them to make sure they're spending more time thinking and helping our customers, looking at the customers rather than typing things. And that's what we are able to accomplish with the bots where you press that one button, which will have required maybe 50 more keystrokes and that's gone. And now you're saving time, you're also saving the effort and the attention loss of serving the best. >>Jay, what does it take to get a new process on board? So I'm thinking about real id, I just went through that in Massachusetts. I took, it was gonna be months to get to the dmv. So I ended up going through a aaa, had to get all these documents, I uploaded all the documents. Of course when I showed up, none were there. Thankfully I had backup copies. But it was really a pleasant experience. Are you, describe what you're doing with real ID and what role bots play? >>Yeah, sure. So with real id, what we are doing today and what I, what we'll be doing in the future, so I can talk about both. What we are doing today is that we are aligning most of the work to be done upfront by the customer. Because real ID is a complex transaction. You've gotta have four different pieces of documentation. You need to provide your information, it needs to match our records. And then you show up to the field office. And by the way, oh man, I did not upload this information. We are getting about 15 to 17% returns customers. And that's a whole lot of time. Every single mile our customer travels to the DMV office, which averages to about 13 miles. In my calculation for average customer, it's a dollar spent in carbon footprint in the time lost in the technician time trying to triage out some other things. So you're talking $26 per visit to the economy. >>Yeah. An amazing frustration, Yes. >>That has to come back and, and our customer satisfaction scores, which we really like to track, goes down right away. So in general, for real, id, what we have been, what we have done is created bunch of self-service channels, which are accelerated by workflow engines, by AI and by bots to collect the documentation, verify the documentation against external systems because we actually connect with Department of Homeland Security verify, you know, what's your passport about? We look at your picture and we verify that yep, it is truly a passport and yours and not your wives. Right? Or not a picture of a dog. And it's actually truly you, right? I mean, people do all kind of fun stuff by mistake or intentionally. So we wanna make sure we save time for our customer, we save time for our, for our employees, and we have zero returns required when employees, where customer shows up, which by the way is requirement right now. But the Department of Homeland Security is in a rule making process. And we are hopeful, very hopeful at this point in time that we'll be able to take the entire experience and get it done from home. And that'll give us a whole lot more efficiency, as you can imagine. And bots are at the tail end of it, committing all the data and transactions into our systems faster and with more accuracy. >>That's a great story. I mean, really congratulations and, and I guess I'll leave it. Last question is, where do you want to take this? What's the, what's your roadmap look like? What's your runway look like? Is it, is there endless opportunities to automate at the state or do you see a sort of light at the end of the tunnel? >>Sure. So there is a thing I shared in the previous session that I was in, which is be modern while we modernize. So that's been the goal with the bot. They are integral part of my transition architecture as I modernize the entire dmv, bring them from 90 60, bringing us from 1960 to 2022 or even 2025 and do it now, right? So bots are able to get me to a place where customers expectations are managed. They are getting their online, they're getting their mobile experience, they are avoiding making field off his trips and avoiding any kind of paper based processing right? For our employees and customers as well. So bots are serving that need today as part of the transition strategy going from 1960 to 2022 in the future. They're continue gonna continue to service. I think it's one thing that was talked about by the previous sessions today that we, they, they're looking at empowering the employees to do their own work back office work also in a full automation way and self-power them to automate their own processes. So that's one of the strategies we're gonna look for. But also we'll continue to have a strategy where we need to remain nimble with upcoming needs and have a faster go to market market plan using the bot. >>Outstanding. Well thanks so much for sharing your, your story and, and thanks for helping Dave. >>Real life testimony. I never, never thought I'd be coming on to praise the California dmv. Here I am and it's legit. Yeah, >>Well done. Can I, can I make an introduction to our Massachusetts colleagues? >>Good to, well actually we have, we have been working with state of New York, Massachusetts, Nevara, Arizona. So goal is to share but also learn from >>That. Help us out, help us out. >>But nice to be here, >>Great >>To have you and looking for feedback next time you was at dmv. >>All right. Oh, absolutely. Yeah. Get that, fill out that NPS score. All right. Thank you for watching. This is Dave Valante for Dave Nicholson. Forward five UI customer conference from the Venetian in Las Vegas. We'll be right back.

>>Yeah, yeah, yeah. We're back at the center of the coverage of the world 20 twenty-two, the first live event in three years. Pretty amazing. And I'm really excited to have Tony Coleman. Here is the c e o of those who changing the finance and banking industry. And this is the global head of industry solutions. That would be welcome. Back to the cube. Welcome. First time. Um, so thanks for coming on. Thank you. >>Thanks for having us, >>Tony. Tell us about what are you guys up to? Disrupting the finance world. >>So tomorrow is everyone's banking platform. So we are a software company. We have over 3000 financial institutions around the world. Marketing tell me that that works out is over 1.2 billion people rely on terminal software for their banking and financial needs. 41 of the top 50 banks in the world run software and we are very proud to be powering all of those entities on their innovation journeys and bringing you know, that digital transformation that we've seen so much all over the past few years and enabling a lot of the world's unbanked through digital banking become, you know, members of the >>community. So basically you're bringing the software platform to enable that to somebody you don't have to build it themselves because they never get there. Absolutely. And and so that's why I don't know if you consider that disruptive. I guess I do to the industry to a certain extent. But when you think of disruption in the business, you think of Blockchain and crypto, and 50 is that is completely separate world and you guys participate in that as well. Well, I >>would say it's related right? I mean, I was doing a podcast recently and they had this idea of, um, buzzword jail where you could choose words to go into jail and I said 50 not because I think they're intrinsically bad, but I think just at the moment they are a rife for scam area. I think it's one of those one of these technologies and investment area that people don't understand it, and there's a lot of a lot of mistakes that can be made in that, >>Yeah, >>I mean, it's a fascinating piece that it could be truly transformative if we get it right, but it's very emerging, so we'll see so don't play a huge part in the Blockchain industry directly. We work with partners in that space, but in terms of digital assets and that sort of thing. Yeah, absolutely. >>So, Boris, you have industry solutions in your title. What does that entail? So >>basically, I'm responsible for all the verticals, and that includes great partners like Tony. And we're doing a lot of verticals by now. When you listen. Today in all these various talks, we have so much stuff ranging from banking, go retail, healthcare, insurance, you name it, we have it by now. And that's obviously the clients moving from the edge solution. Like touching a little toe in the water, but longer to going all in building biggest solutions you saw on stage the lady from this morning. These are not second Great. Yeah, we do something small now. We're part of the transformation journey. And this is where Tony and I can regularly together how we transform things and how we built a new way of banking is done with Michael services and technology surrounding it. Yeah, >>but what about performance in this world? Can you tell me about that? >>Yeah. This is an interesting thing because people always challenging what is performance and document databases. And Tony challenged us actually, six weeks before his own show several weeks ago in London and says, Boris, let's do a benchmark And maybe you bring your story because if I get too excited, I follow. >>Yeah, sure, that performance and efficiency topics close close to my heart. I have been for for years. And so, yeah, we every two or three years, we run a high water. We've got a high water benchmark, and this year we sort of double down literally double down on everything we did previously. So this was 200 million accounts, 100 million customers, and we were thrashing through 102,800 seventy-five transactions a second, which is a phenomenal number. And, uh, >>can I do that on the Blockchain? >>Wow. Yeah, exactly. Right. So this is you know, I get asked why we do such high numbers and the reason is very straightforward. If somebody wants 10,000 transactions a second, we're seeing banks now that need that sort of thing. If I can give them a benchmark report, this is 100,000. I don't need to keep doing benchmarks. 10. >>Yeah. Tell me more about the Anytime you get into benchmarks, you want to understand the configuration. The workload. Tell me more about that. So we have >>a pretty well path of a standard transaction mix. We call it a retail transaction mix. And so it's the tries to the workload. Is that because it's a simulation right around what you would do in your daily basis? So you're going to make payments you're going to check? Your balance is you're going to see what he's moved on your account. So we do all of that and we run it through a proper production, good environment. And this is really important. This is something we do in the lab you couldn't go live on. This is all all of the horrible, non functional requirements around high availability, >>security, security passes, private wings, all these things. And one thing is, they're doing this for a long time. So this is not like let's define something new for the world. Now, this is something Tony's doing for literally 10, 15 years now, right? >>It was only 15 years, but this >>is your benchmark >>top >>developed Okay, >>so we run it through and, um yeah, some fantastic numbers. And not just on the share sort of top-level numbers 100,000 transactions. A second response time out of it was fantastic. One-millisecond, which is just brilliant. So it means you get these really efficient numbers what that helped us do with, you know, some of the other partners that are involved in the benchmark as well. It meant that our throughput court, which is a really good measure of efficiency, is up to four times better than we ran it three years ago. So in terms of a sustainability piece, which is so important that that's really a huge improvement, that's down to application changes, architect changes as well as using appropriate technology in the right place. >>How important? With things like the number, of course, the memory size is the block sizes. All that stuff. >>We are very tiny. So this is the part. When I talk to people, we have what we call a system in the back of people. Look at me. Um, how many transactions on that one? So, to be fair, three-quarters, we're going to be one quarter or something else because we're still putting some components of and start procedures for disclosure. But when I think Seventy-five 1000 transactions on a single single 80 system, which is thirty-two cause you're saying correctly, something like that. This is a tiny machine in the world of banking. So before this was the main friends and now it's wonderful instance on a W s. And this is really amazing. Costed and environmental footprint is so, so important >>and there's a heavy right heavy environment. >>So the the way we the way we architect the solution is it follows something called a command query responsibility, segregated segregation. So what we do, we do all the commands inappropriate database for that piece, and that was running at about Twenty-five 1000 transactions a second and then we're streaming the data out of that directly into So actually I was doing more than the Seventy-five 1000 queries. A second, which is the part of it was also investing Twenty-five 1000 transactions the second at the same time >>and okay, and the workload had a high locality medium locality. It was just give us a picture of what that's like. Sorry. So, >>yeah, >>we don't have that. Yeah, >>so explain that That's not That's not the mindset for a document. Exactly. >>Exactly. In the document database, you don't have the hot spotting the one single field off the table, which is suddenly hot spotting. And now you have literally and recovery comes up and we say, What goes, goes together, get together belongs together, comes out together. So the number of, for example, it's much, much smaller and the document system, then historically, relationship. >>So it is not a good good indicator, necessarily >>anymore. That's what this is so much reduced. The number of access patterns are smaller, and I mean it is highly optimized, for example, internally as well. The internal structures, so that was very close to a >>traditional benchmark, would have a cash in front of a high cash rate. So 100 and 99% right, That's a high locality reference. But that's that's irrelevant. >>It's gone. There's no cashing in the middle anymore. It goes straight against the database. All these things are out, and that's what makes it so exciting and all the things in a real environment. I think we really need to stress it. It's not a test that at home. It's a real life environment out into the wild with the benchmark driving and driving. >>How did your customers respond? You did this for your recent event? >>Yeah, we did it for our use. A conference, our community for, um, which was a few weeks ago in London. Um, and the You know, the reaction was Certainly it was a great reception, of course, but the main thing that people are fascinated about, how much more efficient the whole platform it's explaining. So you know when we can run and it's a great number that we've got the team pulled out, which is so having doubled throughput on the platform from what we did three years ago, we're actually using 20% less infrastructure to give double the performance. Uh, macro-level, that's a phenomenal achievement. And that means that these changes that we make everything that we're doing benefits all of our customers. So all of the banks, when they take the latest release, is they get these benefits. Everything is that much more efficient. So everybody benefits from every investment, >>and this was running in the cloud. Is that correct? You're running out of this. >>So this was list, Um, 80 on a W s with a W s cases and processes. And so it was a really reality driven environment, >>pure pure cloud-native or using mana services on a W s. And then at least for the peace. It's >>awesome. I mean, uh, So now how convenient for the timing from, uh, the world. How are you socializing with your community? >>We're having this afternoon session as well, where we talk a little bit more detail about that, and he has a session as well tomorrow. So we see a lot of good feedback as well when we bring it up with clients. Obviously some clients get very specific because this reduction footprint is so huge when you think a client has 89 environments from early development systems to production to emergency standby, maybe a different cloud. All these things what day talks about the different Atlas features multi cloud environmentally. All this stuff comes to play. And this is why I'm so excited to work with them. We should bring up as well the other things which are available to ready already with your front and solutions with Infinity services because that's the other part of the modernization, the Michael Services, which Tony so politely not mentioning. So there's a lot of cool technology into that one, which fits to how it works in micros services. Happy I first all these what they called factors. Micro service a p. I cloud-native headless. I think that was the right order now. So all these things are reflected as well. But with their leadership chief now, I think a lot of companies have to play Catch-up now to what Tony and his team are delivering on the bank. This >>gets the modernization. We really haven't explicitly talks about that. Everything you've just said talks to modernization. So you typically in financial services find a lot of relation. Database twenty-year-old, hardened, etcetera, high availability. Give them credit for that. But a lot of times you'll see them just shift that into the cloud. You guys chose not to do that. What was the modernization journey look like? >>So it's a bit of, um yeah, a firm believer in pragmatism and using. I think you touched on earlier the appropriate technology. So >>horses for courses >>exactly right out of my mouth. And I was talking to one of the uh, the investor analysts earlier. And you know, the exact same question comes up, right? So if you've got a relation database or you've got a big legacy system and you're not gonna mainframe or whatever it is and you wanna pull that over when you it's not just a case of moving the data model from one paradigm to another. You need to look at it holistically, and you need to be ambitious. I think the industry has got, you know, quite nervous about some of these transformation projects, but in some ways it might be counter intuitive. I think being ambitious and being in bold is a better way. Better way through, you know, take take of you, look at it holistically. Layout of plan. It is hard. It is hard to do these sorts of transformations, but that's what makes it the challenge. That's what makes it fun. Take take those bold steps. Look at it holistically. Look at the end state and then work out a practical way. You can deliver value to the business and your customers as you deliver on the road. So >>did you migrate from a traditional R D B. M s to go. >>So So, Yeah, this is a conversation. So, uh, in the late nineties, the kind of the phrase document model hasn't really been coined yet. And for some of our work at the time, we refer to as a hierarchical model. Um, And at that point in time, really, if you wanted to sell to a bank, you needed to be running Oracle. So we took this data model and we got it running an article and then other relational databases as well, but actually under the colors there it is, sort of as well. So there is a project that we're looking at to say Well, okay, taking that model, which is in a relational database. And of course, you build over time, you do rely on some of the features of relations databases moving that over to something like, isn't it? You know, it's not quite as simple as just changing the data model. Um, so there's a few bits and pieces that we need to work through, but there is a concept that we are running, which is looking really promising and spurred on by the amazing results from the benchmark. That could be something That's really >>yeah, I think you know, 20 years ago you probably wouldn't even thought about it. It's just too risky. But today, with the modern tools and the cloud and you're talking about micro services and containers, it becomes potentially more feasible. >>But the other side of it is, you know, it's only relatively recently the Mongo who's had transaction support across multiple document multi collection transactions and in banking. As we all know, you know, it's highly regulated. That is, all of your worst possible non functional requirement. Security transaction reality. Thomas City You know, the whole the whole shebang. Your worst possible nightmare is Monday morning for >>us. So and I think one part which is exciting about this Tony is a very good practical example about this large scale modernization and cutting out by cutting off that layer and going back to the hierarchical internal structures. We're simply find a lot of the backing components of our because obviously translation which was done before, it's not need it anymore. And that is as well for me, an exciting example to see how long it takes what it is. So Tony space in my life experiments so to speak >>well, you're right because it used to be those migrations. Where how many line of code? How long do I have to freeze it? And that a lot of times lead people to say, Well, forget it, because the business is going to shut down. >>But now we do that. We do that. So I'm working, obviously, besides the work with a lot of financial clients, and but now it's my job is normally shift and left a pain in the game because the result of the work is when they move everything to the cloud and it was bad before. It will not be better in the cloud only because it's in somebody else's data center. So these modernization and innovation factor is absolutely critical. And it's only said that people get it by now. This shift and left over it is how can I innovate? How can accelerate innovation, and that leads very quickly to the document model discussion. >>Yeah, I think the world practitioners will tell you, if you really want to affect the operational model, have a meaningful impact on your business. You have to really modernized. You can't just lift shift that they're absolutely. You know, what's the difference between hundreds of millions or billions in some cases, versus, you know, some nice little hits here or there. >>So we see as well a lot of clients asking for solutions like the terminal solutions. And like others where there is not anymore discussion about how to move to the The question is how fast how can accelerate. We see the services request the first one. It's amazing. After the event, what we had in London, 100 clients calling us. So it's not our sales people calling upon the clients, the clients coming in. I saw it. How do we get started? And that is for me, from the vendor perspective, so to speak. Amazing moment >>yourself. You go, guys, we're gonna go. Thanks so much for that. You have to have you back and see how that goes. That. Yeah, that's a big story of if you're a great All right, keep it right there. Everybody will be right back. This is David for the Cube. You're watching our live coverage of mongo D B World 20 twenty-two from New York City. >>Yeah, >>Yeah, yeah, yeah, yeah

>>Everyone wants a cloud operating model. Since the introduction of the modern cloud. Last decade, the entire technology landscape has changed. We've learned a lot from the hyperscalers, especially from AWS. Now, one thing is certain in the technology business. It's so competitive. Then if a faster, better, cheaper idea comes along, the industry will move quickly to adopt it. They'll add their unique value and then they'll bring solutions to the market. And that's precisely what's happening throughout the technology industry because of cloud. And one of the best examples is Amazon's nitro. That's AWS has custom built hypervisor that delivers on the promise of more efficiently using resources and expanding things like processor, optionality for customers. It's a secret weapon for Amazon. As, as we, as we wrote last year, every infrastructure company needs something like nitro to compete. Why do we say this? Well, Wiki Bon our research arm estimates that nearly 30% of CPU cores in the data center are wasted. >>They're doing work that they weren't designed to do well, specifically offloading networking, storage, and security tasks. So if you can eliminate that waste, you can recapture dollars that drop right to the bottom line. That's why every company needs a nitro like solution. As a result of these developments, customers are rethinking networks and how they utilize precious compute resources. They can't, or won't put everything into the public cloud for many reasons. That's one of the tailwinds for tier two cloud service providers and why they're growing so fast. They give options to customers that don't want to keep investing in building out their own data centers, and they don't want to migrate all their workloads to the public cloud. So these providers and on-prem customers, they want to be more like hyperscalers, right? They want to be more agile and they do that. They're distributing, networking and security functions and pushing them closer to the applications. >>Now, at the same time, they're unifying their view of the network. So it can be less fragmented, manage more efficiently with more automation and better visibility. How are they doing this? Well, that's what we're going to talk about today. Welcome to changing the game for cloud networking made possible by pluribus networks. My name is Dave Vellante and today on this special cube presentation, John furrier, and I are going to explore these issues in detail. We'll dig into new solutions being created by pluribus and Nvidia to specifically address offloading, wasted resources, accelerating performance, isolating data, and making networks more secure all while unifying the network experience. We're going to start on the west coast and our Palo Alto studios, where John will talk to Mike of pluribus and AMI, but Donnie of Nvidia, then we'll bring on Alessandra Bobby airy of pluribus and Pete Lummus from Nvidia to take a deeper dive into the technology. And then we're gonna bring it back here to our east coast studio and get the independent analyst perspective from Bob Liberte of the enterprise strategy group. We hope you enjoy the program. Okay, let's do this over to John >>Okay. Let's kick things off. We're here at my cafe. One of the TMO and pluribus networks and NAMI by Dani VP of networking, marketing, and developer ecosystem at Nvidia. Great to have you welcome folks. >>Thank you. Thanks. >>So let's get into the, the problem situation with cloud unified network. What problems are out there? What challenges do cloud operators have Mike let's get into it. >>Yeah, it really, you know, the challenges we're looking at are for non hyperscalers that's enterprises, governments, um, tier two service providers, cloud service providers, and the first mandate for them is to become as agile as a hyperscaler. So they need to be able to deploy services and security policies. And second, they need to be able to abstract the complexity of the network and define things in software while it's accelerated in hardware. Um, really ultimately they need a single operating model everywhere. And then the second thing is they need to distribute networking and security services out to the edge of the host. Um, we're seeing a growth in cyber attacks. Um, it's, it's not slowing down. It's only getting worse and, you know, solving for this security problem across clouds is absolutely critical. And the way to do it is to move security out to the host. >>Okay. With that goal in mind, what's the pluribus vision. How does this tie together? >>Yeah. So, um, basically what we see is, uh, that this demands a new architecture and that new architecture has four tenants. The first tenant is unified and simplified cloud networks. If you look at cloud networks today, there's, there's sort of like discreet bespoke cloud networks, you know, per hypervisor, per private cloud edge cloud public cloud. Each of the public clouds have different networks that needs to be unified. You know, if we want these folks to be able to be agile, they need to be able to issue a single command or instantiate a security policy across all those locations with one command and not have to go to each one. The second is like I mentioned, distributed security, um, distributed security without compromise, extended out to the host is absolutely critical. So micro-segmentation and distributed firewalls, but it doesn't stop there. They also need pervasive visibility. >>You know, it's, it's, it's sort of like with security, you really can't see you can't protect what you can't see. So you need visibility everywhere. The problem is visibility to date has been very expensive. Folks have had to basically build a separate overlay network of taps, packet brokers, tap aggregation infrastructure that really needs to be built into this unified network I'm talking about. And the last thing is automation. All of this needs to be SDN enabled. So this is related to my comment about abstraction abstract, the complexity of all of these discreet networks, physic whatever's down there in the physical layer. Yeah. I don't want to see it. I want to abstract it. I wanted to find things in software, but I do want to leverage the power of hardware to accelerate that. So that's the fourth tenant is SDN automation. >>Mike, we've been talking on the cube a lot about this architectural shift and customers are looking at this. This is a big part of everyone who's looking at cloud operations next gen, how do we get there? How do customers get this vision realized? >>That's a great question. And I appreciate the tee up. I mean, we're, we're here today for that reason. We're introducing two things today. Um, the first is a unified cloud networking vision, and that is a vision of where pluribus is headed with our partners like Nvidia longterm. Um, and that is about, uh, deploying a common operating model, SDN enabled SDN, automated hardware, accelerated across all clouds. Um, and whether that's underlying overlay switch or server, um, hype, any hypervisor infrastructure containers, any workload doesn't matter. So that's ultimately where we want to get. And that's what we talked about earlier. Um, the first step in that vision is what we call the unified cloud fabric. And this is the next generation of our adaptive cloud fabric. Um, and what's nice about this is we're not starting from scratch. We have a, a, an award-winning adaptive cloud fabric product that is deployed globally. Um, and in particular, uh, we're very proud of the fact that it's deployed in over a hundred tier one mobile operators as the network fabric for their 4g and 5g virtualized cores. We know how to build carrier grade, uh, networking infrastructure, what we're doing now, um, to realize this next generation unified cloud fabric is we're extending from the switch to this Nvidia Bluefield to DPU. We know there's a, >>Hold that up real quick. That's a good, that's a good prop. That's the blue field and video. >>It's the Nvidia Bluefield two DPU data processing unit. And, um, uh, you know, what we're doing, uh, fundamentally is extending our SDN automated fabric, the unified cloud fabric out to the host, but it does take processing power. So we knew that we didn't want to do, we didn't want to implement that running on the CPU, which is what some other companies do because it consumes revenue generating CPU's from the application. So a DPU is a perfect way to implement this. And we knew that Nvidia was the leader with this blue field too. And so that is the first that's, that's the first step in the getting into realizing this vision. >>I mean, Nvidia has always been powering some great workloads of GPU. Now you've got DPU networking and then video is here. What is the relationship with clothes? How did that come together? Tell us the story. >>Yeah. So, you know, we've been working with pluribus for quite some time. I think the last several months was really when it came to fruition and, uh, what pluribus is trying to build and what Nvidia has. So we have, you know, this concept of a Bluefield data processing unit, which if you think about it, conceptually does really three things, offload, accelerate an isolate. So offload your workloads from your CPU to your data processing unit infrastructure workloads that is, uh, accelerate. So there's a bunch of acceleration engines. So you can run infrastructure workloads much faster than you would otherwise, and then isolation. So you have this nice security isolation between the data processing unit and your other CPU environment. And so you can run completely isolated workloads directly on the data processing unit. So we introduced this, you know, a couple of years ago, and with pluribus, you know, we've been talking to the pluribus team for quite some months now. >>And I think really the combination of what pluribus is trying to build and what they've developed around this unified cloud fabric, uh, is fits really nicely with the DPU and running that on the DPU and extending it really from your physical switch, all the way to your host environment, specifically on the data processing unit. So if you think about what's happening as you add data processing units to your environment. So every server we believe over time is going to have data processing units. So now you'll have to manage that complexity from the physical network layer to the host layer. And so what pluribus is really trying to do is extending the network fabric from the host, from the switch to the host, and really have that single pane of glass for network operators to be able to configure provision, manage all of the complexity of the network environment. >>So that's really how the partnership truly started. And so it started really with extending the network fabric, and now we're also working with them on security. So, you know, if you sort of take that concept of isolation and security isolation, what pluribus has within their fabric is the concept of micro-segmentation. And so now you can take that extended to the data processing unit and really have, um, isolated micro-segmentation workloads, whether it's bare metal cloud native environments, whether it's virtualized environments, whether it's public cloud, private cloud hybrid cloud. So it really is a magical partnership between the two companies with their unified cloud fabric running on, on the DPU. >>You know, what I love about this conversation is it reminds me of when you have these changing markets, the product gets pulled out of the market and, and you guys step up and create these new solutions. And I think this is a great example. So I have to ask you, how do you guys differentiate what sets this apart for customers with what's in it for the customer? >>Yeah. So I mentioned, you know, three things in terms of the value of what the Bluefield brings, right? There's offloading, accelerating, isolating, that's sort of the key core tenants of Bluefield. Um, so that, you know, if you sort of think about what, um, what Bluefields, what we've done, you know, in terms of the differentiation, we're really a robust platform for innovation. So we introduced Bluefield to, uh, last year, we're introducing Bluefield three, which is our next generation of Bluefields, you know, we'll have five X, the arm compute capacity. It will have 400 gig line rate acceleration, four X better crypto acceleration. So it will be remarkably better than the previous generation. And we'll continue to innovate and add, uh, chips to our portfolio every, every 18 months to two years. Um, so that's sort of one of the key areas of differentiation. The other is the, if you look at Nvidia and, and you know, what we're sort of known for is really known for our AI artificial intelligence and our artificial intelligence software, as well as our GPU. >>So you look at artificial intelligence and the combination of artificial intelligence plus data processing. This really creates the, you know, faster, more efficient, secure AI systems from the core of your data center, all the way out to the edge. And so with Nvidia, we really have these converged accelerators where we've combined the GPU, which does all your AI processing with your data processing with the DPU. So we have this convergence really nice convergence of that area. And I would say the third area is really around our developer environment. So, you know, one of the key, one of our key motivations at Nvidia is really to have our partner ecosystem, embrace our technology and build solutions around our technology. So if you look at what we've done with the DPU, with credit and an SDK, which is an open SDK called Doka, and it's an open SDK for our partners to really build and develop solutions using Bluefield and using all these accelerated libraries that we expose through Doka. And so part of our differentiation is really building this open ecosystem for our partners to take advantage and build solutions around our technology. >>You know, what's exciting is when I hear you talk, it's like you realize that there's no one general purpose network anymore. Everyone has their own super environment Supercloud or these new capabilities. They can really craft their own, I'd say, custom environment at scale with easy tools. Right. And it's all kind of, again, this is the new architecture Mike, you were talking about, how does customers run this effectively? Cost-effectively and how do people migrate? >>Yeah, I, I think that is the key question, right? So we've got this beautiful architecture. You, you know, Amazon nitro is a, is a good example of, of a smart NIC architecture that has been successfully deployed, but enterprises and serve tier two service providers and tier one service providers and governments are not Amazon, right? So they need to migrate there and they need this architecture to be cost-effective. And, and that's, that's super key. I mean, the reality is deep user moving fast, but they're not going to be, um, deployed everywhere on day one. Some servers will have DPS right away, some servers will have use and a year or two. And then there are devices that may never have DPS, right. IOT gateways, or legacy servers, even mainframes. Um, so that's the beauty of a solution that creates a fabric across both the switch and the DPU, right. >>Um, and by leveraging the Nvidia Bluefield DPU, what we really like about it is it's open. Um, and that drives, uh, cost efficiencies. And then, um, uh, you know, with this, with this, our architectural approach effectively, you get a unified solution across switch and DPU workload independent doesn't matter what hypervisor it is, integrated visibility, integrated security, and that can, uh, create tremendous cost efficiencies and, and really extract a lot of the expense from, from a capital perspective out of the network, as well as from an operational perspective, because now I have an SDN automated solution where I'm literally issuing a command to deploy a network service or to create or deploy our security policy and is deployed everywhere, automatically saving the oppor, the network operations team and the security operations team time. >>All right. So let me rewind that because that's super important. Get the unified cloud architecture, I'm the customer guy, but it's implemented, what's the value again, take, take me through the value to me. I have a unified environment. What's the value. >>Yeah. So I mean, the value is effectively, um, that, so there's a few pieces of value. The first piece of value is, um, I'm creating this clean D mark. I'm taking networking to the host. And like I mentioned, we're not running it on the CPU. So in implementations that run networking on the CPU, there's some conflict between the dev ops team who owned the server and the NetApps team who own the network because they're installing software on the, on the CPU stealing cycles from what should be revenue generating. Uh CPU's. So now by, by terminating the networking on the DPU, we click create this real clean DMARC. So the dev ops folks are happy because they don't necessarily have the skills to manage network and they don't necessarily want to spend the time managing networking. They've got their network counterparts who are also happy the NetApps team, because they want to control the networking. >>And now we've got this clean DMARC where the DevOps folks get the services they need and the NetApp folks get the control and agility they need. So that's a huge value. Um, the next piece of value is distributed security. This is essential. I mentioned earlier, you know, put pushing out micro-segmentation and distributed firewall, basically at the application level, right, where I create these small, small segments on an by application basis. So if a bad actor does penetrate the perimeter firewall, they're contained once they get inside. Cause the worst thing is a bad actor, penetrates a perimeter firewall and can go wherever they want and wreak havoc. Right? And so that's why this, this is so essential. Um, and the next benefit obviously is this unified networking operating model, right? Having, uh, uh, uh, an operating model across switch and server underlay and overlay, workload agnostic, making the life of the NetApps teams much easier so they can focus their time on really strategy instead of spending an afternoon, deploying a single villain, for example. >>Awesome. And I think also from my standpoint, I mean, perimeter security is pretty much, I mean, they're out there, it gets the firewall still out there exists, but pretty much they're being breached all the time, the perimeter. So you have to have this new security model. And I think the other thing that you mentioned, the separation between dev ops is cool because the infrastructure is code is about making the developers be agile and build security in from day one. So this policy aspect is, is huge. Um, new control points. I think you guys have a new architecture that enables the security to be handled more flexible. >>Right. >>That seems to be the killer feature here, >>Right? Yeah. If you look at the data processing unit, I think one of the great things about sort of this new architecture, it's really the foundation for zero trust it's. So like you talked about the perimeter is getting breached. And so now each and every compute node has to be protected. And I think that's sort of what you see with the partnership between pluribus and Nvidia is the DPU is really the foundation of zero trust. And pluribus is really building on that vision with, uh, allowing sort of micro-segmentation and being able to protect each and every compute node as well as the underlying network. >>This is super exciting. This is an illustration of how the market's evolving architectures are being reshaped and refactored for cloud scale and all this new goodness with data. So I gotta ask how you guys go into market together. Michael, start with you. What's the relationship look like in the go to market with an Nvidia? >>Sure. Um, I mean, we're, you know, we're super excited about the partnership, obviously we're here together. Um, we think we've got a really good solution for the market, so we're jointly marketing it. Um, uh, you know, obviously we appreciate that Nvidia is open. Um, that's, that's sort of in our DNA, we're about open networking. They've got other ISV who are gonna run on Bluefield too. We're probably going to run on other DPS in the, in the future, but right now, um, we're, we feel like we're partnered with the number one, uh, provider of DPS in the world and, uh, super excited about, uh, making a splash with it. >>I'm in get the hot product. >>Yeah. So Bluefield too, as I mentioned was GA last year, we're introducing, uh, well, we now also have the converged accelerator. So I talked about artificial intelligence or artificial intelligence with the Bluefield DPU, all of that put together on a converged accelerator. The nice thing there is you can either run those workloads. So if you have an artificial intelligence workload and an infrastructure workload, you can warn them separately on the same platform or you can actually use, uh, you can actually run artificial intelligence applications on the Bluefield itself. So that's what the converged accelerator really brings to the table. Uh, so that's available now. Then we have Bluefield three, which will be available late this year. And I talked about sort of, you know, uh, how much better that next generation of Bluefield is in comparison to Bluefield two. So we will see Bluefield three shipping later on this year, and then our software stack, which I talked about, which is called Doka we're on our second version are Doka one dot two. >>We're releasing Doka one dot three, uh, in about two months from now. And so that's really our open ecosystem framework. So allow you to program the Bluefields. So we have all of our acceleration libraries, um, security libraries, that's all packed into this STK called Doka. And it really gives that simplicity to our partners to be able to develop on top of Bluefield. So as we add new generations of Bluefield, you know, next, next year, we'll have, you know, another version and so on and so forth Doka is really that unified unified layer that allows, um, Bluefield to be both forwards compatible and backwards compatible. So partners only really have to think about writing to that SDK once, and then it automatically works with future generations of Bluefields. So that's sort of the nice thing around, um, around Doka. And then in terms of our go to market model, we're working with every, every major OEM. So, uh, later on this year, you'll see, you know, major server manufacturers, uh, releasing Bluefield enabled servers. So, um, more to come >>Awesome, save money, make it easier, more capabilities, more workload power. This is the future of, of cloud operations. >>Yeah. And, and, and, uh, one thing I'll add is, um, we are, um, we have a number of customers as you'll hear in the next segment, um, that are already signed up and we'll be working with us for our, uh, early field trial starting late April early may. Um, we are accepting registrations. You can go to www.pluribusnetworks.com/e F T a. If you're interested in signing up for, um, uh, being part of our field trial and providing feedback on the product, >>Awesome innovation and network. Thanks so much for sharing the news. Really appreciate it. Thanks so much. Okay. In a moment, we'll be back to look deeper in the product, the integration security zero trust use cases. You're watching the cube, the leader in enterprise tech coverage, >>Cloud networking is complex and fragmented slowing down your business. How can you simplify and unify your cloud networks to increase agility and business velocity? >>Pluribus unified cloud networking provides a unified simplify and agile network fabric across all clouds. It brings the simplicity of a public cloud operation model to private clouds, dramatically reducing complexity and improving agility, availability, and security. Now enterprises and service providers can increase their business philosophy and delight customers in the distributed multi-cloud era. We achieve this with a new approach to cloud networking, pluribus unified cloud fabric. This open vendor, independent network fabric, unifies, networking, and security across distributed clouds. The first step is extending the fabric to servers equipped with data processing units, unifying the fabric across switches and servers, and it doesn't stop there. The fabric is unified across underlay and overlay networks and across all workloads and virtualization environments. The unified cloud fabric is optimized for seamless migration to this new distributed architecture, leveraging the power of the DPU for application level micro-segmentation distributed fireball and encryption while still supporting those servers and devices that are not equipped with a DPU. Ultimately the unified cloud fabric extends seamlessly across distributed clouds, including central regional at edge private clouds and public clouds. The unified cloud fabric is a comprehensive network solution. That includes everything you need for clouds, networking built in SDN automation, distributed security without compromises, pervasive wire speed, visibility and application insight available on your choice of open networking switches and DP use all at the lowest total cost of ownership. The end result is a dramatically simplified unified cloud networking architecture that unifies your distributed clouds and frees your business to move at cloud speed, >>To learn more, visit www.pluribusnetworks.com. >>Okay. We're back I'm John ferry with the cube, and we're going to go deeper into a deep dive into unified cloud networking solution from Clovis and Nvidia. And we'll examine some of the use cases with Alessandra Burberry, VP of product management and pullovers networks and Pete Bloomberg who's director of technical marketing and video remotely guys. Thanks for coming on. Appreciate it. >>Yeah. >>So deep dive, let's get into the what and how Alexandra we heard earlier about the pluribus Nvidia partnership and the solution you're working together on what is it? >>Yeah. First let's talk about the water. What are we really integrating with the Nvidia Bluefield, the DPO technology, uh, plugable says, um, uh, there's been shipping, uh, in, uh, in volume, uh, in multiple mission critical networks. So this advisor one network operating systems, it runs today on a merchant silicone switches and effectively it's a standard open network operating system for data center. Um, and the novelty about this system that integrates a distributed control plane for, at water made effective in SDN overlay. This automation is a completely open and interoperable and extensible to other type of clouds is not enclosed them. And this is actually what we're now porting to the Nvidia DPO. >>Awesome. So how does it integrate into Nvidia hardware and specifically how has pluribus integrating its software with the Nvidia hardware? >>Yeah, I think, uh, we leverage some of the interesting properties of the Bluefield, the DPO hardware, which allows actually to integrate, uh, um, uh, our software, our network operating system in a manner which is completely isolated and independent from the guest operating system. So the first byproduct of this approach is that whatever we do at the network level on the DPU card that is completely agnostic to the hypervisor layer or OSTP layer running on, uh, on the host even more, um, uh, we can also independently manage this network, know that the switch on a Neek effectively, um, uh, managed completely independently from the host. You don't have to go through the network operating system, running on x86 to control this network node. So you throw yet the experience effectively of a top of rack for virtual machine or a top of rack for, uh, Kubernetes bots, where instead of, uh, um, if you allow me with the analogy instead of connecting a server knee directly to a switchboard, now you're connecting a VM virtual interface to a virtual interface on the switch on an ache. >>And, uh, also as part of this integration, we, uh, put a lot of effort, a lot of emphasis in, uh, accelerating the entire, uh, data plane for networking and security. So we are taking advantage of the DACA, uh, Nvidia DACA API to program the accelerators. And these accomplished two things with that. Number one, uh, you, uh, have much greater performance, much better performance. They're running the same network services on an x86 CPU. And second, this gives you the ability to free up, I would say around 20, 25% of the server capacity to be devoted either to, uh, additional workloads to run your cloud applications, or perhaps you can actually shrink the power footprint and compute footprint of your data center by 20%, if you want to run the same number of compute workloads. So great efficiencies in the overall approach, >>And this is completely independent of the server CPU, right? >>Absolutely. There is zero code from running on the x86, and this is what we think this enables a very clean demarcation between computer and network. >>So Pete, I gotta get, I gotta get you in here. We heard that, uh, the DPU is enabled cleaner separation of dev ops and net ops. Can you explain why that's important because everyone's talking DevSecOps right now, you've got net ops, net, net sec ops, this separation. Why is this clean separation important? >>Yeah, I think it's a, you know, it's a pragmatic solution in my opinion. Um, you know, we wish the world was all kind of rainbows and unicorns, but it's a little, a little messier than that. And I think a lot of the dev ops stuff and that, uh, mentality and philosophy, there's a natural fit there. Right? You have applications running on servers. So you're talking about developers with those applications integrating with the operators of those servers. Well, the network has always been this other thing and the network operators have always had a very different approach to things than compute operators. And, you know, I think that we, we in the networking industry have gotten closer together, but there's still a gap there's still some distance. And I think in that distance, isn't going to be closed. And so, you know, again, it comes down to pragmatism and I think, you know, one of my favorite phrases is look good fences, make good neighbors. And that's what this is. >>Yeah. That's a great point because dev ops has become kind of the calling card for cloud, right. But dev ops is as simply infrastructure as code and infrastructure is networking, right? So if infrastructure is code, you know, you're talking about, you know, that part of the stack under the covers under the hood, if you will, this is super important distinction. And this is where the innovation is. Can you elaborate on how you see that? Because this is really where the action is right now. >>Yeah, exactly. And I think that's where, um, one from, from the policy, the security that the zero trust aspect of this, right? If you get it wrong on that network side, all of a sudden you, you can totally open up that those capabilities. And so security is part of that. But the other part is thinking about this at scale, right? So we're taking one top of rack switch and adding, you know, up to 48 servers per rack. And so that ability to automate, orchestrate and manage at scale becomes absolutely critical. >>I'll Sandra, this is really the why we're talking about here, and this is scale. And again, getting it right. If you don't get it right, you're going to be really kind of up, you know what you know, so this is a huge deal. Networking matters, security matters, automation matters, dev ops, net ops, all coming together, clean separation, um, help us understand how this joint solution with Nvidia fits into the pluribus unified cloud networking vision, because this is what people are talking about and working on right now. >>Yeah, absolutely. So I think here with this solution, we're attacking two major problems in cloud networking. One is, uh, operation of, uh, cloud networking. And the second is a distributing security services in the cloud infrastructure. First, let me talk about the first water. We really unifying. If we're unifying something, something must be at least fragmented or this jointed and the, what is this joint that is actually the network in the cloud. If you look holistically, how networking is deployed in the cloud, you have your physical fabric infrastructure, right? Your switches and routers, you'll build your IP clause fabric leaf in spine typologies. This is actually a well understood the problem. I, I would say, um, there are multiple vendors, uh, uh, with, uh, um, uh, let's say similar technologies, um, very well standardized, whether you will understood, um, and almost a commodity, I would say building an IP fabric these days, but this is not the place where you deploy most of your services in the cloud, particularly from a security standpoint, two services are actually now moved into the compute layer where you actually were called builders, have to instrument the, a separate, uh, network virtualization layer, where they deploy segmentation and security closer to the workloads. >>And this is where the complication arise. These high value part of the cloud network is where you have a plethora of options that they don't talk to each other. And they are very dependent on the kind of hypervisor or compute solution you choose. Um, for example, the networking API to be between an GSXI environment or an hyper V or a Zen are completely disjointed. You have multiple orchestration layers. And when, and then when you throw in also Kubernetes in this, in this, in this type of architecture, uh, you're introducing yet another level of networking. And when Kubernetes runs on top of VMs, which is a prevalent approach, you actually just stacking up multiple networks on the compute layer that they eventually run on the physical fabric infrastructure. Those are all ships in the nights effectively, right? They operate as completely disjointed. And we're trying to attack this problem first with the notion of a unified fabric, which is independent from any workloads, whether it's this fabric spans on a switch, which can be con connected to a bare metal workload, or can span all the way inside the DPU, uh, where, um, you have, uh, your multi hypervisor compute environment. >>It's one API, one common network control plane, and one common set of segmentation services for the network. That's probably the number one, >>You know, it's interesting you, man, I hear you talking, I hear one network month, different operating models reminds me of the old serverless days. You know, there's still servers, but they call it serverless. Is there going to be a term network list? Because at the end of the day, it should be one network, not multiple operating models. This, this is a problem that you guys are working on. Is that right? I mean, I'm not, I'm just joking server listen network list, but the idea is it should be one thing. >>Yeah, it's effectively. What we're trying to do is we are trying to recompose this fragmentation in terms of network operation, across physical networking and server networking server networking is where the majority of the problems are because of the, uh, as much as you have standardized the ways of building, uh, physical networks and cloud fabrics with IP protocols and internet, you don't have that kind of, uh, uh, sort of, uh, um, um, uh, operational efficiency, uh, at the server layer. And, uh, this is what we're trying to attack first. The, with this technology, the second aspect we're trying to attack is are we distribute the security services throughout the infrastructure, more efficiently, whether it's micro-segmentation is a stateful firewall services, or even encryption. Those are all capabilities enabled by the blue field, uh, uh, the Butte technology and, uh, uh, we can actually integrate those capabilities directly into the nettle Fabrica, uh, limiting dramatically, at least for east-west traffic, the sprawl of, uh, security appliances, whether virtual or physical, that is typically the way the people today, uh, segment and secure the traffic in the cloud. >>Awesome. Pete, all kidding aside about network lists and serverless kind of fun, fun play on words there, the network is one thing it's basically distributed computing, right? So I love to get your thoughts about this distributed security with zero trust as the driver for this architecture you guys are doing. Can you share in more detail the depth of why DPU based approach is better than alternatives? >>Yeah, I think what's, what's beautiful and kind of what the DPU brings. That's new to this model is a completely isolated compute environment inside. So, you know, it's the, uh, yo dog, I heard you like a server, so I put a server inside your server. Uh, and so we provide, uh, you know, armed CPU's memory and network accelerators inside, and that is completely isolated from the host. So the server, the, the actual x86 host just thinks it has a regular Nick in there, but you actually have this full control plane thing. It's just like taking your top of rack switch and shoving it inside of your compute node. And so you have not only the separation, um, within the data plane, but you have this complete control plane separation. So you have this element that the network team can now control and manage, but we're taking all of the functions we used to do at the top of rack switch, and we're just shooting them now. >>And, you know, as time has gone on we've, we've struggled to put more and more and more into that network edge. And the reality is the network edge is the compute layer, not the top of rack switch layer. And so that provides this phenomenal enforcement point for security and policy. And I think outside of today's solutions around virtual firewalls, um, the other option is centralized appliances. And even if you can get one that can scale large enough, the question is, can you afford it? And so what we end up doing is we kind of hope that of aliens good enough, or we hope that if the excellent tunnel is good enough and we can actually apply more advanced techniques there because we can't physically, you know, financially afford that appliance to see all of the traffic. And now that we have a distributed model with this accelerator, we could do it. >>So what's the what's in it for the customer. I real quick, cause I think this is interesting point. You mentioned policy, everyone in networking knows policy is just a great thing and it adds, you hear it being talked about up the stack as well. When you start getting to orchestrating microservices and whatnot, all that good stuff going on there, containers and whatnot and modern applications. What's the benefit to the customers with this approach? Because what I heard was more scale, more edge deployment, flexibility, relative to security policies and application enablement. I mean, is that what what's the customer get out of this architecture? What's the enablement. >>It comes down to, uh, taking again the capabilities that were in that top of rack switch and asserting them down. So that makes simplicity smaller blast radiuses for failure, smaller failure domains, maintenance on the networks, and the systems become easier. Your ability to integrate across workloads becomes infinitely easier. Um, and again, you know, we always want to kind of separate each one of those layers. So just as in say, a VX land network, my leaf and spine don't have to be tightly coupled together. I can now do this at a different layer. And so you can run a DPU with any networking in the core there. And so you get this extreme flexibility. You can start small, you can scale large. Um, you know, to me, the, the possibilities are endless. Yes, >>It's a great security control plan. Really flexibility is key. And, and also being situationally aware of any kind of threats or new vectors or whatever's happening in the network. Alessandra, this is huge upside, right? You've already identified some successes with some customers on your early field trials. What are they doing and why are they attracted to the solution? >>Yeah, I think the response from customers has been, uh, the most, uh, encouraging and, uh, exciting, uh, for, uh, for us to, uh, to sort of continue and work and develop this product. And we have actually learned a lot in the process. Um, we talked to tier two tier three cloud providers. Uh, we talked to, uh, SP um, software Tyco type of networks, uh, as well as a large enterprise customers, um, in, uh, one particular case. Um, uh, one, uh, I think, um, let me, let me call out a couple of examples here, just to give you a flavor. Uh, there is a service provider, a cloud provider, uh, in Asia who is actually managing a cloud, uh, where they are offering services based on multiple hypervisors. They are native services based on Zen, but they also are on ramp into the cloud, uh, workloads based on, uh, ESI and, uh, uh, and KVM, depending on what the customer picks from the piece on the menu. >>And they have the problem of now orchestrating through their orchestrate or integrating with the Zen center with vSphere, uh, with, uh, open stack to coordinate these multiple environments and in the process to provide security, they actually deploy virtual appliances everywhere, which has a lot of costs, complication, and eats up into the server CPU. The problem is that they saw in this technology, they call it actually game changing is actually to remove all this complexity of in a single network and distribute the micro-segmentation service directly into the fabric. And overall, they're hoping to get out of it, uh, uh, tremendous, uh, um, opics, uh, benefit and overall, um, uh, operational simplification for the cloud infrastructure. That's one potent a use case. Uh, another, uh, large enterprise customer global enterprise customer, uh, is running, uh, both ESI and hyper V in that environment. And they don't have a solution to do micro-segmentation consistently across hypervisors. >>So again, micro-segmentation is a huge driver security looks like it's a recurring theme, uh, talking to most of these customers and in the Tyco space, um, uh, we're working with a few types of customers on the CFT program, uh, where the main goal is actually to our Monet's network operation. They typically handle all the VNF search with their own homegrown DPDK stack. This is overly complex. It is frankly also as low and inefficient, and then they have a physical network to manage the, the idea of having again, one network, uh, to coordinate the provision in our cloud services between the, the take of VNF, uh, and, uh, the rest of the infrastructure, uh, is extremely powerful on top of the offloading capability of the, by the bluefin DPOs. Those are just some examples. >>That was a great use case, a lot more potential. I see that with the unified cloud networking, great stuff, feed, shout out to you guys at Nvidia had been following your success for a long time and continuing to innovate as cloud scales and pluribus here with the unified networking, kind of bring it to the next level. Great stuff. Great to have you guys on. And again, software keeps driving the innovation again, networking is just a part of it, and it's the key solution. So I got to ask both of you to wrap this up. How can cloud operators who are interested in, in this, uh, new architecture and solution, uh, learn more because this is an architectural shift. People are working on this problem. They're trying to think about multiple clouds of trying to think about unification around the network and giving more security, more flexibility, uh, to their teams. How can people learn more? >>Yeah, so, uh, all Sandra and I have a talk at the upcoming Nvidia GTC conference. Um, so that's the week of March 21st through 24th. Um, you can go and register for free and video.com/at GTC. Um, you can also watch recorded sessions if you ended up watching us on YouTube a little bit after the fact. Um, and we're going to dive a little bit more into the specifics and the details and what we're providing in the solution. >>Alexandra, how can people learn more? >>Yeah, absolutely. People can go to the pluribus, a website, www boost networks.com/eft, and they can fill up the form and, uh, they will contact durables to either know more or to know more and actually to sign up for the actual early field trial program, which starts at the end of April. >>Okay. Well, we'll leave it there. Thanks. You both for joining. Appreciate it up next. You're going to hear an independent analyst perspective and review some of the research from the enterprise strategy group ESG. I'm John ferry with the >>Cube. Thanks for watching. >>Okay. We've heard from the folks at networks and Nvidia about their effort to transform cloud networking and unify bespoke infrastructure. Now let's get the perspective from an independent analyst and to do so. We welcome in ESG, senior analysts, Bob LA Liberte, Bob. Good to see you. Thanks for coming into our east coast studios. >>Oh, thanks for having me. It's great to be >>Here. Yeah. So this, this idea of unified cloud networking approach, how serious is it? What's what's driving it. >>Yeah, there's certainly a lot of drivers behind it, but probably the first and foremost is the fact that application environments are becoming a lot more distributed, right? So the, it pendulum tends to swing back and forth. And we're definitely on one that's swinging from consolidated to distributed. And so applications are being deployed in multiple private data centers, multiple public cloud locations, edge locations. And as a result of that, what you're seeing is a lot of complexity. So organizations are having to deal with this highly disparate environment. They have to secure it. They have to ensure connectivity to it and all that's driving up complexity. In fact, when we asked in one of our last surveys and last year about network complexity, more than half 54% came out and said, Hey, our network environment is now either more or significantly more complex than it used to be. >>And as a result of that, what you're seeing is it's really impacting agility. So everyone's moving to these modern application environments, distributing them across areas so they can improve agility yet it's creating more complexity. So a little bit counter to the fact and, you know, really counter to their overarching digital transformation initiatives. From what we've seen, you know, nine out of 10 organizations today are either beginning in process or have a mature digital transformation process or initiative, but their top goals, when you look at them, it probably shouldn't be a surprise. The number one goal is driving operational efficiency. So it makes sense. I've distributed my environment to create agility, but I've created a lot of complexity. So now I need these tools that are going to help me drive operational efficiency, drive better experience. >>I mean, I love how you bring in the data yesterday. Does a great job with that. Uh, questions is, is it about just unifying existing networks or is there sort of a need to rethink kind of a do-over network, how networks are built? >>Yeah, that's a, that's a really good point because certainly unifying networks helps right. Driving any kind of operational efficiency helps. But in this particular case, because we've made the transition to new application architectures and the impact that's having as well, it's really about changing and bringing in new frameworks and new network architectures to accommodate those new application architectures. And by that, what I'm talking about is the fact that these new modern application architectures, microservices, containers are driving a lot more east west traffic. So in the old days, it used to be easier in north south coming out of the server, one application per server, things like that. Right now you've got hundreds, if not thousands of microservices communicating with each other users communicating to them. So there's a lot more traffic and a lot of it's taking place within the servers themselves. The other issue that you starting to see as well from that security perspective, when we were all consolidated, we had those perimeter based legacy, you know, castle and moat security architectures, but that doesn't work anymore when the applications aren't in the castle, right. >>When everything's spread out that that no longer happens. So we're absolutely seeing, um, organizations trying to, trying to make a shift. And, and I think much, like if you think about the shift that we're seeing with all the remote workers and the sassy framework to enable a secure framework there, this it's almost the same thing. We're seeing this distributed services framework come up to support the applications better within the data centers, within the cloud data centers, so that you can drive that security closer to those applications and make sure they're, they're fully protected. Uh, and that's really driving a lot of the, you know, the zero trust stuff you hear, right? So never trust, always verify, making sure that everything is, is, is really secure micro-segmentation is another big area. So ensuring that these applications, when they're connected to each other, they're, they're fully segmented out. And that's again, because if someone does get a breach, if they are in your data center, you want to limit the blast radius, you want to limit the amount of damage that's done. So that by doing that, it really makes it a lot harder for them to see everything that's in there. >>You know, you mentioned zero trust. It used to be a buzzword, and now it's like become a mandate. And I love the mode analogy. You know, you build a moat to protect the queen and the castle, the Queens left the castles, it's just distributed. So how should we think about this, this pluribus and Nvidia solution. There's a spectrum, help us understand that you've got appliances, you've got pure software solutions. You've got what pluribus is doing with Nvidia, help us understand that. >>Yeah, absolutely. I think as organizations recognize the need to distribute their services to closer to the applications, they're trying different models. So from a legacy approach, you know, from a security perspective, they've got these centralized firewalls that they're deploying within their data centers. The hard part for that is if you want all this traffic to be secured, you're actually sending it out of the server up through the rack, usually to in different location in the data center and back. So with the need for agility, with the need for performance, right, that adds a lot of latency. Plus when you start needing to scale, that means adding more and more network connections, more and more appliances. So it can get very costly as well as impacting the performance. The other way that organizations are seeking to solve this problem is by taking the software itself and deploying it on the servers. Okay. So that's a, it's a great approach, right? It brings it really close to the applications, but the things you start running into there, there's a couple of things. One is that you start seeing that the DevOps team start taking on that networking and security responsibility, which they >>Don't want to >>Do, they don't want to do right. And the operations teams loses a little bit of visibility into that. Um, plus when you load the software onto the server, you're taking up precious CPU cycles. So if you're really wanting your applications to perform at an optimized state, having additional software on there, isn't going to, isn't going to do it. So, you know, when we think about all those types of things, right, and certainly the other side effects of that is the impact of the performance, but there's also a cost. So if you have to buy more servers because your CPU's are being utilized, right, and you have hundreds or thousands of servers, right, those costs are going to add up. So what, what Nvidia and pluribus have done by working together is to be able to take some of those services and be able to deploy them onto a smart Nick, right? >>To be able to deploy the DPU based smart SMARTNICK into the servers themselves. And then pluribus has come in and said, we're going to unify create that unified fabric across the networking space, into those networking services all the way down to the server. So the benefits of having that are pretty clear in that you're offloading that capability from the server. So your CPU's are optimized. You're saving a lot of money. You're not having to go outside of the server and go to a different rack somewhere else in the data center. So your performance is going to be optimized as well. You're not going to incur any latency hit for every trip round trip to the, to the firewall and back. So I think all those things are really important. Plus the fact that you're going to see from a, an organizational aspect, we talked about the dev ops and net ops teams. The network operations teams now can work with the security teams to establish the security policies and the networking policies. So that they've dev ops teams. Don't have to worry about that. So essentially they just create the guardrails and let the dev op team run. Cause that's what they want. They want that agility and speed. >>Yeah. Your point about CPU cycles is key. I mean, it's estimated that 25 to 30% of CPU cycles in the data center are wasted. The cores are wasted doing storage offload or, or networking or security offload. And, you know, I've said many times everybody needs a nitro like Amazon nugget, but you can't go, you can only buy Amazon nitro if you go into AWS. Right. Everybody needs a nitro. So is that how we should think about this? >>Yeah. That's a great analogy to think about this. Um, and I think I would take it a step further because it's, it's almost the opposite end of the spectrum because pluribus and video are doing this in a very open way. And so pluribus has always been a proponent of open networking. And so what they're trying to do is extend that now to these distributed services. So leverage working with Nvidia, who's also open as well, being able to bring that to bear so that organizations can not only take advantage of these distributed services, but also that unified networking fabric, that unified cloud fabric across that environment from the server across the switches, the other key piece of what pluribus is doing, because they've been doing this for a while now, and they've been doing it with the older application environments and the older server environments, they're able to provide that unified networking experience across a host of different types of servers and platforms. So you can have not only the modern application supported, but also the legacy environments, um, you know, bare metal. You could go any type of virtualization, you can run containers, et cetera. So a wide gambit of different technologies hosting those applications supported by a unified cloud fabric from pluribus. >>So what does that mean for the customer? I don't have to rip and replace my whole infrastructure, right? >>Yeah. Well, think what it does for, again, from that operational efficiency, when you're going from a legacy environment to that modern environment, it helps with the migration helps you accelerate that migration because you're not switching different management systems to accomplish that. You've got the same unified networking fabric that you've been working with to enable you to run your legacy as well as transfer over to those modern applications. Okay. >>So your people are comfortable with the skillsets, et cetera. All right. I'll give you the last word. Give us the bottom line here. >>So yeah, I think obviously with all the modern applications that are coming out, the distributed application environments, it's really posing a lot of risk on these organizations to be able to get not only security, but also visibility into those environments. And so organizations have to find solutions. As I said, at the beginning, they're looking to drive operational efficiency. So getting operational efficiency from a unified cloud networking solution, that it goes from the server across the servers to multiple different environments, right in different cloud environments is certainly going to help organizations drive that operational efficiency. It's going to help them save money for visibility, for security and even open networking. So a great opportunity for organizations, especially large enterprises, cloud providers who are trying to build that hyperscaler like environment. You mentioned the nitro card, right? This is a great way to do it with an open solution. >>Bob, thanks so much for, for coming in and sharing your insights. Appreciate it. >>You're welcome. Thanks. >>Thanks for watching the program today. Remember all these videos are available on demand@thekey.net. You can check out all the news from today@siliconangle.com and of course, pluribus networks.com many thanks diplomas for making this program possible and sponsoring the cube. This is Dave Volante. Thanks for watching. Be well, we'll see you next time.

>>Okay, let's kick things off. We're here at my capital. One of the CMO of pluribus networks and AMI by Dani VP of networking, marketing developer ecosystem at Nvidia. Great to have you welcome folks. Thank you. Thanks. So let's get into the, the problem situation with cloud unified network. What problems are out there? What challenges do cloud operators have Mike let's get into? >>Yeah, really, you know, the challenges we're looking at are for non hyperscalers that's enterprises, governments, tier two service providers, cloud service providers, and the first mandate for them is to become as agile as a hyperscaler. So they need to be able to deploy services and security policies in seconds. They need to be able to abstract the complexity of the network and define things in software while it's accelerated in hardware. Really ultimately they need a single operating model everywhere. And then the second thing is they need to distribute networking and security services out to the edge of the host. We're seeing a growth in cyber attacks. It's it's not slowing down. It's only getting worse and, you know, solving for this security problem across clouds is absolutely critical. And the way to do it is to move security out to the host. >>Okay. With that goal in mind, what's the pluribus vision. How does this tie together? >>Yeah, so basically what we see is that this demands a new architecture and that new architecture has four tenants. The first tenant is unified and simplified cloud networks. If you look at cloud networks today, there's, there's sort of like discrete bespoke cloud networks, you know, per hypervisor, per private cloud edge cloud public cloud. Each of the public clouds have different networks that needs to be unified. You know, if we want these folks to be able to be agile, they need to be able to issue a single command or instantiate a security policy across all of those locations with one command and not have to go to each one. The second is like I mentioned, distributed security, distributed security without compromise, extended out to the host is absolutely critical. So micro-segmentation and distributed firewalls, but it doesn't stop there. They also need pervasive visibility. You know, it's, it's, it's sort of like with security, you really can't see you can't protect what you can't see. >>So you need visibility everywhere. The problem is visibility to date has been very expensive. Folks have had to basically build a separate overlay network of taps, packet brokers, tap aggregation infrastructure that really needs to be built into this unified network I'm talking about. And the last thing is automation. All of this needs to be SDN enabled. So this is related to my comment about abstraction abstract, the complexity of all these discreet networks, physic whatever's down there in the physical layer. Yeah. I don't want to see it. I want abstract it. I wanted to find things in software, but I do want to leverage the power of hardware to accelerate that. So that's the fourth tenant is SDN automation. >>Mike, we've been talking on the cable a lot about this architectural shift and customers are looking at this. This is a big part of everyone who's looking at cloud operations next gen, how do we get there? How do customers get this vision realized? >>That's a great question. And I appreciate the tee up. I mean, we're, we're here today for that reason. We're introducing two things today. The first is a unified cloud networking vision. And that is a vision of where pluribus is headed with our partners like Nvidia longterm. And that is about deploying a common operating model, SDN enabled SDN, automated hardware, accelerated across all clouds and whether that's underlying overlay switch or server hype, any hypervisor infrastructure containers, any workload doesn't matter. So that's ultimately where we want to get. And that's what we talked about earlier. The first step in that vision is what we call the unified cloud fabric. And this is the next generation of our adaptive cloud fabric. And what's nice about this is we're not starting from scratch. We have an award-winning adaptive cloud fabric product that is deployed globally. And in particular we're very proud of the fact that it's deployed in over a hundred tier one mobile operators as the network fabric for their 4g and 5g virtualized cores. We know how to build carrier grade networking infrastructure. What we're doing now to realize this next generation unified cloud fabric is we're extending from the switch to this Nvidia Bluefield to DPU. We, >>No, there's all that up real quick. That's a good, that's a good prop. That's the blue field and video. >>It's the Nvidia Bluefield two DPU data processing unit. And you know, what we're doing fundamentally is extending our SDN automated fabric, the unified cloud fabric out to the host, but it does take processing power. So we knew that we didn't want to do, we didn't want to implement that running on the CPU, which is what some other companies do because it consumes revenue generating CPU's from the application. So a DPU is a perfect way to implement this. And we knew that Nvidia was the leader with this blue field too. And so that is the first that's, that's the first step in the getting into realizing this vision >>And video has always been powering some great workloads of GPU. Now you've got DP networking, and then video is here. What is the relationship with clothes? How did that come together? Tell us the story. >>Yeah. So, you know, we've been working with pluribus for quite some time. I think the last several months was really when it came to fruition and what pluribus is trying build and what Nvidia has. So we have, you know, this concept of a Bluefield data processing unit, which if you think about it, conceptually does really three things, offload, accelerate an isolate. So offload your workloads from your CPU to your data processing unit infrastructure workloads, that is a accelerate. So there's a bunch of acceleration engine. So you can run infrastructure workloads much faster than you would otherwise, and then isolation. So you have this nice security isolation between the data processing unit and your other CPU environment. And so you can run completely isolated workloads directly on the data processing unit. So we introduced this, you know, a couple of years ago, and with pluribus, you know, we've been talking to the pluribus team for quite some months now. >>And I think really the combination of what pluribus is trying to build and what they've developed around this unified cloud fabric is fits really nicely with the DPU and running that on the DPU and extending it really from your physical switch, all the way to your host environment, specifically on the data processing unit. So if you think about what's happening as you add data processing units to your environment. So every server we believe over time is going to have data processing units. So now you'll have to manage that complexity from the physical network layer to the host layer. And so what pluribus is really trying to do is extending the network fabric from the host, from the switch to the host, and really have that single pane of glass for network operators to be able to configure provision, manage all of the complexity of the network environment. >>So that's really how the partnership truly started. And so it started really with extending the network fabric, and now we're also working with them on security. So, you know, if you sort of take that concept of isolation and security isolation, what pluribus has within their fabric is the concept of micro-segmentation. And so now you can take that extended to the data processing unit and really have isolated micro-segmentation workloads, whether it's bare metal cloud native environments, whether it's virtualized environments, whether it's public cloud, private cloud hybrid cloud. So it really is a magical partnership between the two companies with their unified cloud fabric running on, on the DPU. >>I love about this conversation is it reminds me of when you have these changing markets, the product gets pulled out of the market and, and you guys step up and create these new solutions. And I think this is a great example. So I have to ask you, how do you guys differentiate what sets this apart for customers with what's in it for the, >>Yeah. So I mentioned, you know, three things in terms of the value of what the Bluefield brings, right? There's offloading, accelerating, isolating, that's sort of the key core tenants of Bluefield, so that, you know, if you sort of think about what, what Bluefield, what we've done, you know, in terms of the differentiation, we're really a robust platform for innovation. So we introduced Bluefield to last year, we're introducing Bluefield three, which is our next generation of Bluefields, you know, we'll have five X, the arm compute capacity. It will have 400 gig line rate acceleration for X better crypto acceleration. So it will be remarkably better than the previous generation. And we'll continue to innovate and add, you know, chips to our portfolio every, every 18 months to two years. So that's sort of one of the key areas of differentiation. The other is the, if you look at Nvidia and, and you know, what we're sort of known for is really known for our AI artificial intelligence and our artificial intelligence software, as well as our GPU. >>So you look at artificial intelligence and the combination of artificial intelligence plus data processing. This really creates the faster, more efficient, secure AI systems from, you know, the core of your data center all the way out to the edge. And so with Nvidia, we really have these converged accelerators where we've combined the GPU, which does all your AI processing with your data processing with the DPU. So we have this convergence really nice convergence of, of that area. And I would say the third area is really around our developer environment. So, you know, one of the key, one of our key motivations at Nvidia is really to have our partner ecosystem, embrace our technology and build solutions around our technology. So if you look at what we've done with the DPU, with credit and an SDK, which is an open SDK called Doka, and it's an open SDK for our partners to really build and develop solutions using Bluefield and using all these accelerated libraries that we expose through Doka. And so part of our differentiation is really building this open ecosystem for our partners to take advantage and build solutions around our technology. >>You know, it's exciting is when I hear you talk, it's like you realize that there's no one general purpose network anymore. Everyone has their own super environment Supercloud or these new capabilities. They can really craft their own, I'd say custom environment at scale with easy tools. Right. And it's all kind of, again, this is the new architecture Mike, you were talking about, how does customers run this effectively? Cost-effectively and how do people migrate? >>Yeah, I think that is the key question, right? So we've got this beautiful architecture. You, you know, Amazon nitro is a, is a good example of, of a smart NIC architecture that has been successfully deployed, but enterprises and serve tier two service providers and tier one service providers and governments are not Amazon, right? So they need to migrate there and they need this architecture to be cost-effective. And, and that's, that's super key. I mean, the reality is deep user moving fast, but they're not going to be deployed everywhere on day one. Some servers will ha have DPS right away. Some servers will have deep use in a year or two. And then there are devices that may never have DPS, right? IOT gateways, or legacy servers, even mainframes. So that's the beauty of a solution that creates a fabric across both the switch and the DPU, right? >>And by leveraging the Nvidia Bluefield DPU, what we really like about it is it's open and that drives cost efficiencies. And then, you know, with this, with this, our architectural approach effectively, you get a unified solution across switch and DPU workload independent doesn't matter what hypervisor it is, integrated visibility, integrated security, and that can create tremendous cost efficiencies and really extract a lot of the expense from, from a capital perspective out of the network, as well as from an operational perspective, because now I have an SDN automated solution where I'm literally issuing a command to deploy a network service or to create or deploy our security policy and is deployed everywhere, automatically saving the oper, the network operations team and the security operations team time. >>All right. So let me rewind that because that's super important. Get the unified cloud architecture, I'm the customer, but it's implemented, what's the value again, take, take me through the value to me. I have a unified environment. What's the value. >>Yeah. So I mean, the value is effectively. So there's a few pieces of value. The first piece of value is I'm creating this clean D mark. I'm taking networking to the host. And like I mentioned, we're not running it on the CPU. So in implementations that run networking on the CPU, there's some conflict between the dev ops team who owned the server and the NetApps team who own the network because they're installing software on the, on the CPU stealing cycles from what should be revenue generating CPU's. So now by, by terminating the networking on the DPU, we click create this real clean DMARC. So the dev ops folks are happy because they don't necessarily have the skills to manage network and they don't necessarily want to spend the time managing networking. They've got their network counterparts who are also happy the NetApps team, because they want to control the networking. >>And now we've got this clean DMARC where the dev ops folks get the services they need and the NetApp folks get the control and agility they need. So that's a huge value. The next piece of value is distributed security. This is essential. I mentioned earlier, you know, put pushing out micro-segmentation and distributed firewall, basically at the application level, right, where I create these small, small segments on an application by application basis. So if a bad actor does penetrate the perimeter firewall, they're contained once they get inside. Cause the worst thing is a bad actor penetrates at perimeter firewall, and it can go wherever they want and wreak havoc, right? And so that's why this, this is so essential. And the next benefit obviously is this unified networking operating model, right? Having an operating model, switch and server underlay and overlay, workload agnostic, making the life of the NetApps teams much easier so they can focus their time on really strategy instead of spending an afternoon, deploying a single V LAN for example. >>Awesome. And I think also from my standpoint, I mean, perimeter security is pretty much, I mean, they're out there, it gets the firewall still out there exists, but pretty much they're being breached all the time, the perimeter. So you have to have this new security model. And I think the other thing that you mentioned, the separation between dev ops is cool because the infrastructure is code is about making the developers be agile and build security in from day one. So this policy aspect is, is huge new control points. I think you guys have a new architecture that enables the security to be handled more flexible. Right. That seems to be the killer feature, >>Right? Yeah. If you look at the data processing unit, I think one of the great things about sort of this new architecture, it's really the foundation for zero trust it's. So like you talked about the perimeter is getting breached. And so now each and every compute node has to be protected. And I think that's sort of what you see with the partnership between pluribus and Nvidia is the DPU is really the foundation of zero trust. And pluribus is really building on that vision with allowing sort of micro-segmentation and being able to protect each and every compute node as well as the underlying network. >>And this is an illustration of how the market's evolving architectures are being reshaped and refactored for cloud scale and all this new goodness with data. So I got to ask how you guys go into market together. Michael, start with you. What's the relationship look like in the go to market with an Nvidia? >>Sure. I mean, we're, you know, we're super excited about the partnership. Obviously we're here together. We think we've got a really good solution for the market, so we're jointly marketing it. You know, obviously we appreciate that Nvidia is open that's, that's sort of in our DNA, we're about open networking. They've got other ISV who are gonna run on Bluefield too. We're probably going to run on other DPS in the future, but right now we're we feel like we're partnered with the number one provider of DPS in the world and super excited about making a splash with it >>In video, get the hot product. >>Yeah. So Bluefield too, as I mentioned was GA last year, we're introducing well, we now also have the converged accelerator. So I talked about artificial intelligence or artificial intelligence software with the Bluefield DPU, all of that put together on a converged accelerator. The nice thing there is you can either run those workloads. So if you have an artificial intelligence workload and an infrastructure workload, you can warn them separately on the same platform or you can actually use, you can actually run artificial intelligence applications on the Bluefield itself. So that's what the converged accelerator really brings the table. So that's available now. Then we have Bluefield three, which will be available late this year. And I talked about sort of, you know, how much better that next generation of Bluefield is in comparison to Bluefield two. So we will see Bluefield three shipping later on this year, and then our software stack, which I talked about, which is called Doka we're on our second version are DACA one dot two. >>We're releasing Doka one dot three in about two months from now. And so that's really our open ecosystem framework. So allow you to program the Bluefields. So we have all of our acceleration libraries, security libraries, that's all packed into this SDK called Doka. And it really gives that simplicity to our partners to be able to develop on top of Bluefield. So as we add new generations of Bluefield, you know, next, next year, we'll have, you know, another version and so on and so forth. Doka is really that unified unified layer that allows Bluefield to be both forwards compatible and backwards compatible. So partners only really have to think about writing to that SDK once and then it automatically works with future generations of Bluefields. So that's sort of the nice thing around, around Doka. And then in terms of our go to market model, we're working with every, every major OEM. So later on this year, you'll see, you know, major server manufacturers releasing Bluefield enabled servers, so more to come >>Save money, make it easier, more capabilities, more workload power. This is the future of, of cloud operations. Yeah. >>And one thing I'll add is we are, we have a number of customers as you'll hear in the next segment that are already signed up and we'll be working with us for our early field trial starting late April early may. We are accepting registrations. You can go to www.pluribusnetworks.com/e F T if you're interested in signing up for being part of our field trial and, and providing feedback on the product, >>Awesome innovation and network. Thanks so much for sharing the news. Really appreciate it. Thanks so much. Okay. In a moment, we'll be back to the deeper in the product, the integration security zero trust use cases. You're watching the cube, the leader in enterprise tech coverage.

(upbeat music) >> Hey, welcome back everyone to theCube's coverage of AWS re:Invent 2021. I'm John Furrier, host of theCube, wall-to-wall coverage in-person and hybrid. The two great guests here, Manu Parbhakar, worldwide Leader, Linux and IBM Software Partnership at AWS, and Mike Evans, Vice President of Technical Business Development at Red Hat. Gentlemen, thanks for coming on theCube. Love this conversation, bringing Red Hat and AWS together. Two great companies, great technologies. It really is about software in the cloud, Cloud-Scale. Thanks for coming on. >> Thanks John. >> So get us into the partnership. Okay. This is super important. Red Hat, well known open source as cloud needs to become clear, doing an amazing work. Amazon, Cloud-Scale, Data is a big part of it. Modern software. Tell us about the partnership. >> Thanks John. Super excited to share about our partnership. As we have been partnering for almost 14 years together. We started in the very early days of AWS. And now we have tens of thousands of customers that are running RHEL on EC2. If you look at over the last three years, the pace of innovation for our joint partnership has only increased. It has manifested in three key formats. The first one is the pace at which RHEL supports new EC2 instances like Arm, Graviton. You know, think a lot of features like Nitro. The second is just the portfolio of new RHEL offerings that we have launched over the last three years. We started with RHEL for sequel, RHEL high availability, RHEL for SAP, and then only last month, we've launched the support for knowledge base for RHEL customers. Mike, you want to talk about what you're doing with OpenShift and Ansible as well? >> Yeah, it's good to be here. It's fascinating to me cause I've been at Red Hat for 21 years now. And vividly remember the start of working with AWS back in 2008, when the cloud was kind of a wild idea with a whole bunch of doubters. And it's been an interesting time, but I feel the next 14 years are going to be exciting in a different way. We now have a very large customer base from almost every industry in the world built on RHEL, and running on AWS. And our goal now is to continue to add additional elements to our offerings, to build upon that and extend it. The largest addition which we're going to be talking a lot about here at the re:Invent show was the partnership in April this year when we launched the Red Hat OpenShift service on AWS as a managed version of OpenShift for containers based workloads. And we're seeing a lot of the customers that have standardized on RHEL on EC2, or ones that are using OpenShift on-premise deployments, as the early adopters of ROSA, but we're also seeing a huge number of new customers who never purchased anything from Red Hat. So, in addition to the customers, we're getting great feedback from systems integrators and ISV partners who are looking to have a software application run both on-premise and in AWS, and with OpenShift being one of the pioneers in enabling both container and harnessing Kubernetes where ROSA is just a really exciting area for us to track and continue to advance together with AWS. >> It's very interesting. Before I get to ROSA, I want to just get the update on Red Hat and IBM, obviously the acquisition part of IBM, how is that impacting the partnership? You can just quickly touch on that. >> Sure. I'll start off and, I mean, Red Hat went from a company that was about 15,000 employees competing with a lot of really large technology companies and we added more than 100,000 field oriented people when IBM acquired Red Hat to help magnify the Red Hat solutions, and the global scale and coverage of IBM is incredible. I like to give two simple examples of people. One is, I remember our salesforce in EMEA telling me they got a $4 million order from a country in Africa theydidn't even know existed. And IBM had 100 people in it, or AT&T is one of Red Hat's largest accounts, and I think at one point we had seven full-time people on it and AT&T is one of IBM's largest accounts and they had two seven storey buildings full of people working with AT&T. So RHELative to AWS, we now also see IBM embracing AWS more with both software, and services, in the magnification of Red Hat based solutions, combined with that embrace should be, create some great growth. And I think IBM is pretty excited about being able to sell Red Hat software as well. >> Yeah, go ahead. >> And Manu I think you have, yeah. >> Yeah. I think there's also, it is definitely very positive John. >> Yeah. >> You know, just the joint work that Red Hat and AWS have done for the last 14 years, working in the trenches supporting our end customers is now also providing lot of Tailwinds for the IBM software partnership. We have done some incredible work over the last 12 months around three broad categories. The first one is around product, what we're doing around customer success, and then what we're doing around sales and marketing. So on the product side, we have listed about 15 products on Marketplace over the course of the last 12 to 15 months. And our goal is to launch all of the IBM Cloud Paks. These are containerized versions of IBM software on Marketplace by the first half of next year. The other feedback that we are getting from our customers is that, hey, we love IBM software running at Amazon, but we like to have a cloud native SaaS version of the software. So there's a lot of work that's going on right now, to make sure that many of these offerings are available in a cloud-native manner. And you're not talking with Db2 Cognos, Maximo, (indistinct), on EC2. The second thing that we're doing is making sure that many of these large enterprise customers are running IBM software, are successful. So our technical teams are attached to the hip, working on the ground floor in making customers like Delta successful in running IBM software on them. I think the third piece around sales and marketing just filing up a vibrant ecosystem, rather how do we modernize and migrate this IBM software on Cloud Paks on AWS? So there's a huge push going on here. So (indistinct), you know, the Red Hat partnership is providing a lot of Tailwinds to accelerate our partnership with IBM software. >> You know, I always, I've been saying all this year in Red Hat summit, as well as Ansible Fest that, distributed computing is coming to large scale. And that's really the, what's happening. I mean, you looking at what you guys are doing cause it's amazing. ROSA Red Hat OpenShift on AWS, very notable to use the term on AWS, which actually means something in the partnership as we learned over the years. How is that going Mike because you launched on theCube in April, ROSA, it had great traction going in. It's in the Marketplace. You've got some integration. It's really a hand in glove situation with Cloud-Scale. Take us through what's the update? >> Yeah, let me, let me let Manu speak first to his AWS view and then I'll add the Red Hat picture. >> Thanks Mike. John for ROSA is part of an entire container portfolio. So if you look at it, so we have ECS, EKS, the managed Kubernetes service. We have the serverless containers with Fargate. We launched ECS case anywhere. And then ROSA is part of an entire portfolio of container services. As you know, two thirds of all container workloads run on AWS. And a big function of that is because we (indistinct) from our customer and then sold them what the requirements are. There are two sets of key customers that are driving the demand and the early adoption of ROSA. The first set of customers that have standardized on OpenShift on-premises. They love the fact that everything that comes out of the box and they would love to use it on Arm. So that's the first (indistinct). The second set of customers are, you know, the large RHEL users on EC2. The tens of thousands of customers that we've talked about that want to move from VM to containers, and want to do DevOps. So it's this set of two customers that are informing our roadmap, as well as our investments around ROSA. We are seeing solid adoption, both in terms of adoption by a customer, as well as the partners and helping, and how our partners are helping our customers in modernizing from VMs to containers. So it's a, it's a huge, it's a huge priority for our container service. And over the next few years, we continue to see, to increase our investment on the product road map here. >> Yeah, from my perspective, first off at the high level in mind, my one of the most interesting parts of ROSA is being integrated in the AWS console and not just for the, you know, where it shows up on the screen, but also all the work behind what that took to get there and why we did it. And we did it because customers were asking both of us, we're saying, look, OpenShift is a platform. We're going to be building and deploying serious applications at incredible scale on it. And it's really got to have joint high-quality support, joint high-quality engineering. It's got to be rock solid. And so we came to agreement with AWS. That was the best way to do that, was to build it in the console, you know, integrated in, into the core of an AWS engineering team with Red Hat engineers, Arm and Arms. So that's, that's a very unique service and it's not like a high level SaaS application that runs above everything, it's down in the bowels and, and really is, needs to be rock solid. So we're seeing, we're seeing great interest, both from end users, as I mentioned, existing customers, new customers, the partner base, you know, how the systems integrators are coming on board. There's lots of business and money to be made in modernizing applications as well as building new cloud native applications. People can, you know, between Red Hat and AWS, we've got some, some models around supporting POCs and customer migrations. We've got some joint investments. it's a really ripe area. >> Yeah. That's good stuff. Real quick. what do you think of ROSA versus EKS and ECS? What's, how should people think about that Mike? (indistinct) >> You got to go for it Manu. Your job is to position all these (indistinct). (indistinct) >> John, ROSA is part of our container portfolio services along with EKS, ECS, Fargate, and any (indistinct) services that we just launched earlier this year. There are, you know, set of customers both that are running OpenShift on-premises that are standardized on ROSA. And then there are large set of RHEL customers that are running RHEL on EC2, that want to use the ROSA service. So, you know, both AWS and Red Hat are now continuing to invest in accelerating the roadmap of the service on our platform. You know, we are working on improving the console experience. Also one of the things we just launched recently is the Amazon controller to Kubernetes, or what , you know, service operators for S3. So over the next few years you will see, you know, significant investment from both Red Hat and AWS in this joint service. And this is an integral part of our overall container portfolio. >> And great stuff to get in the console. That's great, great integration. That's the future. I got to ask about the graviton instances. It's been one of the most biggest success stories, I think we believe in Amazon history in the acquisition of Annapurna, has really created great differentiation. And anyone who's in the software knows if you have good chips powering apps, they go faster. And if the chips are good, they're less expensive. And that's the innovation. We saw that RHEL now supports graviton instances. Tell us more about the Red Hat strategy with graviton and Arms specifically, has that impact your (indistinct) development, and what does it mean for customers? >> Sure. Yeah, it's pretty, it's a pretty fascinating area for me. As I said, I've been a Red Hat for 21 years and my job is actually looking at new markets and new technologies now for Red Hat and work with our largest partners. So, I've been tracking the Arm dynamics for awhile, and we've been working with AWS for over two years, supporting graviton. And it's, I'm seeing more enthusiasm now in terms of developers and, especially for very horizontal, large scale applications. And we're excited to be working with AWS directly on it. And I think it's going to be a fascinating next two years on Arm, personally. >> Many of the specialized processors for training and instances, all that stuff, can be applied to web services and automation like cloud native services, right? Is that, it sounds like a good direction. Take us through that. >> John, on our partnership with Red Hat, we are continuing to iterate, as Mike mentioned, the stuff that we've done around graviton, both the last two years is pretty incredible. And the pace at which we are innovating is improving. Around the (indistinct) and the inferential instances, we are continuing to work with Red Hat and, you know, the support for RHEL should come shortly, very soon. >> Well, my prediction is that the graviton success was going to be applied to every single category. You can get that kind of innovation with this on the software side, just really kind of just, that's the magical, that's the, that's the proven form of software, right? We've been there. Good software powering with some great performance. Manu, Mike, thank you for coming on and sharing the, the news and the partnership update. Congratulations on the partnership. Really good. Thank you. >> Excellent John. Incredible (indistinct). >> Yeah, this is the future software as we see, it's all coming together. Here on theCube, we're bringing all the action, software being powered by chips, is theCube coverage of AWS re:invent 2021. I'm John Furrier, your host. Thanks for watching. (upbeat music)

>>Well, welcome back to the cubes coverage of AWS reinvent 2021. We're here joined by Ian buck, general manager and vice president of accelerated computing at Nvidia I'm. John Ford, your host of the QB. And thanks for coming on. So in video, obviously, great brand congratulates on all your continued success. Everyone who has does anything in graphics knows the GPU's are hot and you guys get great brand great success in the company, but AI and machine learning was seeing the trend significantly being powered by the GPU's and other systems. So it's a key part of everything. So what's the trends that you're seeing, uh, in ML and AI, that's accelerating computing to the cloud. Yeah, >>I mean, AI is kind of drape bragging breakthroughs innovations across so many segments, so many different use cases. We see it showing up with things like credit card, fraud prevention and product and content recommendations. Really it's the new engine behind search engines is AI. Uh, people are applying AI to things like, um, meeting transcriptions, uh, virtual calls like this using AI to actually capture what was said. Um, and that gets applied in person to person interactions. We also see it in intelligence systems assistance for a contact center, automation or chat bots, uh, medical imaging, um, and intelligence stores and warehouses and everywhere. It's really, it's really amazing what AI has been demonstrated, what it can do. And, uh, it's new use cases are showing up all the time. >>Yeah. I'd love to get your thoughts on, on how the world's evolved just in the past few years, along with cloud, and certainly the pandemics proven it. You had this whole kind of full stack mindset initially, and now you're seeing more of a horizontal scale, but yet enabling this vertical specialization in applications. I mean, you mentioned some of those apps, the new enablers, this kind of the horizontal play with enablement for specialization, with data, this is a huge shift that's going on. It's been happening. What's your reaction to that? >>Yeah, it's the innovations on two fronts. There's a horizontal front, which is basically the different kinds of neural networks or AIS as well as machine learning techniques that are, um, just being invented by researchers for, uh, and the community at large, including Amazon. Um, you know, it started with these convolutional neural networks, which are great for image processing, but as it expanded more recently into, uh, recurrent neural networks, transformer models, which are great for language and language and understanding, and then the new hot topic graph neural networks, where the actual graph now is trained as a, as a neural network, you have this underpinning of great AI technologies that are being adventure around the world in videos role is try to productize that and provide a platform for people to do that innovation and then take the next step and innovate vertically. Um, take it, take it and apply it to two particular field, um, like medical, like healthcare and medical imaging applying AI, so that radiologists can have an AI assistant with them and highlight different parts of the scan. >>Then maybe troublesome worrying, or requires more investigation, um, using it for robotics, building virtual worlds, where robots can be trained in a virtual environment, their AI being constantly trained, reinforced, and learn how to do certain activities and techniques. So that the first time it's ever downloaded into a real robot, it works right out of the box, um, to do, to activate that we co we are creating different vertical solutions, vertical stacks for products that talk the languages of those businesses, of those users, uh, in medical imaging, it's processing medical data, which is obviously a very complicated large format data, often three-dimensional boxes in robotics. It's building combining both our graphics and simulation technologies, along with the, you know, the AI training capabilities and different capabilities in order to run in real time. Those are, >>Yeah. I mean, it's just so cutting edge. It's so relevant. I mean, I think one of the things you mentioned about the neural networks, specifically, the graph neural networks, I mean, we saw, I mean, just to go back to the late two thousands, you know, how unstructured data or object store created, a lot of people realize that the value out of that now you've got graph graph value, you got graph network effect, you've got all kinds of new patterns. You guys have this notion of graph neural networks. Um, that's, that's, that's out there. What is, what is a graph neural network and what does it actually mean for deep learning and an AI perspective? >>Yeah, we have a graph is exactly what it sounds like. You have points that are connected to each other, that established relationships and the example of amazon.com. You might have buyers, distributors, sellers, um, and all of them are buying or recommending or selling different products. And they're represented in a graph if I buy something from you and from you, I'm connected to those end points and likewise more deeply across a supply chain or warehouse or other buyers and sellers across the network. What's new right now is that those connections now can be treated and trained like a neural network, understanding the relationship. How strong is that connection between that buyer and seller or that distributor and supplier, and then build up a network that figure out and understand patterns across them. For example, what products I may like. Cause I have this connection in my graph, what other products may meet those requirements, or also identifying things like fraud when, when patterns and buying patterns don't match, what a graph neural networks should say would be the typical kind of graph connectivity, the different kind of weights and connections between the two captured by the frequency half I buy things or how I rate them or give them stars as she used cases, uh, this application graph neural networks, which is basically capturing the connections of all things with all people, especially in the world of e-commerce, it's very exciting to a new application, but applying AI to optimizing business, to reducing fraud and letting us, you know, get access to the products that we want, the products that they have, our recommendations be things that, that excited us and want us to buy things >>Great setup for the real conversation that's going on here at re-invent, which is new kinds of workloads are changing. The game. People are refactoring their business with not just replatform, but actually using this to identify value and see cloud scale allows you to have the compute power to, you know, look at a note on an arc and actually code that. It's all, it's all science, all computer science, all at scale. So with that, that brings up the whole AWS relationship. Can you tell us how you're working with AWS before? >>Yeah. 80 of us has been a great partner and one of the first cloud providers to ever provide GPS the cloud, uh, we most more recently we've announced two new instances, uh, the instance, which is based on the RA 10 G GPU, which has it was supports the Nvidia RTX technology or rendering technology, uh, for real-time Ray tracing and graphics and game streaming is their highest performance graphics, enhanced replicate without allows for those high performance graphics applications to be directly hosted in the cloud. And of course runs everything else as well, including our AI has access to our AI technology runs all of our AI stacks. We also announced with AWS, the G 5g instance, this is exciting because it's the first, uh, graviton or ARM-based processor connected to a GPU and successful in the cloud. Um, this makes, uh, the focus here is Android gaming and machine learning and France. And we're excited to see the advancements that Amazon is making and AWS is making with arm and the cloud. And we're glad to be part of that journey. >>Well, congratulations. I remember I was just watching my interview with James Hamilton from AWS 2013 and 2014. He was getting, he was teasing this out, that they're going to build their own, get in there and build their own connections, take that latency down and do other things. This is kind of the harvest of all that. As you start looking at these new new interfaces and the new servers, new technology that you guys are doing, you're enabling applications. What does, what do you see this enabling as this, as this new capability comes out, new speed, more, more performance, but also now it's enabling more capabilities so that new workloads can be realized. What would you say to folks who want to ask that question? >>Well, so first off I think arm is here to stay and you can see the growth and explosion of my arm, uh, led of course, by grab a tiny to be. I spend many others, uh, and by bringing all of NVIDIA's rendering graphics, machine learning and AI technologies to arm, we can help bring that innovation. That arm allows that open innovation because there's an open architecture to the entire ecosystem. Uh, we can help bring it forward, uh, to the state of the art in AI machine learning, the graphics. Um, we all have our software that we released is both supportive, both on x86 and an army equally, um, and including all of our AI stacks. So most notably for inference the deployment of AI models. We have our, the Nvidia Triton inference server. Uh, this is the, our inference serving software where after he was trained to model, he wanted to play it at scale on any CPU or GPU instance, um, for that matter. So we support both CPS and GPS with Triton. Um, it's natively integrated with SageMaker and provides the benefit of all those performance optimizations all the time. Uh, things like, uh, features like dynamic batching. It supports all the different AI frameworks from PI torch to TensorFlow, even a generalized Python code. Um, we're activating how activating the arm ecosystem as well as bringing all those AI new AI use cases and all those different performance levels, uh, with our partnership with AWS and all the different clouds. >>And you got to making it really easy for people to use, use the technology that brings up the next kind of question I want to ask you. I mean, a lot of people are really going in jumping in the big time into this. They're adopting AI. Either they're moving in from prototype to production. There's always some gaps, whether it's knowledge, skills, gaps, or whatever, but people are accelerating into the AI and leaning into it hard. What advancements have is Nvidia made to make it more accessible, um, for people to move faster through the, through the system, through the process? >>Yeah, it's one of the biggest challenges. The other promise of AI, all the publications that are coming all the way research now, how can you make it more accessible or easier to use by more people rather than just being an AI researcher, which is, uh, uh, obviously a very challenging and interesting field, but not one that's directly in the business. Nvidia is trying to write a full stack approach to AI. So as we make, uh, discover or see these AI technologies come available, we produce SDKs to help activate them or connect them with developers around the world. Uh, we have over 150 different STKs at this point, certain industries from gaming to design, to life sciences, to earth scientist. We even have stuff to help simulate quantum computing. Um, and of course all the, all the work we're doing with AI, 5g and robotics. So, uh, we actually just introduced about 65 new updates just this past month on all those SDKs. Uh, some of the newer stuff that's really exciting is the large language models. Uh, people are building some amazing AI. That's capable of understanding the Corpus of like human understanding, these language models that are trained on literally the continent of the internet to provide general purpose or open domain chatbots. So the customer is going to have a new kind of experience with a computer or the cloud. Uh, we're offering large language, uh, those large language models, as well as AI frameworks to help companies take advantage of this new kind of technology. >>You know, each and every time I do an interview with Nvidia or talk about Nvidia my kids and their friends, they first thing they said, you get me a good graphics card. Hey, I want the best thing in their rig. Obviously the gaming market's hot and known for that, but I mean, but there's a huge software team behind Nvidia. This is a well-known your CEO is always talking about on his keynotes, you're in the software business. And then you had, do have hardware. You were integrating with graviton and other things. So, but it's a software practices, software. This is all about software. Could you share kind of more about how Nvidia culture and their cloud culture and specifically around the scale? I mean, you, you hit every, every use case. So what's the software culture there at Nvidia, >>And it is actually a bigger, we have more software people than hardware people, people don't often realize this. Uh, and in fact that it's because of we create, uh, the, the, it just starts with the chip, obviously building great Silicon is necessary to provide that level of innovation, but as it expanded dramatically from then, from there, uh, not just the Silicon and the GPU, but the server designs themselves, we actually do entire server designs ourselves to help build out this infrastructure. We consume it and use it ourselves and build our own supercomputers to use AI, to improve our products. And then all that software that we build on top, we make it available. As I mentioned before, uh, as containers on our, uh, NGC container store container registry, which is accessible for me to bus, um, to connect to those vertical markets, instead of just opening up the hardware and none of the ecosystem in develop on it, they can with a low-level and programmatic stacks that we provide with Kuda. We believe that those vertical stacks are the ways we can help accelerate and advance AI. And that's why we make as well, >>Ram a little software is so much easier. I want to get that plug for, I think it's worth noting that you guys are, are heavy hardcore, especially on the AI side. And it's worth calling out, uh, getting back to the customers who are bridging that gap and getting out there, what are the metrics they should consider as they're deploying AI? What are success metrics? What does success look like? Can you share any insight into what they should be thinking about and looking at how they're doing? >>Yeah. Um, for training, it's all about time to solution. Um, it's not the hardware that that's the cost, it's the opportunity that AI can provide your business and many, and the productivity of those data scientists, which are developing, which are not easy to come by. So, uh, what we hear from customers is they need a fast time to solution to allow people to prototype very quickly, to train a model to convergence, to get into production quickly, and of course, move on to the next or continue to refine it often. So in training is time to solution for inference. It's about our, your ability to deploy at scale. Often people need to have real time requirements. They want to run in a certain amount of latency, a certain amount of time. And typically most companies don't have a single AI model. They have a collection of them. They want, they want to run for a single service or across multiple services. That's where you can aggregate some of your infrastructure leveraging the trading infant server. I mentioned before can actually run multiple models on a single GPU saving costs, optimizing for efficiency yet still meeting the requirements for latency and the real time experience so that your customers have a good, a good interaction with the AI. >>Awesome. Great. Let's get into, uh, the customer examples. You guys have obviously great customers. Can you share some of the use cases, examples with customers, notable customers? >>Yeah. I want one great part about working in videos as a technology company. You see, you get to engage with such amazing customers across many verticals. Uh, some of the ones that are pretty exciting right now, Netflix is using the G4 instances to CLA um, to do a video effects and animation content. And, you know, from anywhere in the world, in the cloud, uh, as a cloud creation content platform, uh, we work in the energy field that Siemens energy is actually using AI combined with, um, uh, simulation to do predictive maintenance on their energy plants, um, and, and, uh, doing preventing or optimizing onsite inspection activities and eliminating downtime, which is saving a lot of money for the engine industry. Uh, we have worked with Oxford university, uh, which is Oxford university actually has over two, over 20 million artifacts and specimens and collections across its gardens and museums and libraries. They're actually using convenient GPS and Amazon to do enhance image recognition, to classify all these things, which would take literally years with, um, uh, going through manually each of these artifacts using AI, we can click and quickly catalog all of them and connect them with their users. Um, great stories across graphics, about cross industries across research that, uh, it's just so exciting to see what people are doing with our technology together with, >>And thank you so much for coming on the cube. I really appreciate Greg, a lot of great content there. We probably going to go another hour, all the great stuff going on in the video, any closing remarks you want to share as we wrap this last minute up >>Now, the, um, really what Nvidia is about as accelerating cloud computing, whether it be AI, machine learning, graphics, or headphones, community simulation, and AWS was one of the first with this in the beginning, and they continue to bring out great instances to help connect, uh, the cloud and accelerated computing with all the different opportunities integrations with with SageMaker really Ks and ECS. Uh, the new instances with G five and G 5g, very excited to see all the work that we're doing together. >>Ian buck, general manager, and vice president of accelerated computing. I mean, how can you not love that title? We want more, more power, more faster, come on. More computing. No, one's going to complain with more computing know, thanks for coming on. Thank you. Appreciate it. I'm John Farrell hosted the cube. You're watching Amazon coverage reinvent 2021. Thanks for watching.

>>mhm Yes. >>Hello and welcome back to the cubes coverage of dr khan 2021 virtual. I'm john Kerry hosted the Q got a great cube segment here. Simon Maple Field C T Oh it's technique. Great company security shifting left great to have you on Simon. Thanks for thanks for stopping by >>absolute pleasure. Thank you very much for having me. >>So you guys were on last year the big partnership with DR Conn remember that interview vividly because it was really the beginning at the beginning but really come to me the mainstream of shifting left as devops. It's not been it's been around for a while. But as a matter of practice as containers have been going super mainstream. Super ballistic in the developer community then you're seeing what's happening. It's containers everywhere. Security Now dev sec apps is the standard. So devops great infrastructure as code. We all know that but now it's def sec ops is standard. This is the real deal. Give us the update on what's going on with sneak. >>Absolutely, yeah. And you know, we're still tireless in our approach of trying to get make sure developers don't just have the visibility of security but are very much empowered in terms of actually fixing issues and secure development is what we're really striving for. So yeah, the update, we're still very, very deep into a partnership with DACA. We have updates on DR desktop which allows developers to scan the containers on the command line, providing developers that really fast feedback as as early as possible. We also have uh, you know, new updates and support for running Docker scan on Lennox. Um, and yeah, you know, we're still there on the Docker hub and providing that security insights um, to, to users who are going to Docker hub to grab their images. >>Well, for the folks watching maybe for the first time, the sneak Docker partnership, we went in great detail last year was the big reveal why Docker and sneak partnership, what is the evolution of that partnership over the year? They speak highly of you guys as a developer partner. Why Doctor? What's the evolution looked like? >>It's a it's a really great question. And I think, you know, when you look at the combination of DACA and sneak well actually let's take let's take each as an individual. Both companies are very, very developer focused. First of all, right, so our goals and will be strife or what we what we tirelessly spend their time doing is creating features and creating, creating an environment in which a developer you can do what they need to do as easily as possible. And that, you know, everyone says they want to be developer friendly, They want to be developer focused. But very few companies can achieve. And you look at a company like doctor, you're a company like sneak it really, really provides that developer with the developer experience that they need to actually get things done. Um, and it's not just about being in a place that a developer exists. It's not enough to do that. You need to provide a developer with that experience. So what we wanted to do was when we saw doctor and extremely developer friendly environment and a developer friendly company, when we saw the opportunity there to partner with Yoko, we wanted to provide our security developer friendliness and developer experience into an already developed a friendly tool. So what the partnership provides is the ease of, you know, deploying code in a container combined with the ease of testing your code for security issues and fixing security issues in your code and your container and pulling it together in one place. Now, one of the things which we as a as a security company um pride ourselves on is actually not necessarily saying we provide security tools. One of what our favorite way of saying is we're a developer tooling company. So we provide tools that are four developers now in doing that. It's important you go to where the developers are and developers on DACA are obviously in places like the Docker hub or the Docker Cli. And so it's important for us to embed that behavior and that ease of use inside Dhaka for us to have that uh that that flow. So the developer doesn't need to leave the Docker Cli developer that doesn't need to leave Docker hub in order to see that data. If you want to go deeper, then there are probably easier ways to find that data perhaps with sneak or on the sneak site or something like that. But the core is to get that insight to get that visibility and to get that remediation, you can see that directly in in the in the Dhaka environment. And so that's what makes the relationship so so powerful. The fact that you combine everything together and you do it at source >>and doing it at the point of code. >>Writing >>code is one of the big things I've always liked about the value proposition is simple shift left. Um So let's just step back for a second. I got to ask you this question because this I wanted to make sure we get this on the table. What are the main challenges uh and needs to, developers have with container security? What are you seeing as the main top uh A few things that they need to have right now for the challenges uh with container security? >>Yeah, it's a it's a very good question. And I think to answer that, I think we need to um we need to think of it in a couple of ways. First of all, you've just got developers security uh in general, across containers. Um And the that in itself is there are different levels at which developers engage with containers. Um In some organizations, you have security teams that are very stringent in terms of what developers can and can't do in other organizations. It's very much the developer that that chooses their environment, chooses their parent image, et cetera. And so there when a developer has many, many choices in which they need to need to decide on, some of those choices will lead to more issues, more risk. And when we look at a cloud native environment, um uh Let's take let's take a node uh image as an example, the number of different uh images tags you can choose from as a developer. It's you know, there are hundreds, probably thousands. That you can actually you can actually choose. What is the developer gonna do? Well, are they going to just copy paste from another doctor file, for example, most likely. What if there are issues in that docker file? They're just gonna copy paste that across mis configurations that exist. Not because the developer is making the wrong decision, but because the developer very often doesn't necessarily know that they need to add a specific directive in. Uh So it's not necessarily what you add in a conflict file, but it's very often what you admit. So there are a couple of things I would say from a developer point of view that are important when we think about cloud security, the first one is just that knowledge that understanding what they need to do, why they need to do it. Secure development doesn't need to be, doesn't mean they need to be deep in security. It means they need to understand how they can develop securely and what what the best decisions that could come from guard rails, from the security team that they provide the development team to offer. But that's the that's an important error of secure development. The second thing and I think one of the most important things is understanding or not understanding necessarily, but having the information to get an act on those things early. So we know the length of time that developers are uh working on a branch or working on um some some code changes that is reducing more and more and more so that we can push to production very, very quickly. Um What we need to do is make sure that as a developer is making their changes, they can make the right decision at the right time and they have the right information at that time. And a lot of this could be getting information from tools, could be getting information from your team where it could be getting information from your production environments and having that information early is extremely important to make. That decision. May be in isolation with your team in an autonomous way or with advice from the security team. But I would say those are the two things having that information that will allow you to make that action, that positive change. Um uh and and yeah, understanding and having that knowledge about how you can develop security. >>All right. So I have a security thing. So I'm a development team and by the way, this whole team's thing is a huge deal. I think we'll get to that. I want to come back to that in a second but just throw this out there. Got containers, got some security, it's out there and you got kubernetes clusters where containers are coming and going. Sometimes containers could have malware in them. Um and and this is, I've heard this out and about how do how that happens off container or off process? How do you know about it? Is that infected by someone else? I mean is it gonna be protected? How does the development team once it's released into the wild, so to speak. Not to be like that, but you get the idea, it's like, okay, I'm concerned off process this containers flying around. What is it How do you track all >>and you know, there's a there's a few things here that are kind of like potential potential areas that, you know, we can trip up when we think about malware that's running um there are certain things that we need to that we need to consider and what we're really looking at here are kind of, what do we have in place in the runtime that can kind of detect these issues are happening? How do we block that? And how do you provide that information back to the developer? The area that I think is, and that is very, very important in order to in order to be able to identify monitor that those environments and then feed that back. So that that that's the kind of thing that can be that can be fixed. Another aspect is, is the static issues and the static issues whether that's in your os in your OS packages, for example, that could be key binaries that exist in your in your in your docker container out the box as well or of course in your application, these are again, areas that are extremely important to detect and they can be detected very very early. So some things, you know, if it's malware in a package that has been identified as malware then absolutely. That can be that can be tracked very very early. Sometimes these things need to be detected a little bit later as well. But yeah, different tools for different for different environments and wear sneak is really focused. Is this static analysis as early as possible. >>Great, great insight there. Thanks for sharing that certainly. Certainly important. And you know, some companies classes are locked down and all of sudden incomes, you know, some some malware from a container, people worried about that. So I want to bring that up. Uh The other thing I want to ask you is this idea of end to end security um and this is a team formation thing we're seeing where modern teams have essentially visibility of their workload and to end. So this is a huge topic. And then by the way it might integrate their their app might integrate with other processes to that's great for containers as well and observe ability and microservices. So this is the trend. What's in it for the developer? If I work with sneak and docker, what benefits do I get if I want to go down that road of having these teams began to end, but I want the security built in. >>Mhm. Yeah, really, really important. And I think what's what's most important there is if we don't look end to end, there are component views and there are applications. If we don't look into end, we could have our development team fixing things that realistically aren't in production anyway or aren't the key risks that are potentially hurting us in our production environment. So it's important to have that end to end of you so that we have the right insights and can prioritize what we need to identify and look at early. Um, so I think, I think that visibility into end is extremely important. If we think about who, who is re fixing uh certain issues, again, this is gonna depend from dog to walk, but what we're seeing more and more is this becoming a developer lead initiative to not just find or be given that information, but ultimately fixed. They're getting more and more responsible for DR files for for I see for for their application code as well. So one of the areas which we've looked into as well is identifying and actually running in cuba Netease workloads to identify where the most important areas that a developer needs to look at and this is all about prioritization. So, you know, if the developer has just a component view and they have 100 different images, 100 different kubernetes conflicts, you know, et cetera. Where do they prioritize, where do they spend their time? They shouldn't consider everything equal. So this identification of where the workloads are running and what um is causing you the most risk as a business and as an organization, that is the data. That can be directly fed back into your, your your vulnerability data and then you can prioritize based on the kubernetes workloads that are in your production and that can be fed directly into the results in the dashboards. That's neat. Can provide you as well. So that end to end story really provides the context you need in order to not just develop securely, but act and action issues in a proper way. >>That's a great point. Context matters here because making it easy to do the right thing as early as possible, the right time is totally an efficiency productivity gain, you see in that that's clearly what people want. It's a great formula, success, reduce the time it takes to do something, reduced the steps and make it easy. Right, come on, that's a that's a formula. Okay, so I gotta bring that to the next level. When I ask you specifically around automation, this is one the hot topic and def sec ops, automation is part of it. You got scale, you got speed, you've got a I machine learning, you go out of all these new things. Microservices, how do you guys fit into the automation story? >>It's a great question. And you know, one of the recent reports that we that we did based on a survey data this year called the state of a state of cloud, native applications security. We we asked the question how automated our people in their in their deployment pipelines and we found some really strong correlations between value from a security point of view um in terms of in terms of having that automation in it, if I can take you through a couple of them and then I'll address that question about how we can be automated in that. So what we found is a really strong correlation as you would expect with security testing in ci in your source code repositories and all the way through the deployment ci and source code were the two of the most most well tested areas across the pipeline. However the most automated teams were twice as likely to test in I. D. S. And testing your CLS in local development. And now those are areas that are really hard to automate if at all because it's developers running running their cli developers running and testing in their I. D. So the having a full automation and full uh proper testing throughout the sclc actually encourages and and makes developers test more in their development environment. I'm not saying there's causation there but there's definite correlation. A couple of other things that this pushes is um Much much more likely to test daily or continuously being automated as you would expect because it's part of the bills as part of your monitoring. But crucially uh 73% of our respondents were able to fix a critical issue in less than a week as opposed to just over 30% of people that were not automated, so almost double people are More likely to fix within a week. 36% of people who are automated can fix a critical security issue in less than a day as opposed to 8% of people who aren't automated. So really strong data that correlates being automated with being able to react now. If you look at something like Sneak what if our um goals of obviously being developer friendly developer first and being able to integrate where developers are and throughout the pipeline we want to test everywhere and often. Okay, so we start as far left as we can um integrating into, you know, CLS integrating into Docker hub, integrating into into doctors can so at the command line you type in doctors can you get sneak embedded in DHAKA desktop to provide you those results so as early as possible, you get that data then all the way through to to uh get reposed providing that testing and automatically testing and importing results from there as well as as well as other repositories, container repositories, being at a poor from there and test then going into ci being able to run container tests in C I to make sure we're not regressing and to choose what we want to do their whether we break, whether we continue with with raising an issue or something like that, and then continuing beyond that into production. So we can monitor tests and automatically send pull requests, etcetera. As and when new issues or new fixes occur. So it's about integrating at every single stage, but providing some kind of action. So, for example, in our ui we provide the ability to say this is the base level you should be or could be at, it will reduce your number of vulnerabilities by X and as a result you're going to be that much more secure that action ability across the pipeline. >>That's a great, great data dump, that's a masterclass right there on automation. Thanks for sharing that sign. I appreciate it. I gotta ask you the next question that comes to my mind because I think this is kind of the dots connect for the customer is okay. I love this kind of hyper focus on containers and security. You guys are all over it, shift left as far as possible, be there all the time, test, test, test all through the life cycle of the code. Well, the one thing that is popping up as a huge growth areas, obviously hybrid cloud devops across both environments and the edge, whether it's five G industrial or intelligent edge, you're gonna have kubernetes clusters at the edge now. So you've got containers. The relationship to kubernetes and then ultimately cloud native work clothes at, say, the edge, which has data has containers. So there's a lot of stuff going on all over the place. What's your, what's your comment there for customer says, Hey, you know, I got, this is my architecture that's happening to me now. I'm building it out. We're comfortable with kubernetes put in containers everywhere, even on the edge how to sneak fit into that story. >>Yeah, really, really great question. And I think, you know, a lot of what we're doing right now is looking at a developer platform. So we care about, we care about everything that a developer can check in. Okay, so we care about get, we care about the repositories, we care about the artifact. So um, if you look at the expansion of our platform today, we've gone from code that people uh, third party libraries that people test. We added containers. We've also added infrastructure as code. So Cuban eighties conflicts, Terror form scripts and things like that. We're we're able to look at everything that the developer touches from their code with sneak code all the way through to your to your container. And I see, so I think, you know, as we see more and more of this pushing out into the edge, cuba Nitties conflict that that, you know, controls a lot of that. So much of this is now going to be or not going to be, but so much of the environment that we need to look at is in the configurations or the MIS configurations in that in those deployment scripts, um, these are some of the areas which which we care a lot about in terms of trying to identify those vulnerabilities, those miS configurations that exist within within those scripts. So I can see yeah more and more of this and there's a potential shift like that across to the edge. I think it's actually really exciting to be able to see, to be able to see those uh, those pushing across. I don't necessarily see any other, any, you know, different security threats or the threat landscape changing as a result of that. Um there could be differences in terms of configurations, in terms of miS configurations that that that could increase as a result, but, you know, a lot of this and it just needs to be dealt with in the appropriate way through tooling through, through education of of of of how that's done. >>Well, obviously threat vectors are all gonna look devops like there's no perimeter. So they're everywhere right? Looking at I think like a hacker to be being there. Great stuff. Quick question on the future relationship with DR. Obviously you're betting a lot here on that container relationship, a good place to start. A lot of benefits there. They have dependencies, they're going to have implications. People love them, they love to use them, helps old run with the new and helps the new run better. Certainly with kubernetes, everything gets better together. What's the future with the DACA relationship? Take us through how you see it. >>So yeah, I mean it's been an absolute blast the doctor and you know, even from looking at some of the internal internal chats, it's been it's been truly wonderful to see the, the way in which both the doctor and sneak from everything from an engineering point of view from a marketing, from a product team. It's been a pleasure to, it's been a pleasure to see that relationship grow and flourish. And, and I think there's two things, first of all, I think it's great that as companies, we, we both worked very, very well together. I think as as as users um seeing, you know, doctor and and and sneak work so so seamlessly and integrated a couple of things. I would love to see. Um, I think what we're gonna see more and more and this is one of the areas that I think, um you know, looking at the way sneak is going to be viewing security in general. We see a lot of components scanning a lot, a lot of people looking at a components can and seeing vulnerabilities in your components. Can I think what we need to, to to look more upon is consolidating a lot of the a lot of the data which we have in and around different scans. What I would love to see is perhaps, you know, if you're running something through doctors can how can you how can you view that data through through sneak perhaps how can we get that closer integration through the data that we that we see. So I would love to see a lot more of that occur, you know, within that relationship and these are kind of like, you know, we're getting to that at that stage where we see integration, it just various levels. So we have the integration where we have we are embedded but how can we make that better for say a sneak user who also comes to the sneak pages and wants to see that data through sneak. So I would love to see at that level uh more there where as I mentioned, we have we have some some additional support as well. So you can run doctors can from from Lenox as well. So I can see more and more of that support rolling out but but yeah, in terms of the future, that's where I would love to see us uh to grow more >>and I'll see in the landscape side on the industry side, um, security is going beyond the multiple control planes out there. Kubernetes surveillance service matches, etcetera, continues to be the horizontally scalable cloud world. I mean, and you got you mentioned the edge. So a lot more complexity to rein in and make easier. >>Yeah, I mean there's a lot more complexity, you know, from a security point of view, the technology is the ability to move quickly and react fast in production actually help security a lot because you know, being able to spin a container and make changes and and bring a container down. These things just weren't possible, you know, 10 years ago, 20 years ago. Pre that it's like it was it's insanely hard compared trying to trying to do that compared to just re spinning a container up. However, the issue I see from a security point of view, the concerns I see is more around a culture and an education point of view of we've got all this great tech and it's it's awesome but we need to do it correctly. So making sure that as you mentioned with making the right decision, what we want to make sure is that right decision is also the easy decision and the clear decision. So we just need to make sure that as we as we go down this journey and we're going down it fast and it's not gonna, I don't see it slowing down, we're going fast down that journey. How do we make, how do we prepare ourselves for that? We're already seeing, you know, miss configurations left, right and center in the news, I am roles as three buckets, etcetera. These are they're they're simpler fixes than we than we believe, right? We just need to identify them and and make those changes as needed. So we just need to make sure that that is in place as we go forward. But it's exciting times for sure. >>It's really exciting. And you got the scanning and right at the point of coding automation to help take that basic mis configuration, take that off the table. Not a lot of manual work, but ultimately get to that cloud scale cool stuff. >>Simon, thank you >>for coming on the cube dr khan coverage. Really appreciate your time. Drop some nice commentary there. Really appreciate it. Thank you. >>My pleasure. Thank you very much. >>Simon Maple Field C T. O. A sneak hot startup. Big partner with Docker Security, actually built in deVOPS, is now dead. Say cops. This is dr khan cube 2021 virtual coverage. I'm sean for your host. Thanks for watching. Mm.

>>from around the globe. It's the Cube presenting accelerating automation with definite brought to you by Cisco. >>Hello and welcome to the Cube. I'm John for a year host. We've got a great conversation virtual event, accelerating automation with definite Cisco. Definite. And of course, we got the Cisco Brain Trust here. Cube alumni Suzy we Vice President, senior Vice President GM and also CTO of Cisco. Definite and ecosystem Success C X, All that great stuff. Many Wadley Who's the director? Senior director of definite certifications. Eric Field, director of developer advocacy. Susie Mandy. Eric, Great to see you. Thanks for coming on. >>Great to see you down. So >>we're not in >>person. We >>don't Can't be at the definite zone. We can't be on site doing definite created All the great stuff we've been doing in the past three years were virtual the cube Virtual. Thanks for coming on. Uh, Susie, I gotta ask you because you know, we've been talking years ago when you started this mission and just the succession had has been awesome. But definite create has brought on a whole nother connective tissue to the definite community. This is what this ties into the theme of accelerating automation with definite because you said to me, I think four years ago everything should be a service or X a s is it's called and automation plays a critical role. Um, could you please share your vision? Because this is really important. And still only 5 to 10% of the enterprises have containerized things. So there's a huge growth curve coming with developing and program ability. What's your What's your vision? >>Yeah, absolutely. I mean, what we know is that is, more and more businesses are coming online is I mean, they're all online, But is there growing into the cloud? Is their growing in new areas as we're dealing with security is everyone's dealing with the pandemic. There's so many things going on. But what happens is there's an infrastructure that all of this is built on and that infrastructure has networking. It has security. It has all of your compute and everything that's in there. And what matters is how can you take a business application and tie it to that infrastructure. How can you take, you know, customer data? How can you take business applications? How can you connect up the world securely and then be ableto really satisfy everything that businesses need. And in order to do that, you know, the whole new tool that we've always talked about is that the network is programmable, the infrastructure is programmable, and you don't need just acts writing on top. But now they get to use all of that power of the infrastructure to perform even better. And in order to get there, what you need to do is automate everything. You can't configure networks manually. You can't be manually figuring out policies, but you want to use that agile infrastructure in which you can really use automation. You can rise to a higher level business processes and tie all of that up and down the staff by leveraging automation. >>You remember a few years ago when definite create first started, I interviewed Todd Nightingale and we're talking about Muraki. You know, not to get in the weeds, but you know, switches and hubs and wireless. But if you look at what we were talking about, then this is kind of what's going on now. And we were just recently, I think our last physical event was Cisco um Europe in Barcelona before all the cove it hit and you had the massive cloud surgeon scale happening going on right when the pandemic hit. And even now, more than ever, the cloud scale the modern APS. The momentum hasn't stopped because there's more pressure now to continue addressing Mawr innovation at scale. Because the pressure to do that because >>the stay alive get >>your thoughts on, um, what's going on in your world? Because you were there in person. Now we're six months in scale is huge. >>We are, Yeah, absolutely. And what happened is as all of our customers as businesses around the world as we ourselves all dealt with, How do we run a business from home? You know, how do we keep people safe? How do we keep people at home and how do we work? And then it turns out, you know, business keeps rolling, but we've had to automate even more because >>you >>have to go home and then figure out how from home can I make sure that my I t infrastructure is automated out from home? Can I make sure that every employee is out there in working safely and securely? You know, things like call center workers, which had to go into physical locations and being kind of, you know, just, you know, blocked off rooms to really be secure with their company's information. They had to work from home. So we had to extend business applications to people's homes in countries like, you know, well around the world. But also in India, where it was actually not, you know, not they wouldn't let They didn't have rules toe let people work from home in these areas. So then what we had to do was automate everything and make sure that we could administer. You know, all of our customers could administer these systems from home, so that puts extra stress on automation. It puts extra stress on our customers digital transformation. And it just forced them toe, you know, automate digitally transform quicker. And they had to because you couldn't just go into a server room and tweak your servers. You have to figure out how to automate all of that. >>You know, one of them >>were still there, all in that environment today. >>You know, one of the hottest trends before the pandemic was observe ability, uh, kubernetes serve micro services. So those things again. All Dev ups. And you know, if you guys got some acquisitions, you thought about 1000 eyes. Um, you got a new one you just bought recently Port shift to raise the game in security, Cuban, All these micro services, So observe, ability, superhot. But then people go work at home, as you mentioned. How do you think? Observe, What do you observing? The network is under huge pressure. I mean, it's crashing on. People zooms and WebEx is and education, huge amount of network pressure. How are people adapting to this in the upside? How are you guys looking at the what's being programmed? What are some of the things that you're seeing with use cases around this program? Ability, challenge and observe ability, challenges? It's a huge deal. >>Yeah, absolutely. And, you know, going back to Todd Nightingale, right? You know, back when we talked to Todd before he had Muraki and he had designed this simplicity, this ease of use, this cloud managed, you know, doing everything from one central place. And now he has This goes entire enterprise and cloud business. So he is now applying that at that Bigger Attn. Bigger scale. Francisco and for our customers. And he is building in the observe ability and the dashboards and the automation of the A P. I s and all of it. But when we take a look at what our customers needed is again, they had to build it all in, um, they had to build in. And what happened was how your network was doing, how secure your infrastructure was, how well you could enable people toe work from home and how well you could reach customers. All of that used to be a nightie conversation. It became a CEO and a board level conversation. So all of a sudden CEOs were actually, you know, calling on the heads of I t and the CEO and saying, You know, how is our VPN connectivity? Is everybody working from home? How many people are, you know, connected and ableto work and watch their productivity? Eso All of a sudden, all these things that were really infrastructure I t stuff became a board level conversation and you know, once again, at first everybody was panicked and just figuring out how to get people working. But now what we've seen in all of our customers is that they're now building in automation, additional transformation and these architectures, and that gives them a chance to build in that observe ability. You know, looking for those events. The dashboards, you know? So it really has been fantastic to see what our customers are doing and what our partners air doing to really rise to that next level. >>Susan, I know you gotta go, but real quick, um, describe what? Accelerating automation with definite means. >>Well, you've been fault. You know, we've been working together on definite in the vision of the infrastructure program ability and everything for quite some time. And the thing that's really happened is yes, you need to automate, but yes, it takes people to do that. And you need the right skill sets in the program ability. So a networker can't be a networker. A networker has to be a network automation developer. And so it is about people. And it is about bringing infrastructure expertise together with software expertise and letting people run. Things are definite. Community has risen to this challenge. People have jumped in. They've gotten their certifications. We have thousands of people getting certified. You know, we have you know, Cisco getting certified. We have individuals. We have partners, you know, They're just really rising to the occasion. So accelerate accelerating automation while it is about going digital. It's also about people rising to the level of, you know, being able to put infrastructure and software expertise together to enable this next chapter of business applications of cloud directed businesses and cloud growth. So it actually is about people, Justus, much as it is about automation and technology. >>And we got definite create right around the corner virtual. Unfortunately, being personal will be virtual Susie. Thank you for your time. We're gonna dig into those people challenges with Mandy and Eric. Thank you for coming on. I know you got to go, but stay with us. We're gonna dig in with Mandy and Eric. Thanks. >>Thank you so much. Thank you. Thanks, John. Okay. >>Mandy, you heard Susie is about people, and one of the things that's close to your heart you've been driving is a senior director of definite certifications. Um is getting people leveled up? I mean, the demand for skills cybersecurity, network program, ability, automation, network design solution, architect cloud multi cloud design thes are new skills that are needed. Can you give us the update on what you're doing to help people get into the acceleration of automation game? >>Oh, yes, absolutely. The you know what we've been seeing is a lot of those business drivers that Susie was mentioning those air. What's accelerating? A lot of the technology changes, and that's creating new job roles or new needs on existing job roles where they need new skills. We are seeing, uh, customers, partners, people in our community really starting to look at, you know, things like Dev SEC ops engineer, network Automation engineer, network automation developer, which sues you mentioned and looking at how these fit into their organization, the problems that they solve in their organization. And then how do people build the skills to be able to take on these new job roles or add that job role to their current, um, scope and broaden out and take on new challenges? >>Eric, I want to go to you for a quick second on this, um uh, piece of getting the certifications. Um, first, before you get started, describe what your role is. Director of developer advocacy, because that's always changing and evolving what's the state of it now? Because with Cove and people are working at home, they have more time to contact, switch and get some certifications and that they can code more. What's your >>What's your role? Absolutely So it's interesting. It definitely is changing a lot. A lot of our historically a lot of focus for my team has been on those outward events. So going to the definite creates the Cisco lives and helping the community connect and help share technical information with them, doing hands on workshops and really getting people into. How do you really start solving these problems? Eso that's had to pivot quite a bit. Obviously, Sisco live us. We pivoted very quickly to a virtual event when when conditions changed and we're able to actually connect, as we found out with a much larger audience. So you know, as opposed to in person where you're bound by the parameters of you know how big the convention center is. We were actually able to reach a worldwide audience with are definite day that was kind of attached onto Sisco Live, and we got great feedback from the audience that now we're actually able to get that same enablement out to so many more people that otherwise might not have been able to make it. But to your broader question of you know what my team does. So that's one piece of it is is getting that information out to the community. So as part of that, there's a lot of other things we do as well. We were always helping out build new sandboxes, new learning labs, things like that that they can come and get whenever they're looking for it out on the definite site. And then my team also looks after communities such as the Cisco Learning Network, where there's there's a huge community that has historically been there to support people working on their Cisco certifications. We've seen a huge shift now in that group that all of the people that have been there for years are now looking at the definite certifications and helping other people that are trying to get on board with program ability. They're taking a lot of those same community enablement skills and propping up community with, you know, helping answer questions, helping provide content. They move now into the definite spaces well and are helping people with that sort of certifications. So it's great seeing the community come along and really see that >>I gotta ask you on the trends around automation. What skills and what developer patterns are you seeing with automation? Are Is there anything in particular? Obviously, network automation been around for a long time. Cisco's been leader in that. But as you move up, the staff has modern applications or building. Do you see any patterns or trends around what is accelerating automation? What people learning? >>Yeah, absolutely. So you mentioned observe ability was big before Cove it and we actually really saw that amplified during co vid. So a lot of people have come to us looking for insights. How can I get that better observe ability now that we needed? Well, we're virtual eso. That's actually been a huge uptick, and we've seen a lot of people that weren't necessarily out looking for things before that air. Now, figuring out how can I do this at scale? I think one good example that Susie was talking about the VPN example, and we actually had a number of SCS in the Cisco community that had customers dealing with that very thing where they very quickly had to ramp up and one in particular actually wrote a bunch of automation to go out and measure all of the different parameters that I T departments might care about about their firewalls, things that you didn't normally look at. The old days you would size your firewalls based on, you know, assuming a certain number of people working from home. And when that number went to 100% things like licenses started coming into play where they need to make sure they had the right capacity in their platforms that they weren't necessarily designed for. So one of the essays actually wrote a bunch of code to go out, use them open source, tooling to monitor and alert on these things, and then published it so the whole community code could go out and get a copy of it. Try it out in their own environment. And we saw a lot of interest around that and trying to figure out Okay, now I could take that. I can adapt into what I need to see for my observe ability. >>That's great, Mandy, I want to get your thoughts on this, too, because as automation continues to scale. Um, it's gonna be a focus. People are at home. And you guys had a lot of content online for you. Recorded every session that in the definite zone learning is going on sometimes literally and non linearly. You've got the certifications, which is great. That's key. Great success there. People are interested. But what other learnings are you seeing? What are people, um, doing? What's the top top trends? >>Yeah. So what we're seeing is like you said, people are at home, they've got time, they want toe advance, their skill set. And just like any kind of learning, people want choice. They wanna be able to choose which matches their time that's available and their learning style. So we're seeing some people who want to dive into full online study groups with mentors leading them through a study plan. On we have two new expert lead study groups like that. We're also seeing whole teams at different companies who want to do an immersive learning experience together with projects and office hours and things like that. And we have a new offer that we've been putting together for people who want those kind of team experiences called Automation Boot Camp. And then we're also seeing individual who want to be able to, you know, dive into a topic, do a hands on lab, gets, um, skills, go to the rest of the day of do their work and then come back the next day. And so we have really modular, self driven hands on learning through the Definite Fundamentals course, which is available through DEV. Net. And then there's also people who are saying, I just want to use the technology. I like Thio experiment and then go, you know, read the instructions, read the manual, do the deeper learning. And so they're They're spending a lot of time in our definite sandbox, trying out different technologies. Cisco Technologies with open source technologies, getting hands on and building things, and three areas where we're seeing a lot of interest in specific technologies. One is around SD wan. There's a huge interest in people Skilling up there because of all the reasons that we've been talking about. Security is a focus area where people are dealing with new scale, new kinds of threats, having to deal with them in new ways and then automating their data center using infrastructure as code type principles. So those were three areas where we're seeing a lot of interest and you'll be hearing more about that at definite create. >>Awesome Eric and man, if you guys can wrap up the accelerated automated with definite package and virtual event here, um, and also t up definite create because definite create has been a very kind of grassroots, organically building momentum over the years. Again, it's super important because it's now the app world coming together with networking, you know, end to end program ability. And with everything is a service that you guys were doing everything with a piece. Um Onley can imagine the enablement that's gonna enable create Can >>you hear the >>memory real quick on accelerating automation with definite and TF definite create. Mandy will start with you. >>Yes, I'll go first, and then Eric can close this out. Um, so just like we've been talking about with you at every definite event over the past years, you know, Devon, it's bringing a p I s across our whole portfolio and up and down the stack and accelerating automation with definite. Suzy mentioned the people aspect of that the people Skilling up and how that transformed team transforms teams. And I think that it's all connected in how businesses are being pushed on their transformation because of current events. That's also a great opportunity for people to advance their careers and take advantage of some of that quickly changing landscape. And so would I think about accelerating automation with definite. It's about the definite community. It's about people getting those new skills and all the creativity and problem solving that will be unleashed by that community with those new skills. >>Eric, take us home. He accelerate automation. Definite and definite create a lot of developer action going on cloud native right now, your thoughts? >>Absolutely. I I think it's exciting. I mentioned the transition to virtual for definite day this year for Cisco Live, and we're seeing we're able to leverage it even further with create this year. So whereas it used to be, you know, confined by the walls that we were within for the event. Now we're actually able to do things like we're adding a start now track for people that I want to be there. They want to be a developer. Network automation developer, for instance, We've now got a track just for them where they could get started and start learning some of the skills they'll need, even if some of the other technical sessions were a little bit deeper than what they were ready for. Eso. I love that we're able to bring that together with the experience community that we usually do from across the industry, bringing us all kinds of innovative talks, talking about ways that they're leveraging technology, leveraging the cloud to do new and interesting things to solve their business challenges. So I'm really excited to bring that whole mixed together as well as getting some of our business units together to and talk straight from their engineering departments. What are they doing? What are they seeing? What are they thinking about when they're building new AP eyes into their platforms? What are the what problems are they hoping that customers will be able to solve with them? So I think together, seeing all of that and then bringing the community together from all of our usual channels. So, like I said, Cisco Learning Network, we've got a ton of community coming together, sharing their ideas and helping each other grow those skills. I see nothing but acceleration ahead of us for automation. >>Awesome. Thanks so much. God, man, can >>I add one had >>one more thing. >>Yeah, I was just going to say the other really exciting thing about create this year with the virtual nature of it is that it's happening in three regions. And, you know, we're so excited to see the people joining from all the different regions. And, uh, content and speakers and the region stepping upto have things personalized to their area to their community. And so that's a whole new experience for definite create that's going to be fantastic this year. >>You know, that's what God is going to close out and just put the final bow on that by saying that you guys have always been successful with great content focused on the people in the community. I think now, during with this virtual definite virtual definite create virtual the cube virtual, I think we're learning new things. People working in teams and groups on sharing content. We're gonna learn new things. We're gonna try new things, and ultimately people will rise up and will be resilient. I think when you have this kind of opportunity, it's really fun. And whoa, we'll ride the wave with you guys. So thank you so much for taking the time to come on. The Cuban talk about your awesome accelerate automation and definitely looking forward to it. Thank you. >>Thank you so much. >>Happy to be here. >>Okay, I'm John for the Cube. Virtual here in Palo Alto studios doing the remote content amendment Virtual until we're face to face. Thank you so much for watching. And we'll see you at definite create. Thanks for watching.

>>Hello everyone. This is Dave Vellante, and I want to welcome you to the cubes presentation of accelerating automation with dev net in this special program, we're going to explore how to accelerate digital transformation and how the global pandemic is changing the way we work and the kinds of work that we do, the cube has pulled together experts from Cisco dev net. Now dev net is essentially Cisco as code. I've said many times in the cube, but in my opinion, it's the most impressive initiative coming out of any established enterprise infrastructure company. What Cisco has done brilliantly with dev net is to create an API economy by leveraging its large infrastructure portfolio and its ecosystem. But the linchpin of dev net is the army of trained Cisco engineers, including those with the elite CC I E designation. Now dev net was conceived to train people on how to code infrastructure and develop applications in integrations. It's a platform to create new value and automation is a key to that. Creativity. Now let's kick things off with the architect of dev net senior vice president in general manager of Cisco's dev net and CX ecosystem success. Susie, we roam around the globe presenting accelerating automation with damnit brought to you by Cisco. >>Hello and welcome to the cube. I'm Sean for a year host. We've got a great conversation, a virtual event, accelerating automation with dev net, Cisco dev net. And of course we got the Cisco brain trust here, our cube alumni, Susie wee vice president, senior vice president GM, and also CTO of Cisco dev net and ecosystem success CX all that great stuff. Many Wade Lee, who's the director, senior director of dev net certifications, Eric field, director of developer advocacy, Susie Mandy, Eric. Great to see you. Thanks for coming on. Great to see you, John. So we're not in first. We don't, can't be at the dev net zone. We can't be on site doing dev net creative, all the great stuff we've been doing over the past few years where virtual the cube virtual. Thanks for coming on. Uh, Susie, I gotta ask you because you know, we've been talking years ago when you started this mission and just the success you've had has been awesome, but dev net create has brought on a whole nother connective tissue to the dev net community. This is what this ties into the theme of accelerating automation with dev net, because you said to me, I think four years ago, everything should be a service or X AAS as it's called and automation plays a critical role. Um, could you please share your vision because this is really important and still only five to 10% of the enterprises have containerized things. So there's a huge growth curve coming with developing and programmability. What's your, what's your vision? >>Yeah, absolutely. I mean, what we know is that as more and more businesses are >>Coming online is, I mean, they're all online, but as they're growing into the cloud is they're growing in new areas. As we're dealing with security is everyone's dealing with the pandemic. There's so many things going on. Uh, but what happens is there's an infrastructure that all of this is built on and that infrastructure has networking. It has security, it has all of your compute and everything that's in there. And what matters is how can you take a business application and tie it to that infrastructure? How can you take, you know, customer data? How can you take business applications? How can you connect up the world securely and then be able to, you know, really satisfy everything that businesses need. And in order to do that, you know, the whole new tool that we've always talked about is that the network is programmable. The infrastructure is programmable and you don't need just apps riding on top, but now they get to use all of that power of the infrastructure to perform even better. And in order to get there, what you need to do is automate everything. You can't configure networks manually. You can't be manually figuring out policies, but you want to use that agile infrastructure in which you can really use automation. You can rise to higher level business processes and tie all of that up and down the staff by leveraging automation. >>You know, I remember a few years ago when dev net created for start a, I interviewed Todd Nightingale and we were talking about Meraki, you know, not to get in the weeds, but you know, switches and hubs and wireless. But if you look at what we were talking about, then this is kind of what's going on now. And we were just recently, I think our last physical event was a Cisco, um, uh, Europe in Barcelona before all the COVID hit. And you had this massive cloud surgeon scale happening going on, right when the pandemic hit. And even now more than ever the cloud scale, the modern apps, the momentum hasn't stopped because there's more pressure now to continue addressing more innovation at scale because the pressure to do that, um, cause the business stay alive. And to get your thoughts on, um, what's going on in your world because you were there in person now we're six months in scale is huge. >>We are. Yeah, absolutely. And what happened is as all of our customers, as businesses around the world, as we ourselves all dealt with, how do we run a business from home? You know, how do we keep people safe? How do we keep people at home and how do we work? And then it turns out, you know, business keeps rolling, but we've had to automate even more because you have to go home and then figure out how from home, can I make sure that my it infrastructure is automated out from home? Can I make sure that every employee is out there and working safely and securely, you know, things like call center workers, which had to go into physical locations and be in kind of, you know, just, you know, blocked off rooms to really be secure with their company's information. They had to work from home. >>So we had to extend business applications to people's homes, uh, in countries like, you know, well around the world, but also in India where it was actually not, you know, not, they wouldn't let, they didn't have rules to let people work from home in these areas. So then what had to do was automate everything and make sure that we could administer, you know, all of our customers could administer these systems from home. So that put extra stress on automation. It put extra stress on our customer's digital transformation and it just forced them to, you know, automate digitally, transform quicker. And they had to, because you couldn't just go into a server room and tweak your servers, you had to figure out how to automate all of that. And we're still all in that environment today. >>Now one of the hottest trends before the pandemic was observability, uh, Coobernetti's serve, uh, microservices. So those things, again, all dev ops and, you know, have you guys got some acquisitions, you about thousand eyes? Um, um, you've got a new one you just bought, um, recently port shift to raise the game in security Cooper and all these microservices. So observability super hot, but then people go work at home. As you mentioned, how do you observe, what are you observing? The network is under a huge pressure. I mean, it's crashing on people's zooms and WebExes and, uh, education, huge amount of network pressure. How are people adapting to this and the app side? How are you guys looking at the what's being programmed? What are some of the things that you're seeing with use cases around this program? Ability, challenge and observability challenges. It's a huge deal. >>Yeah, absolutely. And, um, you know, going back to Todd Nightingale, right. You know, back when we talked to Todd before he had Meraki and he had designed this simplicity, this ease of use this cloud managed, you know, doing everything from one central place and now he has Cisco's entire enterprise and cloud business. So he is now applying that at that bigger, um, at that bigger scale for Cisco and for our customers. And he is building in the observability and the dashboards and the automation and the API APIs into all of it. Um, but when we take a look at what our customers needed is again, they had to build it all in. Um, they have to build in and what happened was how your network was doing, how secure your infrastructure was, how well you could enable people to work from home and how well you could reach customers. >>All of that used to be an it conversation. It became a CEO and a board level conversation. So all of a sudden CEOs were actually calling on the heads of it and the CIO and saying, you know, how's our VPN connectivity is everybody working from home? How many people are connected and able to work and what's their productivity. So all of a sudden, all these things that were really infrastructure, it stuff became a board level conversation. And, you know, once again, at first, everybody was panicked and just figuring out how to get people working. But now what we've seen in all of our customers is that they are now building in automation and digital transformation and these architectures, and that gives them a chance to build in that observability, you know, looking for those events, the dashboards, you know, so it really has, has been fantastic to see what our customers are doing and what our partners are doing to really rise to that next level. >>Cause you know, you got to go, but real quick, um, describe what accelerating automation with dev net means. Well, you've >>Been falling, you know, we've been working together on dev net and the vision of the infrastructure programmability and everything for quite some time. And the thing that's really happened is yes, you need to automate, but yes, it takes people to do that and you need the right skill sets and the programmability. So a networker can't be a networker. A networker has to be a network automation developer. And so it is about people and it is about bringing infrastructure expertise together with software expertise and letting people rumblings are definite community has risen to this challenge. Um, people have jumped in, they've gotten their certifications. We have thousands of people getting certified. Uh, you know, we have, you know, Cisco getting certified. We have individuals, we have partners, you know, they're just really rising to the occasion. So accelerate, accelerating automation while it is about going digital. It's also about people rising to the level of, you know, being able to put infrastructure and software expertise together to enable this next chapter of business applications of, you know, cloud directed businesses and cloud growth. So it actually is about people just as much as it is about automation and technology. >>We got dev net created right around the corner, virtual unfortunate won't be in person, but we'll be virtual. Susie. Thank you for your time. We're going to dig into those people, challenges with Mandy and Eric. Thank you for coming on. I know you've got to go, but stay with us. We're going to dig in with Mandy and Eric. >>Thanks. Thank you so much. Have fun. Thanks John. >>Okay. Mandy, you heard, uh, Susie is about people and one of the things that's close to your heart and you've been driving is, uh, as senior director of dev net certifications, um, is getting people leveled up. I mean the demand for skills, cybersecurity network, programmability automation, network design solution architect, cloud multicloud design. These are new skills that are needed. Can you give us the update on what you're doing to help people get into the acceleration of automation game? >>Oh yes, absolutely. The, you know, what we've been seeing is a lot of those business drivers that Susie was mentioning, those are, what's accelerating a lot of the technology changes and that's creating new job roles or new needs on existing job roles where they need new skills. We are seeing customers, partners, people in our community really starting to look at, you know, things like DevSecOps engineer, network, automation, engineer, network, automation, developer, which Susie mentioned and looking at how these fit into their organization, the problems that they solve in their organization. And then how do people build the skills to be able to take on these new job roles or add that job role to their current scope and broaden out and take on new challenges. >>Eric, I want to go to you for a quick second on this, um, um, piece of getting the certifications. Um, first, before you get started, describe what your role is as director developer advocacy, because that's always changing and evolving. What's the state of it now because with COVID people are working at home, they have more time to contact, switch and get some certifications and that they can code more. What's your >>Absolutely. So it's interesting. It definitely is changing a lot. A lot of our historically a lot of focus for my team has been on those outward events. So going to the Devin that creates the Cisco lives and helping the community connect and to help share tech mountain technical information with them, um, doing hands on workshops and really getting people into how do you really start solving these problems? Um, so that's had to pivot quite a bit. Um, obviously Cisco live us. We pivoted very quickly to a virtual event when, when conditions changed and we're able to actually connect as we found out with a much larger audience. So, you know, as opposed to in person where you're bound by the parameters of, you know, how big the convention center is, uh, we were actually able to reach a worldwide audience with our, uh, our definite data that was kind of attached on to Cisco live. >>And we got great feedback from the audience that now we were actually able to get that same enablement out to so many more people that otherwise might not have been able to make it. Um, but to your broader question of, you know, what my team does. So that's one piece of it is getting that information out to the community. So as part of that, there's a lot of other things we do as well. We were always helping out build new sandboxes and your learning labs, things like that, that they can come and get whenever they're looking for it out on a dev net site. And then my team also looks after communities such as the Cisco learning network where this there's a huge community that has historically been there to support people working on their Cisco certifications. We've seen a huge shift now in that group, that all of the people that have been there for years are now looking at the domain certifications and helping other people that are trying to get on board with programmability. They're taking a lot of those same community enablement skills and propping up the community with, you know, helping you answer questions, helping provide content. They've moved now into the dump space as well, and are helping people with that service or what it's great seeing the community come along and really see that. Okay. >>I ask you on the trends around automation, what skills and what developer patterns are you seeing with automation? Are, is there anything in particular, obviously network automation has been around for a long time. Cisco has been leader in that, but as you move up, the stack as modern applications are building, do you see any patterns or trends around what is accelerating automation? What are people learning? >>Yeah, absolutely. So you mentioned a observability was big before COVID and we actually really saw that amplified during COVID. So a lot of people have come to us looking for insights. How can I get that better observability, uh, now that we need it? Well, we're virtual. Um, so that's actually been a huge uptake and we've seen a lot of people that weren't necessarily out looking for things before that are now figuring out how can I do this at scale? I think one good example that, uh, Susie was talking about the VPN example, and we actually had a number SES in the Cisco community that had customers dealing with that very thing where they very quickly had to ramp up. And one in particular actually wrote a bunch of automation to go out and measure all of the different parameters that it departments might care about, about their firewalls, things that you do normally look at me old days, you would size your firewalls based on, you know, assuming a certain number of people working from home. >>And when that number went to a hundred percent things like licenses started coming into play, where they needed to make sure they have the right capacity in their platforms that they weren't necessarily designed for. So one of the STDs actually wrote a bunch of code to go out, use some open source tooling, to monitor and alert on these things and then published it. So the whole community code could go out and get a copy of it, try it out their own environment. And we saw a lot of interest around that in trying to figure out, okay, now I can take that and I can adapt it to what I need to see for my observability. >>That's great. Mandy. I want to get your thoughts on this too, because as automation continues to scale, um, it's going to be a focus and people are at home and you guys had a lot of content online for you recorded every session that didn't the dev Ned zone learnings going on, sometimes linearly. And nonlinearly you got the certifications, which is great. That's key, key, great success there. People are interested, but what are the learnings? Are you seeing? What are people doing? What's the top top trends. >>Yeah. So what we're seeing is like you said, people are at home, they've got time. They want to advance their skillset. And just like any kind of learning people want choice because they want to be able to choose what's matches their time that's available and their learning style. So we're seeing some people who want to dive into full online study groups with mentors, leading them through a study plan. And we have two new, uh, expert led study groups like that. We're also seeing whole teams at different companies who want to do, uh, an immersive learning experience together, uh, with projects and office hours and things like that. And we have a new, um, offer that we've been putting together for people who want those kinds of team experiences called automation boot camp. And then we're also seeing individuals who want to be able to, you know, dive into a topic, do a hands on lab, get some skills, go to the rest of the day of do their work and then come back the next day. >>And so we have really modular self-driven hands on learning through the dev net fundamentals course, which is available through dev net. And then there's also people who are saying, I just want to use the technology. I like to experiment and then go, you know, read the instructions, read the manual, do the deeper learning. And so they're, they're spending a lot of time in our dev net sandbox, trying out different technologies, Cisco technologies with open source technologies, getting hands on and building things. And three areas where we're seeing a lot of interest in specific technologies. One is around SD wan. There's a huge interest in people skilling up there because of all the reasons that we've been talking about security is a focus area where people are dealing with new, new kinds of threats, having to deal with them in new ways and then automating their data center, using infrastructure as code type principles. So those are three areas where we're seeing a lot of interest and you'll be hearing some more about that at dev net create >>Eric and Mandy. If you guys can wrap up this accelerate automation with dev net package and a virtual event here, um, and also tee up dev net create because dev net create has been a very kind of grassroots, organically building momentum over the years. And again, it's super important cause it's now the app world coming together with networking, you know, end to end programmability and with everything as a service that you guys are doing everything with API APIs, I'm only can imagine the enablement that's gonna create. Can you share the summary real quick on accelerating automation with dev net and tee up dev net create Mandy, we'll start with you. >>Yes, I'll go first. And then Eric can close this out. Um, so just like we've been talking about with you at every Devin event over the past years, you know, damnit is bringing APIs across our whole portfolio and up and down the stack and accelerating, uh, automation with dev net. Susie mentioned the people aspect of that the people's skilling up and how that transformed teams, transforms teams. And I think that it's all connected in how businesses are being pushed on their transformation because of current events. That's also a great opportunity for people to advance their careers and take advantage of some of that quickly changing landscape. And so what I think about accelerating automation with dev net, it's about the Duveneck community. It's about people getting those new skills and all the creativity and problem solving that will be unleashed by that community. With those new skills. >>Eric take us home. He accelerating automation, dev net and dev net create a lot of developer action going on in cloud native right now, your thoughts? >>Absolutely. I think it's exciting. I mentioned the transition to virtual for Devin that day, this year for Cisco live. And we're seeing, we're able to leverage it even further with create this year. So, whereas it used to be, you know, confined by the walls that we were within for the event. Now we're actually able to do things like we're adding the start now track for people that want to be there. They want to be a developer, a network automation developer, for instance, we've now got attract just for them where they can get started and start learning. Some of the skills they'll need, even if some of the other technical sessions were a little bit deeper than what they were ready for. Um, so I love that we're able to bring that together with the experienced community that we usually do from across the industry, bringing us all kinds of innovative talks, talking about ways that they're leveraging technology, leveraging the cloud, to do new and interesting things to solve their business challenges. So I'm really excited to bring that whole mix together, as well as getting some of our business units together too, and talk straight from their engineering departments. What are they doing? What are they seeing? What are they thinking about when they're building new APIs into their platforms? What are the, what problems are they hoping >>That customers will be able to solve with them? So I think together seeing all of that and then bringing the community together from all of our usual channels. So like I said, Cisco learning network, we've got a ton of community coming together, sharing their ideas and helping each other grow those skills. I see nothing but acceleration ahead of us for automation. >>Awesome. Thanks so much. >>Can I add one, add one more thing? Yeah. I was just gonna say the other really exciting thing about create this year with the virtual nature of it is that it's happening in three regions. And, um, you know, we're so excited to see the people joining from all the different regions and, uh, content and speakers and the region stepping up to have things personalized to their area, to their community. And so that's a whole new experience for them that create that's going to be fantastic this year. >>Yeah. That's what I was going to close out and just put the final bow on that. By saying that you guys have always been successful with great content focused on the people in the community. I think now during what this virtual dev net virtual dev net create virtual, the cube virtual, I think we're learning new things. People working in teams and groups and sharing content, we're going to learn new things. We're going to try new things and ultimately people will rise up and we'll be resilient. I think when you have this kind of opportunity, it's really fun. And we'll, we'll, we'll ride the wave with you guys. So thank you so much for taking the time to come on the cube and talk about your awesome accelerating automation and dev net. Great. Looking forward to it. Thank you. >>Thank you so much. Happy to be here. >>Okay. I'm Jennifer with the cube virtual here in Palo Alto studios doing the remote content amendment virtual tour face to face. Thank you so much for watching and we'll see you at dev net create thanks for watching. >>Welcome back. And Jeffrey, >>The cube coming to you from our Palo Alto studio with ongoing coverage of the Cisco dev data van, it's called accelerating automation with dev net and the new normal. And we certainly know the new normal is, is not going away. They've been doing this since the middle of March or all the way to October. And so we're excited to have our next guest is Thomas Shively. He's the vice president of product marketing and data center networking for the intent based networking group at Cisco Thomas. Great to see you. >>Hey, good to see you too. Yeah. Yeah. Everybody can see on our background. Exactly, >>Exactly. So, I mean, I'm curious, we've talked to a lot of people. We talked to a lot of leaders, you know, especially like back in March and April with this light switch moment, which was, you know, no time to prep and suddenly everybody has to work from home. Teachers got to teach from home. And so you got the kids home, you got the spouse home, everybody's home trying to get on the network and do their zoom calls in their classes. I'm curious from your perspective, you guys are right there on the, on the network you're right in the infrastructure. What did you hear and see kind of from your customers when suddenly, you know, March 16 hit and everybody had to go home. >>Wow, good point. Hey, I do think we all appreciate the network >>Much more than we used to do before. Uh, and then the only other difference is I'm really more on WebEx calls and zoom calls, but, you know, otherwise, uh, yes. Um, what, what I do see actually is that as I said, network becomes much more operative as a critical piece. And so before we really talked a lot about, uh, agility and flexibility these days, we talk much more about resiliency quite frankly. Uh, and what do I need to have in place with respect to network to get my things from left to right. And you know, it, 2000 East to West, as we say on the data center. Right. Uh, and that just is for most of my customers, a very, very important topic at this point. >>Right. You know, it's, it's amazing to think, you know, had this happened, you know, five years ago, 10 years ago, you know, the ability for so many people in, in, in the information industry to be able to actually make that transition relatively seamlessly, uh, is, is actually pretty amazing. I'm sure there was some, some excitement and some kudos in terms of, you know, it, it is all based on the network and it is kind of this quiet thing in the background that nobody pays attention to. It's like a ref in the football game until they make a bad play. So, you know, it, it is pretty fascinating that you and your colleagues have put this infrastructure and that enabled us to really make that move with, with, with really no prep, no planning and actually have a whole lot of services delivered into our homes that we're used to getting at the office are used to getting at school. >>Yeah. And I mean, to your point, I mean, some of us did some planning, can we clearly talking about some of these, these trends and the way I look at this trans as being distributed data centers and, um, having the ability to move your workloads and access for users to wherever you want to be. And so I think that clearly went on for a while then. So in a sense, we, we, we prep was, or no, but we're prepping for it. Um, but as I said, resiliency just became so much more important than, you know, one of the things I actually do a little block, a little, little, uh, abrupt before a block I put out end of August around resiliency. Uh, you, you, if he didn't, if he didn't put this in place, you better put it in place. Because I think as we all know, we sold our match. This is like maybe two or three months, we're now in October. Um, and I sing, this is the new normal for some time being. Yeah, >>I think so. So let's stick on that theme in terms of, of trends, right? The other great, uh, trend as public cloud, um, and hybrid cloud and multi cloud, there's all types of variants on that theme you had in that blog post about, uh, resiliency in data center, cloud networking, data center cloud, you know, some people think, wait, it's, it's kind of an either, or I either got my data center or I've got my stuff in the cloud and I've got public cloud. And then as I said, hybrid cloud, you're talking really specifically about enabling, um, both inner inner data center resiliency within multi data centers within the same enterprise, as well as connecting to the cloud. That's probably counterintuitive for some people to think that that's something that Cisco is excited about and supporting. So I wonder if you can share, you know, kind of how the market is changing, how you guys are reacting and really putting the things in place to deliver customer choice. >>Yeah, no, it's actually, to me, it's really not a counterintuitive because in the end was what, uh, I'm focusing on. And the company is focused on is what our customers want to do and need to do. Uh, and that's really, um, would, you know, most people call hybrid cloud or multi-cloud, uh, in, in the end, what it is, what it is, is really the ability to have the flexibility to move your workloads where you want them to be. And there are different reasons why you want to place them, right? You might've placed them for security reasons. You might have played some compliance reasons, depending on which customer segment you after, if you're in the United States or in Europe or in Asia, there are a lot of different reasons where you're going to put your sinks. And so I sing in the end, what a, an enterprise looks for is that agility, flexibility, and resiliency. >>And so really what you want to put in place is what we call like the cloud on ramp, right? You need to have an ability to move sings as needed. But the logic context section, which we see in the last couple of months, accelerating is really this whole seam around digital transformation, uh, which goes hand in hand then was, uh, the requirement on the at T side really do. And I T operations transformation, right. How it operates. Uh, and I think that's really exciting to see, and this is where a lot of my discussions I was customers, uh, what does it actually mean with respect to the it organization and what are the operational changes? This a lot of our customers are going through quite frankly, accelerated right. Going through, >>Right. And, and automation is in the title of the event. So automation is, you know, is an increasingly important thing, you know, as the, as we know, and we hear all the time, you know, the flows of data, the complexity of the data, either on the security or the way the network's moving, or as you said, shifting workloads around, based on the dynamic situations, whether that's business security, et cetera, in a software defined networking has been around for a while. How are you seeing kind of this evolution in adding more automation, you know, to more and more processes to free up those, those, um, no kind of limited resources in terms of really skilled people to focus on the things that they should be focused on and not stuff that, that hopefully you can, you know, get a machine to run with some level of. >>Yeah. Yeah. That's a good point. And I said the tech line, I have, you know, sometimes when my mind is really going from a cloud ready, which is in most of our infrastructure is today to cloud native. And so let me a little expand on those, right? There's like the cloud ready is basically what we have put in place over the last five to six years, all the infrastructure that all our customers have, network infrastructure, all the nexus 9,000, they're all cloud ready. Right. And what this really means, do you have API APIs everywhere, right? Whether this is on the box, whether it's on the controller, whether this is on the operations tools, all of these are API enabled and that's just the foundation for automation, right? You have to have that. Now, the next step really is what do you do with that capability? >>Right? And this is the integration with a lot of automation tools, uh, and that's a whole range, right? And this is where the it operation transformation kicks in different customers at different speeds, right? Some just, you know, I use these API APIs and use NoMo tools that they have on a network world just to pull information. Some customers go for further and saying, I want to integrate this with some CMDB tools. Some go even further and saying, this is like the cloud native pleasing, Oh, I want to use, let's say red hat Ansible. I want to use, uh, how she called Terraform and use those things to actually drive how I manage my infrastructure. And so that's really the combination of the automation capability. Plus the integration with relevant cloud native enabling tools that really is happening at this point. We're seeing customers accelerating that, that motion, which really then drives us how they run their it operations. Right? And so that's a pretty exciting, exciting area to see a given. I, we have the infrastructure in place. There's no need for customers to actually do change something. Most of them have already the infrastructures that can do this. It is just no doing the operational change. The process changes to actually get there. >>Right. And it's funny, we, we recently covered, you know, PagerDuty and, and they highlight what you just talked about. The cloud native, which is, you know, all of these applications now are so interdependent on all these different API APIs, you know, pulling data from all of these applications. So a, when they work great, it's terrific. But if there's a problem, you know, there's a whole lot of potential throat to choke out there and find, find those issues. And it's all being connected via the network. So, you know, it's even more critically important, not only for the application, but for all these little tiny components within the application to deliver, you know, ultimately a customer experience within a very small units of time, uh, so that you don't lose that customer. You, you complete that transaction. They, they check out of their shopping cart. You know, all these, these things that are now created with cloud native applications that just couldn't really do before. >>No, you're absolutely right. And that's, this is like, just sit. I'm actually very excited because it opens up a lot of abilities for our customers, how they want to actually structure the operation. Right? One of the nice things around this or automation plus, uh, tool integration, cloning to, and integration is you actually opened this up, not a soul automation train, not just to the network operations personnel, right. You also open it up and can use this for the second ops person or for the dev ops person or for the cloud ops engineering team. Right. Because the way it's structured, the way we built this, um, is literally as an API interface and you can now decide, what is your process do you want to have? And what traditional, you have a request network, operation teams executes the request using these tools and then hand it back over. >>Or do you say, Hey, maybe some of these security things I got to hand over the sec ups team, and they can directly call these these KPIs, right? Or even one step further, you can have the opportunity that the dev ops or the application team actually says, Hey, I got to write a whole infrastructure as code kind of a script or template, and I just execute. Right. And it's really just using what the infrastructure provides. And so that whole range of different user roles and our customer base, what they can do with the automation capability that's available. It's just very, very exciting way because it's literally unleashes a lot of flexibility, how they want to structure and how they want to rebuild the it operations processes. >>That's interesting, you know, cause the, you know, the DevOps culture has taken over a lot, right. Obviously change software programming for the last 20 years. And I think, you know, there's a, there's a lot of just kind of the concept of dev ops versus necessarily, you know, the actual things that you do to execute that technique. And I don't think most people would think of, you know, network ops or, you know, net ops, you know, whatever the equivalent is in the networking world to have, you know, kind of a fast changing dynamic, uh, kind of point of view versus a, you know, stick it in, you know, spec it, stick it in, lock it down. So I wonder if you can, you can share how, you know, kind of that dev ops, um, attitude point of view, workflow, whatever the right verb is, has impacted, you know, things at Cisco and the way you guys think about networking and flexibility within the networking world. >>Yeah, literally, absolutely. And again, it's all customer driven, right? There's none of those. None of those is really actually, you know, a little bit of credit, maybe some of us where we have a vision, but a lot of it is just customer driven feedback. Uh, and yeah, we, we do have network operations teams comes to saying, Hey, we use Ansible heavily on the compute side, we might use this for alpha seven. We want to use the same for networking. And so we made available all these integrations, uh, with sobriety as a state, whether these are the switches, whether these are ACI decent, a controller or our multicell orchestration capabilities, all of these has Ansible integration the way to the right. Uh, the other one, as I mentioned, that how she formed Turco Terraform, we have integrations available and they see the requests for these tools to use that. >>Uh, and so that is emotion where in for all the, you know, and, uh, another block actually does out there, we just posted saying, Neil, all set what you can do and then a Palo to this, right. Just making the integration available. We also have a very, very heavy focus on definite and enablement and training, uh, and you know, a little plugin. I know, uh, probably, uh, part of the segment, the whole definite community that Cisco has is very, very vibrant. Uh, and the beauty of this is right. If you look at us, whether you're a NetApps person or dev ops person or SecOps person, it doesn't really matter. It has a lot of like capability available to just help you get going or go from one level to the next level. Right. And it's simplest thing that like sent books and why moments where you can, we know what's out stress, try sinks out snippets of code Coda there, you can do all of these things. And so we do see it's a kind of a push and pull a tremendous amount of interest and a tremendous, uh, uh, time people spend to learn quite frankly. And that's another site product of, of, you know, the situation we're in and people said, Oh man, and say, okay, online learning, that's the thing. So these, these, these tools are used very, very heavily. Right, >>Right. That's awesome. Cause you know, we've, we've had Susie Lee on a number of times and I know he and Mandy and the team really built this dev net thing. And it really follows along this other theme that we see consistently across other pieces of tech, which is democratization, right. Democratization of the access tool, taking it out of, of just a mahogany row with, again, a really limited number of people that know how to make it work and can make the changes and then opening up to a software defined world where now that the, you know, the, it says application centric, point of view, where the people that are building the apps to go create competitive advantage. Now don't have to wait for, you know, the one network person to help them out out of these environments. Really interesting. And I wonder if, you know, when you look at what's happening with public cloud and how they kind of change the buying parameter, how they kind of changed the degree of difficulty to get projects started, you know, how you guys have kind of integrated that, that type of thought process to make it easier for app developers to get their job done. >>Yeah. I mean, again, it's, it's, uh, I typically look at this more from a, from a customer lands, right? It's the transformation process and it always starts as I want agility. I want flexibility. I want to resiliency, right. This is where we talk to a business owner, what they're looking for. And then that translates into, into an I operations process, right? Your strategy needs to map then how you actually do this. Uh, and that just drives then what tools do you want to have available to actually enable this? Right. And the enablement again is for different roles, right? There is you need to give sync services to the app developer and, uh, the, the platform team and the security team, right. To your point. So the network, uh, can act at the same speed, but you also give to us to the network operations teams because they need to, uh, adjust. >>Then they have the ability to react to, uh, to some of these requirements. Right. And it's not just automation. I say, we, we, we focused on that, but there's also to your point, the, the need, how do I extend between data centers? You know, just, just for backup and recovery and how do I extend into, into public clouds, right? Uh, and in the end, that's a, that's a network connectivity problem. Uh, and we have soft as, uh, we have made as available. We have integrations into, uh, AWS. We have integrations into a joy to actually make this very easy from a, from a network perspective to extend your private, private networks into which of private networks on these public clouds. So from an app development perspective, now it looks like he's on the same network. It's a protective enterprise network. Some of it might sit here. >>Some of it might sit here, but it's really looking the same. And that's really in the enticing, what a business looks at, right. They don't necessarily want to say, I need to have something separate for this deployment. What's a separate for that deployment. What they want is I need to deploy something. I need to do this resilient. And the resilient way in an agile way gives me the tools. And so that's really where we focused, um, and what we're driving, right? It's that combination of automation consistently, and then definite tools, uh, available that we support. Uh, but they're all open. Uh, they're all standard tools as the ones I mentioned, right. That everybody's using. So I'm not getting into this. Oh, this is specific to Cisco, right. It's really democratisation. I actually liked your term. Yeah. >>Yeah. It's, it's a great terminate. And it's, it's really interesting, especially with, with the API APIs and the way everything is so tied together that everyone kind of has to enable this because that's what the customer is demanding. Um, and it is all about the applications and the workloads and where those things are moving, but they don't really want to manage that. They just want to, you know, deliver business benefit to their customers and respond to, uh, you know, competitive threats in the marketplace, et cetera. So it's really an interesting time for the infrastructure, you know, to really support kind of this app first point of view, uh, versus the other way around is kind of what it used to be and, and enable this hyper fast development hyper fast, uh, change in, in, in the competitive landscape or else you will be left behind. Um, so super important stuff. >>Yeah, no, I totally agree. And as I said, I mean, it's, it's kind of interesting is we, we started on the Cisco data center side. We started this probably six or seven years ago. Uh, when we, when we named the application centric, uh, clearly a lot of these concepts evolve, uh, but in a sense it is that reversal of the role from the network provides something and you use to, uh, this is what I want to do. And I need a service, uh, thinking on a networking side to expose. So as that can be consumed. And so that clearly is playing out. Um, and as I said, automation is a key key foundation that we put in place, uh, and our customers, most of our customers at this point, uh, on these, on these products, uh, they have all the capabilities they are, they can literally take advantage. There's really nothing that stops them point. >>Well, it's good times for you because I'm sure you've seen all the memes and in social media, right. What what's driving your digital transformation is that the CEO, the CMO or COVID, and we all know the answer to the question. So I don't think the, the pace of change is going to slow down anytime soon. So keeping the network up and enabling us all to get done, what we have to get done and all the little magic that happens behind the scenes. >>Yeah. No thanks. Thanks for having me. And again, yeah. If you're listening and you're wondering, how do I get started Cisco? Definitely just the place to go. It's fantastic. Fantastic. I highly recommend everybody roll up his sleeves and you know, the best races you can have. >>And we know once the physical events come back, we've been to dev net create a bunch of times, and it's a super vibrant, super excited, but really engaged community sharing. Lots of information is kind of, it's still kind of that early vibe, you know, where everyone is still really enthusiastic and really about learning and sharing information. So, you know, like say Susie and the team are really built a great thing, and we're a, we're happy to continue to cover it. And eventually we'll be back, uh, face to face. I look forward to that as well. All right, thanks. Uh, he's Thomas I'm Jeff, you're watching continuing coverage of Cisco dev net accelerating with automation and programmability >>Kia. Nini is here. He's a distinguished engineer at Cisco TK, my friend. Good to see you again. How are you? Good. I mean, you and I were in Barcelona in January and, you know, we knew we saw this thing coming, but we didn't see it coming this way. Did we know that no one did, but yeah, that was right before everything happened. Well, it's weird. Right? I mean, we were, you know, we, we, it was in the back of our minds in January, we sort of had Barcelona's hasn't really been hit yet. It looked like it was really isolated in China, but, uh, but wow, what a change and I guess, I guess I'd say I'd start with the, we're seeing really a secular change in, in your space and security identity, access management, cloud security, endpoint security. I mean, all of a sudden these things explode as the work from home pivot has occurred, and it feels like these changes are permanent or semi-permanent, what are you seeing out there? >>I don't think anybody thinks the world's going to go back the way it was. Um, to some degree it's, it's changed forever. Um, you know, I, I, I do a lot of my work remotely. Um, and, and so, you know, being a remote worker, isn't such a big deal for me, but for some, it was a huge impact. And like I said, you know, um, remote education, you know, everybody's on the opposite side of a computer. And so the digital infrastructure has just become a lot more important to protect the integrity of it essentially is almost our own integrity these days. Yeah. And when you see that, you know, that work from home pivot, I mean, you know, our estimates are, or along with our partner, DTR about 16% of the workforce was at home working from home prior to COVID and now it's know, North of 70% >>Plus, and that's going to come down maybe a little bit over the next, next six months. We'll see what happens with the fall surge, but, but people essentially accept, expect that to at least double that 16%, you know, going forward indefinitely. So how, what does that, what kind of pressure does that put on the security infrastructure and how, how organizations are approaching security? >>Yeah, I, I just think, uh, from a mindset standpoint, you know, what was optional, uh, maybe, um, last year, uh, is no longer optional and I don't think it's going to go back. Um, I think, I think a lot of people, uh, have changed the way, you know, they live and the way they work. Um, and they're doing it in ways, hopefully that, you know, in some cases, uh, yield more productivity, um, again, um, you know, usually with technology that's severely effective, it doesn't pick sides. So the security slant to it is it frankly works just as well for the bad guys. And so that's, that's the balance we need to keep, which is we need to be extra diligent, uh, on how we go about securing infrastructure, uh, how we go about securing even our, our social channels, because remember all our social channels now are digital. So that's, that's become the new norm. >>You know, you've helped me understand over the years. I remember a line you shared with me in the cube one time is that the adversary is highly capable as sort of the, of the phrase that you used. And, and essentially the way you describe it, as you know, your job as a security practitioner is to decrease the bad guy's return on investment, you know, increase their costs, increase the numerator, but as, as work shifts from home, yeah, I'm in my house, you know, my wifi in my, you know, router with my, you know, dog's name is the password, you know, it's much, much harder for me to, to increase that denominator at home. So can you help? >>Yeah. I mean, it's, it is, it is truly, um, when you think, when you get into the mind of the adversary and, and, uh, you know, the cyber crime out there, they're honestly just like any other business they're trying to operate with high margin. And so if you can get there, if you can get in there and erode their margin, frankly go find something else to do. Um, and, and again, you know, you know, the shift we experienced day to day is it's not just our kids are online in school and, uh, our work is online, but all of the groceries we order, um, you know, this Thanksgiving and holiday season, uh, a lot more online shopping is going to place. So everything's gone digital. And so the question is, you know, how, how do we up our game there so that we can go about our business, uh, effectively. And I make it very expensive for the adversary to operate, uh, and take care of their business. Cause it's nasty stuff. >>I want to ask you about automation generally, and then specifically how it applies to security. So we, I mean, we certainly saw the ascendancy of the hyperscalers and of course they really attacked the it labor problem. We learned a lot from that and an it organizations have applied much of that thinking. And it's critical at scale. I mean, you just can't scale humans at the pace, the technology scales today, how does that apply to security and specifically, how is automation affecting security? >>Yeah, it's, it's, it's the topic these days. Um, you know, businesses, I think, realize that they can't continue to grow at human scale. And so the reason why automation and things like AI and machine learning have a lot of value is because everyone's trying to expand, uh, and operate at machine scale. Now, I mean that for, for businesses, I mean that for, you know, education and everything else now, so are the adversaries, right? So it's expensive for them to operate at Cuban scale and they are going to machine scale, going to machine scale, uh, a necessity is that you're going to have to harness some level of automation, have the machines, uh, work on your behalf, have the machines carry your intent. Um, and when you do that, um, you can do it safely or you could do it dangerously. And that that's really kind of your choice. Um, you know, just because you can automate something doesn't mean you should, um, you, you wanna make sure that frankly, the adversary can't get in there and use that automation on their behalf. So it's, it's a tricky thing because, you know, if, when you take the phrase, you know, uh, how do we, how do we automate security? Well, you actually have to, uh, take care of, of securing the automation first. >>Yeah. We talked about this in Barcelona, where you were explaining that, you know, the, the bad guys, the adversaries are essentially, you know, weaponizing using your own tooling, which makes them appear safe because it's, they're hiding in plain sight. >>Well, there's, they're clever, uh, give them that, um, you know, that there's this phrase that they, they always talk about called living off the land. Um, there's no sense in them coming into your network and bringing their tools and, uh, and being detective, you know, if they can use the tools that's already there, then, uh, they have a higher degree of, of evading, uh, your protection. If they can pose as Alice or Bob, who's already been credentialed and move around your network, then they're moving around the network as Alice or Bob. They're not marked as the adversary. So again, you know, having the detection methods available to find their behavior anomalies and things like that become a paramount, but also, you know, having the automation to contain them, to eradicate them, to, you know, minimize their effectiveness, um, without it, I mean, ideally without human interaction, cause you, you just, can you move faster, you move quicker. Um, and I, I see that with an asterisk because, um, if, if done wrong, frankly, um, you're just making their job more effective. >>I wonder if we could talk about the market a little bit, uh, it's I'm in the security space, cybersecurity 80 plus billion, which by the way, is just a little infant Tessa mill component of our GDP. So we're not spending nearly enough to protect that massive, uh, GDP, but guys, I wonder if you could bring up the chart because when you talk to CSOs and you ask them, what's your, what's your biggest challenge? Let's say lack of talent. And, and so what this chart shows is from ETR, our, our, our survey partner and on the vertical axis is net score. And that's an indication of spending momentum on the horizontal axis is market share, which is a measure of presence, a pervasiveness, if you will, inside the data sets. And so there's a couple of key points here. I wanted to put forth to our audience and then get your reactions. >>So you can see Cisco, I highlighted in red, Cisco is business and security is very, very strong. We see it every quarter. It's a growth area that Chuck Robbins talks about on the, on the conference call. And so you can see on the horizontal axis, you've got, you know, big presence in the data set. I mean, Microsoft is out there, but they're everywhere, but you're right there in that, in that data set. And then you've got for such a large presence, you've got a lot of momentum in the marketplace, so that's very impressive. But the other point here is you've got this huge buffet of options. There's just a zillion vendors here. And that just adds to the complexity. This is of course only a subset of what's in the security space. You know, the people who answered for the survey. So my question is how can Cisco help simplify this picture? Is it automation? Is it, you know, you guys have done some really interesting tuck in acquisitions and you're bringing that integration together. Can you talk about that a little bit? >>Yeah. I mean, that's an impressive chart. I mean, when you look to the left there it's, um, I had a customer tell me once that, you know, I came to this trade show, looking for transportation, and these people are trying to sell me car parts. Um, that's the frustration customers have, you know, and I think what Cisco has done really well is to really focus on the outcomes. Um, what is the customer outcome? Cause ultimately that's, that is what the customer wants. You know, there might be a few steps to get to that outcome, but the closest you can closer, you can get to delivering outcomes for the customer, the better you are. And I think, I think security in general has just year over year have been just written with, um, you need to be an expert. Um, you need to buy all these parts and put it together yourself. And, and I think, I think those days are behind us, but particularly as, as security becomes more pervasive and we're, you know, we're selling to the business, we're not selling to the, you know, t-shirt wearing hacker anymore. >>Yeah. So, well, well, how does cloud fit in here? Because I think there's a lot of misconceptions about cloud people that God put my data in the cloud I'm safe, but you know, of course we know it's a shared responsibility model. So I'm interested in your, your thoughts on that. Is it really, is it a sense of complacency? A lot of the cloud vendors, by the way, say, Oh, the state of security is great in the cloud. Whereas many of us out there saying, wow, it's, it's not so great. Uh, so what are your thoughts on that, that whole narrative and what Cisco's play in, in cloud? >>I think cloud, um, when you look at the services that are delivered via the cloud, you see that exact pattern, which is you see customers paying for the outcome or as close to the outcome as possible. Um, you know, no, no data center required, no disk drive required, you just get storage, you know, it's, it's, it's all of those things that are again, closer to the outcome. I think the thing that interests me about cloud two is it's really been, it's really punctuated the way we go about building systems. Um, again, at machine scale. So, you know, before, when I write code and I think about what computers are gonna run on, or, you know, what servers are going to is you're going to run on those. Those thoughts never crossed my mind anymore. You know, I'm modeling the intent of what the service should do and the machines then figure it out. So, you know, for instance, on Tuesday, if the entire internet shows up, uh, the, the system works without fail. And if on Wednesday, if only North America shows up, you know, so what, but, but there's no way you could staff that, right? There's just no human scale approach that gets you there. And that's, that's the beauty of all of this cloud stuff is, um, it really is, uh, the next level of how we computer science. >>So you're talking about infrastructure as code and that applies to, you know, security as code. That's what, you know, dev net is really all about. I've said many times, I think Cisco of the, the large established enterprise companies is one of the few, if not the only, that really has figured out, you know, that developer angle, because it's practical do, you're not trying to force your way into developers, but, you know, I wonder if you could, you could talk a little bit about that trend and where you see it going. >>Yeah, no, that is, that is truly the trend. Every time I walk into dev net, um, the big halls at Cisco live, it is Cisco as code. Um, everything about Cisco is being presented through an API. It is automation ready. And, and frankly, that is, um, that is the love language of the cloud. Um, it's it's machines, if the machines talking to machines in very effective ways. So, you know, it is the, the, uh, I, I think, I think necessary, maybe not sufficient but necessary for, um, you know, doing all the machine scale stuff. What what's also necessary, uh, is to, um, to secure if, if infrastructure is code therefore, um, what, what secure, uh, what security methodologies do we have today that we use to secure code while we have automated testing, we have threat modeling, right? Those things actually have to be now applied to infrastructure. So when I, when I talk about how do you do, uh, automation securely, you do it the same way you secure your code, you test it, you, you threaten model, you, you, you say, you know, Ken, my adversary, uh, exhibit something here that drives the automation in a way that I didn't intend it to go. Um, so all of those practices apply. It's just, everything is code these days. >>I've often said that security and privacy are sort of two sides of the same coin. And I want to ask you a question and it's really, to me, it's not necessarily Cisco and company likes companies like Cisco's responsibility, but I wonder if there's a way in which you can help. And of course, there's this Netflix documentary circling around the social dilemma. I don't know if you have a chance to see it, but basically dramatize is the way in which companies are appropriating our data to sell us ads and, you know, creating our own little set of facts, et cetera. And that comes down to sort of how we think about privacy and admin. It's good from the standpoint of awareness, you know, you may or may not care if you're a social media user. I love tick doc. I don't care, but they sort of laid out this pretty scary scenario with a lot of the inventors of those technologies. You have any thoughts on that? And you'll consist go play a role there in terms of protecting our privacy mean beyond GDPR and California consumer privacy act. Um, what do you think? >>Yeah. Um, uh, I'll give you my, you know, my humble opinion is you, you fix social problems with social tools, you fixed technology problems with technology tools. Um, I think there is a social problem. Um, uh, that needs to be rectified the, you know, um, we, we, weren't built as human beings to live and interact with an environment that agrees with us all the time. It's just pretty wrong. So yeah, that, that, that, um, that series that really kind of wake up a lot of people it is, is, you know, it's probably every day I hear somebody asked me if I, I saw, um, but I do think it also, you know, with that level of awareness, I think we, we overcome it or we compensate by what number one, just being aware that it's happening. Um, number two, you know, how you go about solving it, I think maybe come down to an individual or even a community's, um, solution and what might be right for one community might be, you know, not the same for the other. So you have to be respectful in that manner. >>Yeah. So it's, it's, it's almost, I think if I could, you know, play back, what I heard is, is yeah. Technology, you know, maybe got us into this problem, but technology alone is not going to get us out of the problem. It's not like some magic AI bot is going to solve this. It's got to be, you know, society has to really, really take this on as your premise. >>When I, when I first started playing online games, I'm going back to, you know, the text based adventure stuff like muds and Mose. I did a talk at, at MIT one time and, um, this old curmudgeon in the back of the room, um, we were talking about democracy and we were talking about, you know, the social processes that we had modeled in our game and this and that. And this guy just gave us the SmackDown. He needs to be walked up to the front of the room and said, you know, all you techies, you judge efficiency by how long it takes. He says, democracy is a completely the opposite, which is you need to sleep on it. In fact, you shouldn't be scared if somebody can decide in a minute, what is good for the community? It, two weeks later, they probably have a better idea of what's good for the community. So it almost has the opposite dynamic. And that was super interesting to me, >>Really interesting, you know, you read the, like the, the Lincoln historians and he was criticized in the day for having taken so long, you know, to make certain decisions, but, you know, ultimately when he acted acted with, with confidence. Um, so to that point, but, um, so what, what else are you working on these days that, uh, that are, that is, is interesting that maybe you want to share with our audience? Anything that's really super exciting for you or are you >>Yeah. You know, generally speaking, um, try not try and make it a little harder for the bad guys to operate. I guess that's a general theme making it simpler for the common person to use, uh, tools. Um, again, you know, all of these security tools, no matter how fancy it is, it's not that we're losing the complexity, it's that we're moving the complexity away from the user so that they can drive at human scale. And we can do things at machine scale and kind of working those two together is sort of the, the, the magic recipe. Um, it's, it's not easy, but, um, but it is, it is fun. So that's, that's what keeps me engaged. >>I'm definitely seeing, I wonder if you see it as just sort of a, obviously a heightened organization awareness, but I'm also seeing shifts in the organizational structures. You know, the, you know, it used to be a sec ops team and an Island. Okay, it's your problem? You know, the, the, the CSO cannot report into the, to the CIO because that's like the Fox in the hen house, a lot of those structures are, are, are changing. It seems, and be becoming a, this responsibility is coming much more ubiquitous across the organization. What are you seeing there? And what are you? >>And it's so familiar to me because, you know, um, I, I started out as a musician. So, you know, bands bands are a great analogy. You know, you play bass, I big guitar. You know, somebody else plays drums, everybody knows their role and you create something that's larger than the sum of all parts. And so that, that analogy I think, is coming to, you know, we, we saw it sort of with dev ops where, you know, the developer, doesn't just throw their coat over the wall and it's somebody else's problem. They move together as a band. And, and that's what I think, um, organizations are seeing is that, you know, why, why stop there? Why not include marketing? Why not include sales? Why don't we move together as a business? Not just here's the product and here's the rest of the business. That's, that's, that's pretty awesome. Um, I think, uh, we see a lot of those patterns, uh, particularly for the highly high performance businesses. >>You know, in fact, it's interesting, you have great analogy by the way. And you actually see in that within Cisco, you're seeing sort of a, and I know sometimes you guys don't like to talk about the plumbing, but I think it matters. I mean, you've got a leadership structure now. I I've talked to many of them. They seem to really be more focused on how their connect connecting, you know, across organizations. And it's increasingly critical in this world of, you know, of silo busters. Isn't it? >>Yeah, no, I mean, you almost, as, as you move further and further away, you know, you can see how ridiculous it was before it would be like acquiring the band and say, okay, all your guitar players go over here. All your bass players go over there. Like what happened to the band? That's what I'm talking about is, you know, moving all of those disciplines, moving together and servicing the same backlog and achieving the same successes together is just so awesome. Well, I, I always feel better after talking to you. You know, I remember I remember art. Coviello used to put out his letter every year and I was reading. I'd get depressed. We spend all this money now we're less secure. But when I talked to you TK, I feel like much more optimistic. So I really appreciate the time you spend on the cube. It's, it's awesome to have you as a guest. I love these, I love these sessions. So things thanks for inviting me and I miss you, you know, hopefully, you know, next year we can get together at some of the Cisco shows or other shows, but be well and stay weird. Like the sign says kidney, thanks so much for coming to the Q. We, uh, we really appreciate it. And thank you for watching everybody. This is Dave Volante. We've right back with our next guest. This short break, >>After the cubes coverage, just to keep virtuals coverage of dev net create virtual. We're not face to face the cubes been there with dev net and dev net create. Since the beginning, dev net create was really a part of the dev net community. Looking out at the external market outside of Cisco, which essentially is the cloud native world, which is going mainstream. We've got a great guest here. Who's, who's been the company's been on the cube. Many times. We've been talking to them recently acquired by Cisco thousand eyes. We have Joe Vaccaro is beast vice president of product. Uh, Joe, welcome to the cube. Thanks for coming on. Great. And thanks for having me. You have the keys to the kingdom, you, the vice president of product, which means you get to look inside and you get to look outside, figure it all out, uh, make everything run on thousand eyes. >>You guys have been finding common language, uh, across multiple layers of network intelligence, external services. This is the heart of what we're seeing in innovation with multi-cloud microservices, cloud native. This is really a hot area it's converged in multiple theaters and technology. Super important. I want to get into that with you, but first thousand eyes is recently acquired by Cisco, um, big acquisition, uh, super important, the new CEO of Cisco, very clear API, everything we're seeing that come out. That's a big theme at dev net create the ecosystem of Cisco's going outside their own, you know, their, their walls outside of the Cisco network operators, network engineers. We're talking to developers talking programmability. This is the big theme. What's it like at Cisco? Tell us, honestly, the COVID hits. You get acquired by Cisco, tell us what's happening. >>Yeah, it's really been an exciting six months for the entire team and customers, >>You know, as we all kind of shifted to the new normal of working from home. And I think, you know, that change alone really kind of amplified. Even some of the fundamental beliefs that we have as a company that you know, cloud is becoming the new data center or customers that Indra internet has become the new network and the new enterprise network backbone. And that SAS has really become the new application stack. And as you think about these last six months, those fundamental truths have never been more evident as we rely upon the cloud to be able to, to work as we rely upon our own home networks and the internet in order to be productive. And as we access more sized applications on a daily basis. And as you think about those fundamental truths, what's common across all of them is that you rely upon them now more than ever, not only to run your business, but to any of your employees would be productive, but you don't own them. And if you don't own them, then you lack the ability in a traditional way to be able to understand that digital experience. And I think that's ultimately what, what thousand eyes is trying to solve for. And I think it's really being amplified in really these last six months. >>Talk about the Cova dynamic because I think it highlighted and certainly accelerated digital transformation, but specifically exposes opportunities, challenges, weaknesses, I've talked to many CXOs CSOs. Uh, sec security is huge. Um, the home of the conference book talk track we'll get to in a second, but it exposes what's worth doubling down on what to abandoned from a project standpoint, as people start to look at their priorities, they're going, Hey, we got to have a connected experience. We got to have security. People are working at home. No one has VPNs at home. VPNs are passe. Maybe it's SD when maybe it's something else they're on a backbone. They're connecting to the internet, a lot of different diversity in connections. At the same time, you got a ton of modern apps running for these networks. This is a huge issue. COVID is exposed this at scale. What's your view on this? And what is thousand eyes thinking about this? >>You know, if you think about the kind of legacy application delivery, it went from largely users in an office connected over, say a dedicated corporate network, largely to traditional say internal hosted applications. And that was a early, simple, uh, connectivity bath. And as you mentioned, we've seen amplifications in terms of the diversity from the users. So users are not in the office. Now they're connected in distributed disparate locations that are dynamically changing. And you think that how they're getting to that application, they're going across a really complex service chain of different network services that are working together across as public internet backbone will totally to land them on an application. And then those applications themselves are becoming now, as you mentioned, distributed largely based upon a microservices architecture and increasing their own dependence upon third party sample size applications to fulfill say, functions of that application, those three things together. >>Ultimately you're creating that level level of complex service chain that really makes it difficult to understand the digital experience and ultimately the it organization newly chartered with not just delivering the infrastructure, but delivering the right experience. And you then have a way to be able to see, to gain that visibility, that experience, you know, to measure it and understand, and to provide that intelligence and then ultimately to act on it, to be able to ensure that your employees, as well as your customers are getting the right overall, um, approach to being able to leverage those assets. >>It's funny, you know, as you get into some of these high-scale environments, a lot of these concepts are converging. You know, we had terms like automation, self healing networks. Um, you mentioned microservices early, you mentioned data at the clouds, the new data center, uh, or when's the new land. However, we're going to look at it. It's a whole different architecture. So I want to get your thoughts on, on the automation piece of networking and internet outages, for instance, um, because when you, you know, there's so many outages going up and down, it is like, uh, catching, looking for a needle in a haystack, right. So, um, we've had this conversation with you guys on the cube before, how does automation occur when you guys look at those kinds of things? Uh, what's important to look at, can you comment on and react to, you know, the internet outages and how you find resolve those? >>Yeah. It's um, it was really great. And as you mentioned, automation really in a place that a key, when you think about the, just a broad problem that it is trying to drive and, you know, from our lens, we look at it in really three ways. First off is you have to be able to gain the level of visibility from where it matters and be able to, to test and be able to provide that level of active measurements across the, the type of ways you want to be able to inspect the network. But then also from the right vantage points, you want to inspect it. But what we talk about right inside, you know, data, um, alone, doesn't solve that problem. As you mentioned, that needle in the haystack, you know, data just provides the raw metrics that are screaming across the screen. You have to then enable that data to provide meeting. >>You need to enable that data become intelligent. And that intelligence comes through the automation of being able to process that data very quickly, allow you to be able to see the unseen, to allow you to be able to quickly understand the issues that are happening across this digital supply chain to identify issues that are even happening outside of your own control across the public internet. And then the last step of automation really comes in the form of the action, right? How do you enable that intelligence to be put, to use? How do you enable that intelligence to then drive across the rest of your it workflow as well as to be able to be used as a signaling engine, to be able to then make the fundamental changes back at the network fabric, whether that is a dressing or modifying your BGB pairing, that we see happen within our customers using thousand eyes data, to be able to route around major internet outages that we've seen over the past six months, or to be able to then that data, to be able to optimize the ultimate experience that they're delivering to both our customers, as well as our employees, >>Classic policy based activity, taking it to a whole nother level. I got to get your thoughts on the employees working at home. Okay. Because, um, you know, most it, people are like, Oh yeah, we're going to forecast in cases of disruption or a hurricane or a flood or hurricane Sandy, but now with COVID, everyone's working at home. So who would have forecasted a hundred percent, um, you know, work from home, which puts a lot of pressure on him, everything. So I got to ask you, now that employees are working at home, how do you tie network visibility to the actual user experience? >>Yeah, that's a great question. As you, you know, we saw it within our own customer base, you know, when COVID head and we saw this rise of work from home, it teams were really scrambling and said, okay, I have to light up this, say VPN infrastructure, or I need to now be able to support my users in a work from home situation where I don't control the corporate network. In essence, now you have essentially thousands. Every employee is acting across their own corporate network and people were then using thousand eyes in different ways to be able to monitor their CTPs infrastructure across, back into the corporate network, as well as in using our thousand eyes end point agents that runs on a local, a user's laptop or machine in their home to help you to be able to gain that visibility down to that last mile of connectivity. >>Because when a user calls up support and says, I'm having trouble say accessing my application, whether that's Salesforce or something else, what ultimately might be causing that issue might not necessarily be a Salesforce issue, right? It could be the device in the device performance in terms of CPU, memory utilization. It could be the wifi and the signal quality within your wifi network. It could be your access point. It could be your raw, local home router. It can be your local ISP. It could be the path that you're taking ultimately to your corporate network or that application. There's so many places that could go wrong that are now difficult to be able to see, unless you have the ability to see comprehensively from the user to the application, and to be able to understand that full end to end path, >>You know, it teams have also been disrupted. They've been on offsite prop off property as well, but you've got the cloud. How has your technology helped the it teams? Can you give some examples there? Um, >>Yeah, a great way is, you know, how people use thousand eyes as part of that data sharing ecosystem. Again, that notion of how do you go from visibility to intelligence action and where in the past you might be able as an it administrator to walk over to their network team and say, Hey, can you take a look at what I'm seeing now? That's no longer available. So how do you be able to work efficiently as the United organization? You know, we think a thousand eyes in how our customers are using us a thousand times becomes a common operating language that allows them to be able to analyze across from the application down into the underlying infrastructure, through those different layers of the network what's happening. And where do you need to focus your attention? And then furthermore, with 10,000 eyes in terms of a need, enabling that data sharing ecosystem, leveraging our share link capability really gives them the ability to say, you know, what, here's what I'm seeing and be able to send that to anybody within the it organization. But it goes even further and many times in recent times, as well as over the course of people using thousand eyes, they take those share links and actually send them to their external providers because they're not just looking to resolve issues within their own it organization. They're having to work collaboratively with a different ISP. If they're pairing with, with their cloud providers that they're appearing, uh, they're leveraging, or the SAS applications that are part of that core dependency of how they deliver their experience. >>I asked you the question, we think about levels of visibility and making the lives easier for it. Teams. Um, you see a lot of benefits with thousand eyes. You pointed out a few of them just got to ask you the question. So if I'm an it person I'm in the trenches, are you guys have, uh, an aspirin or a vitamin or both? Can you give an example because there's a lot of pain point out there. So yeah. Give me a cup, a couple Advils and aspirins, but also you're an enabler to the new things are evolving. You pointed out some use case. You talk about the difference between where you're helping people pain points and also enabling them be successful for it teams. >>Yeah, that's a great analogy. You're thinking it, like you said, it definitely sits on both sides of that spectrum, you know, thousand eyes is the trusted tool, the source of truth for it. Organizations when issues are happening as their alarm bells are ringing, as they are generating the, um, the different, uh, on call, uh, to be able to jump into a war situation thousand eyes is that trusted source of truth. Allow them to focus, to be able to resolve that issue in the heat of the moment. But that was a nice also when we think about baselining, your experience, what's important is not understanding that experience at that moment at time, but also how that's deviated over time. And so by leveraging thousand eyes on a continuous basis, it gives you that ability to see the history of that experience, to understand how your network is changing is as you mentioned, networks are constantly evolving, right? >>The internet itself is constantly changing. It's an organic system, and you need to be able to understand not only what are the metrics that are moving out of your bounds, but then what is potentially the cause of that as a network has evolved. And then furthermore, you can be begin to use that as you mentioned, in terms of your vitamin type of an analogy, to be able to understand the health of your system over time on a baseline basis so that you can begin to, uh, be able to ensure its success in a great way to really kind of bring that to light. As people using say, thousand eyes as part of the same se land-based rollout, where you're looking to say benchmark, and you can confidence as you look to scale out in either, you know, benchmarking different ESPs within that, I feel like connectivity for as you look to ensure a level of success with a single branch, give you that competence to then scale out to the rest of your organization. >>That's great insights. The classic financial model ROI got baseline and upside, right? You got handle the baseline as you pointed out, and the upside music experience connectivity, you know, application performance, which drives revenue, et cetera. So great point. Great insight, Joe. Thank you so much for that insight. It's got a final question for you. I want to just riff a little bit with you on the industry. A lot of us have been having debates about automation and who doesn't, who doesn't love automation. Automation is awesome, right? Automate things, but as the trend starts going on, as everything is a service or X, a S as it's called, certainly Cisco's going down that road. Talk about your view about the difference between automation and everything is a service because at the end of the day, everything will be a service, but without automation, you really can't have services, right? So, you know, automation, automation, automation, great, great drum to bang all day long, but then also you got the same business side saying as a service, as a service, pushing that into the products, it means not trivial. Talk about, talk about how you look at automation and everything as a service and the relationship and interplay between those two concepts. >>Yeah. Ultimately I think about in terms of what is the problem that the business is trying to solve in ultimately, what is the deal that they're trying to face? And in many ways, right, they're being exploded with increase of data that needs, they need to be able to not only process and gather, but then be able to then make use of, and then from that, as we mentioned, once you've processed that data and you've said, gather the insights from it. You need to be able to then act on that data. And automation plays a key role of allowing you to be able to then put that through your workflow. Because again, as that, it experience becomes even more complex as more and more services get put into that digital supply chain. As you adopt say increased complexity within your infrastructure, by moving to a multicloud architecture where you look to increase the number of say, network services that you're leveraging across that digital experience. >>Ultimately you need with the level of automation, you'll be able to see outside of your own vantage point. You need to be able to look at the problem from as broad of a, a broad of a way as possible. And, you know, data and automation allows you to be able to do what is fundamentally difficult to do from a very narrow point of view, in terms of the visibility you gather intelligence you generate, and then ultimately, how do you act on that data as quick as possible to be able to provide the value of what you're looking for. >>It's like a feature it's under the hood. The feature of everything comes to the surface is automation, data, machine learning, all the goodness in the software. I mean, that's really kind of what we're talking about here. Isn't it a final question for you as we wrap up, uh, dev net create really, again, is going beyond Cisco's dev net community going into the industry ecosystem where developers are there. Um, these are folks that want infrastructure as code. They want network as code. So network programmability, huge topic. We've been having that conversation, uh, with Cisco and others throughout the industry for the past three years. What's your message to developers out there that are watching this who say, Hey, I just want to develop code. Like I want, you know, you guys got that. That was nice. Thanks so much. You know, you take care of that. I just want to write code. What's your message to those folks out there who want to tap some of these new services, these new automation, these new capabilities, what's your message. >>And ultimately, I think, you know, when you're looking at thousand eyes, um, you know, from a fraud perspective, you know, we try to build our product in an API first model to allow you to be able to then shift left of how you think about that overall experience. And from a developer standpoint, you know, what I'd say is, is that while you're developing in your silo, you're going to be part of a larger ultimate system. In your experience you deliver within your application is now going to be dependent upon not only the infrastructure that's running upon, but the network it's connected to, and then ultimately the user in the sense of that user and by leveraging that thousand eyes and being able to then integrate thousand into how you think closely on that experience, that's going to help ensure that ultimately the application experience that the developer's looking to deliver meets that objective. And I think what I would say is, you know, while you need to focus on your, uh, your role as a developer, having the understanding of how you fit into the larger ecosystem and what the reality of the, of how your users access that application is critical. >>Awesome, Joe, thank you so much. Again, trust is everything letting people understand that what's going on underneath is going to be viable and capable. You guys got a great product and congratulations on the acquisition that Cisco made of your company. We've been following you guys for a long time and a great technology chops, great market traction, congratulations to everyone, 1,009. Thanks for coming on sharing. I appreciate it. Thanks Joe Vaccaro, vice president of product here, but thousand nine is now part of Cisco, John, for your host of the cube cube virtual for dev net, create virtual. Thanks for watching. >>Even prior to the pandemic, there was a mandate to automate the hyperscale cloud companies. They've shown us that to scale. You really have to automate you human labor. It just can't keep up with the pace of technology. Now, post COVID that automation mandate is even more pressing. Now what about the marketplace? What are S E seeing on the horizon? The cubes Jeff Frick speaks with Cisco engineers to gather their insights and explore the definite specialized partner program. We've got a Coon Jacobs. He's the director of systems engineering for Cisco. >>Good to see Kuhn. >>Thank you for having me >>Joining him as Eric nip. He is the VP of system systems engineering for Cisco. Good to see Eric. Good to be here. Thank you. Pleasure. So before we jump into kind of what's going on now in this new great world of programmability and, and control, I want to kind of go back to the future for a minute because when I was doing some research for this interview, it was cool. I saw an old presentation that you were giving from 2006 about the changing evolution of the, uh, the changing evolution of networking and moving from. I think that the theme was a human centered human centered network. And you were just starting to touch a little bit on video and online video. Oh my goodness, how far we have come, but I would love to get kind of a historical perspective because we've been talking a lot and I know Eric son plays football about the football analogy of the network is kind of like an offensive lineman where if they're doing a good job, you don't hear much about them, but they're really important to everything. >>And the only time you hear about them as the women, the flag gets thrown. So if you look back with the historical perspective, the load and the numbers and the evolution of the network, as we've moved to this modern time, and, you know, thank goodness cause of COVID hit five years ago, 10 years ago, 15 years ago, you know, all of us in the information space would not have been able to make this transition. So I just, I just love to get some historical perspective cause you've been kind of charting this and mapping this for a very long time. >>Yeah. W we absolutely have. I think, you know, what you're referring to was back in the day, the human network campaign, and to your point, the load, the number of hosts that traffic that just overall, the intelligence of the network has just evolved tremendously over these last decade and a half, uh, 15 years or so. And you look at where we are now in terms of the programmable nature of the network and what that enables in terms of new degrees of relevance that we can create for the customers and how, you know, the role of it has changed entirely again, especially during this pandemic, you know, the fact that it's now as a serve as an elastic is absolutely fundamental to being able to ensure, uh, on an ongoing basis, a great customer experience. And so, uh, it's been, it's been, uh, a very interesting ride. >>And then just to close the loop, the, one of your more later interviews talking to Sylvia, your question is, are you a developer or an engineer? So it was, and, and your whole advice to all these network engineers is just, just don't jump in and start doing some coding and learning. So, you know, the focus and really the emphasis and where the opportunity to differentiate as a company is completely shifting gears over to the, you know, really software defined side. >>Oh, absolutely. So I mean, you look at how the software world and the network has come together and how we're applying now, you know, basically the same construct of CIC pipeline to network, uh, infrastructure, look at network really as, and get all of the benefits from that. And the familiarity of it, the way that our engineers have had to evolve. And that is just, you know, quite, quite significant in, in, in like the skill set. And the best thing is jump in, right. You know, dip your toe in the water, but continue to evolve that skill set. And, you know, don't, don't be shy. It's a leap of faith for some of us who've been in the industry a bit longer. We like to look at ourselves as the craftsman of the network, but now it's definitely a software centricity and programmability, right? >>So Eric, you've got some digital exhaust out there too, that I was able to dig up going back to 2002 752 page book and the very back corner of a dark dirty dusty Amazon warehouse is managing Cisco network security, 752 pages. Wow. How has security change from a time where before I could just read a book, a big book, you know, throw some protocols in and probably block a bunch of ports to the world that we live in today, where everything is connected. Everything is API driven, everything is software defined. You've got pieces of workloads spread out all over the place and Oh, by the way, you need to bake security in at every single level of the application stack. >>Yeah, no, I'm so, wow. The kudos that you, you found that book I'm really impressed. There was a thank you a little street, correct. So I want to hit on something that you, you talked about. Cause I think it's very important to, to this overall conversation. If we think about the scale of the network and Coon hit on it briefly, you talked about it as well. We're seeing a massive explosion of devices by the estimated by the end of this year, there's going to be about 27 billion devices on the global internet. That's about 3.7 devices for every man, woman and child life. And if we extrapolate that out over the course of the next decade on the growth trajectory we're on. And if you look at some of the published research on this, it's estimated there could be upwards of 500 billion devices accessing the global internet on a, on a daily basis in the primarily that, that, that is a IOT devices, that's digitally connected devices. >>Anything that can be connected will be connected, but then introduces a really interesting security challenge because every one of those devices that is accessing the global internet is within a company's infrastructure or accessing pieces of corporate data is a potential attack factor. So we really need to, and I think the right expression for this is we need to reimagine security because security is, as you said, not about parameters. You know, I wrote that book back in 2002, I was talking about firewalls and a cutting edge technology was intrusion prevention and intrusion detection. Now we need to look at security really in the, in the guys up or under the, under the, under the realm of really two aspects, the identity who is accessing the data and the context, what data is being accessed. And that is going to require a level of intelligence, a level of automation and the technologies like machine learning and automated intelligence are going to be our artificial intelligence rather are going to be table stakes because of the sheer scale of what we're trying to secure is going to be untenable under current, you know, just current security practices. I mean, the network is going to have to be incredibly intelligent and leverage again, a lot of that, uh, that AI type of data to match patterns of potential attacks and ideally shut them down before they ever cause any type of damage. >>Yeah, it's really interesting. I mean, one thing that COVID has done a bunk many things is kind of retaught us all about the power of exponential curves and how extremely large those things are and how fast they grow. We at Dave runs it on a Google cloud a couple of years ago. And I remember him talking about early days at Google when they were starting to map out kind of, as you described kind of map out their growth curves, and they just figured out they could not hire if they hired everybody, they couldn't hire enough people to deal with it. Right. So really kind of rethinking automation and rethinking about the way that you manage these things and the level, right. The old, is it a pet or is it, or is it, um, uh, part of a herd and, and I think it's interesting what you talked about, uh, con really the human powered internet and being driven by a lot of this video, but to what you just said, Eric, the next big wave, right. >>Is IOT and five G. And I think, you know, you talk about 3.7 million devices per person. That's nothing compared to right. All these sensors and all these devices and all these factories, because five G is really targeted to machine the machines, which there's a lot of them and they trade a lot of information really, really quickly. So, you know, I want to go back to you Coon thinking about this next great wave in a five G IOT kind of driven world where it's kind of like when voice kind of fell off compared to IP traffic on the network. I think you're going to see the same thing, kind of human generated data relative to machine generated data is also going to fall off dramatically as a machine generated data just skyrocket through the roof. >>Yeah, no, absolutely. And I think too, also what Eric touched on the visibility on that, and they've been able to process that data at the edge. That's going to catalyze cloud adoption even further, and it's going to, you know, make the role of the network, the connectivity of it all and the security within that crucially important. And then you look at the role of programmability within that. We're seeing the evolution going so fast. You look at the element of the software defined network in an IOT speed space. We see that we have a host Sarah that are not necessarily, um, you know, behaving like other hosts would, uh, on a network, for example, manufacturing floor, uh, production robot, or a security camera. And what we're seeing is we're seeing, you know, partners and customers employing programmability to make sure that we overcome some of the shortcomings, uh, in terms of where the network is at, but then how do you customize it in terms of the relevance that can provide, >>Um, bringing on board those, uh, those hosts in a very transparent way, and then, you know, keep, keep the agility of it and keep the speed of innovation going. >>So, Eric, I want to come back to you and shift gears kind of back to the people will leave the IOT in the machines along, along for a minute, but I'm curious about what does beat the boss. I mean, I go to your LinkedIn profile and it's just filled with congratulatory statements, but everyone's talking about beating the boss. You know, it's, it's a really, you know, kind of interesting and different way to, to motivate people, to build this new skillset in terms of getting software certifications, uh, within the Cisco world. And I just thought it was really cute the way that you, uh, clearly got people motivated, cause there's posts all over the place and they've all got their, their nice big badge or their certification, but, you know, at a higher level, it is a different motivation to be a developer versus an you're an a technician. And it's kind of a different point of view. And I just wonder if you could share, you know, some of the ways that you're, you're kind of encouraging, you know, kind of this transformation within your own workforce, as well as the partners, et cetera, and really adopting kind of almost a software first and this program kind of point of view versus, you know, I'm just wiring stuff up. >>Apparently a lot of people like to beat me. So I mean, not itself was a, was a, a, it was a great success, but you know, if we think we take a step back, you know, what is Cisco about as an organization? Um, I mean, obviously he looked back to the very early days of our vision, right? It was, it was to change the way the world worked, played, live and learn. And that you think about, and you hit on this when we were, you know, we were discussion with co with Kuhn in the early days of COVID. We really saw that play out as so much shifted from, you know, in-person type of interactions to virtual interactions in the network that, uh, that our, our customers, our partners, our employees built over the course of the last several years, the last three decades really helped the world continue to, um, to, to do business for students to continue to go to school or clinicians, to connect with patients. >>If I think about that mission to me, programmability is just the next iteration of that mission, continuing to enable the world to communicate, continuing, to enable customers, employees, uh, partners, uh, to essentially leverage the network for more than just connectivity now to leverage it for critical insight. Again, if we look at some of the, uh, some of the use cases that we're seeing for social distancing and contact tracing and network has a really important place to play there because we can pull insight from it, but it isn't necessarily an out of the box type of integration. So I look at programmability and in what we're doing with, with dev net to give relevance to the network for those types of really critical conversations that every organization is having right now, it's a way to extrapolate. It's a way to pull critical data so that I can make a decision. >>And if that is automated, or if that decision requires some type of manual intervention, regardless, we're still about connecting. And in this case, we're connecting insight with the people who need it most, right. The debit challenge we ran is really in respect for how critical this new skill set is going to be. It's not enough, like I said, just to connect the world anymore. We need to leverage that network, the network for that critical insight. And when we drove, we were, we created the beat, the boss challenge. It was really simple. Hey guys, I think this is important and I am going to go out and I'm going to achieve the certification myself, because I don't want to continue to be very relevant. I want to continue to be able to provide that insight for my customers and partners. So therefore I'm going for anybody that can get there before me. Maybe there's a little incentive tied to it and the incentive, although it's funny, we interviewed a lot of, a lot of our team who, who achieved it when incentive was secondary, they just wanted to have the bragging rights, like yeah, I beat Eric. Right? >>Right. Absolutely. No, it's a, it's it, you know, putting your money where your mouth is, right. If it's important, then why you should do it too. And, and you know, the whole, you're not asking people to do what you wouldn't do yourself. So I think there's a lot of good leadership, uh, leadership lessons there as well, but I want to extend kind of the conversation on the covert impact, right? Cause I'm sure you've seen all the social media means, you know, who's driving your digital transformation, the CEO, the CMO or COVID. And we all know the answer to the question, but you know, you guys have already been dealing with kind of an increased complexity around enterprise infrastructure world in terms of cloud and public cloud and hybrid cloud and multi cloud. And people are trying to move stuff all the way around now suddenly had this COVID moment right in, in March, which is really a light switch moment. >>People didn't have time to plan or prepare for suddenly everybody working from home. And it's not only you, but your spouse and your kids and everybody else. So I, but now we're six months plus into this thing. And I would just love to get your perspective and kind of the change from, Oh my goodness, we have to react to the light switch moment. What do we do to make sure people can, can get, get what they need when they need it from where they are a bubble, but then really moving from this is a, an emergency situation, a stop gap situation to, Hmm, this is going to extend for some period of time. And even when it's the acute crisis is over, you know, this is going to drive a real change in the way that people communicate in the way that people, where they sit and do their jobs and, and kind of how customers are responding accordingly as the, you know, kind of the narrative has changed from an emergency stop gap to this is the new normal that we really need to plan for. >>So, uh, I think, I think you said it very well. I think anything that could be digitized, any, any interaction that could be driven virtually was, and what's interesting is we, as you said, we went from that light switch moment where I, and I believe the status, this, and I'll probably get number wrong, but like in the United States here at the beginning, at the end of February, about 2% of the knowledge worker population was virtual, you know, working from home or in a, in a remote work environment. And over the course of about 11 days, that number went from 2% to 70%. Wow. Interesting that it worked, you know, there was a lot of hiccups along the way, and there was a lot of organizations making really quick decisions on how do I enable VPN scale of mass? How do I leverage, uh, you know, things like WebEx for virtual meetings and virtual connectivity, uh, much faster now that as you said, that we kind of gotten out of the fog of, of, of war for our fog of battle organizations are looking at what they accomplished. >>And it was nothing short of Herculean and looking at this now from a transition to, Oh my gosh, we need to change too. We have an opportunity to change. And we're looking, we see a lot of organizations specifically around, uh, financial services, healthcare, uh, the, uh, the K through 20, uh, educational environment, all looking at how can they do more virtually for a couple of reasons. Obviously there is a significant safety factor. And again, we're still in that we're still on the height of this pandemic. They want to make sure their employees, their customers, students, patients remain safe. But second, um, we've found in, in discussions with a lot of senior it executives that our customers, that people are happier working from home, people are more productive working from home. And that, again, the network that's been built over the course of the last few decades has been resilient enough to allow that to happen. >>And then third, there is a potential cost savings here outside of people. The next most expensive resource that organizations are paying for is real estate. If they can shrink that real estate footprint while providing a better user experience at the locations that they're maintaining, again, leveraging things like location services, leveraging things like a unified collaboration. That's very personalized to the end user's experience. They're going to do that. And again, they're going to save money. They're going to have happier employees and ultimately they're going to make their, uh, their employees and their customers a lot safer. So we see, we believe that there is in some parts of the economy, a shift that is going to be more permanent and some estimates put it as high as 15% of the current workforce is going to stay in there in a virtual or a semi virtual working environment for the foreseeable future. >>And I, and I, and I would say, I'd say 15% is low, especially if you, if you qualify it with, you know, part time, right. I, there was a great interview we were doing and talking about working from home, we used to work from home as the exception, right? Cause the cable person was coming, are you getting a new washing machine or something where now that's probably getting, you know, in many cases we'll shift to the other where I'm generally gonna work from home unless, you know, somebody is in town or having an important meeting or there's some special collaboration that drives me to be in. But you know, I want to go back to you Kuhn and, and really doubled down on, you know, I think most people spent too much time focusing, especially, we'll just say within the virtual events base where we play on the things you can't do virtually, we can't meet in the hall. >>We can't grab a quick coffee and a drink instead of focusing on the positive things like we're accomplishing right here, you're in Belgium, right. Eric is in Ohio, we're in California. Um, and you know, we didn't take three days to, to travel and, and check into a hotel and all that stuff to get together, uh, for this period of time. So there's a lot of stuff that digital enables. And I think, you know, people need to focus more on that versus continuing to focus on the two or three things that, that it doesn't replace and it doesn't replace those. So let's just get that off the table and move on with our lives. Cause those aren't coming back anytime soon. >>No, totally. I think it's the balance of those things. It's guarding the fact that you're not necessarily working for home. I think the trick there is you could be sleeping at the office, but I think the positives are way, way more outspoken. Um, I, you know, I look at myself, I got much more exercise time in these last couple of months than I usually do because you don't travel. You don't have the jet lag and the connection. And then you talked about those face to face moments. I think a lot of people are in a way, um, wanting to go back to the office part time as, as Eric also explained. But a lot of it you can do virtually we have virtual coffees with team or, you know, even here in Belgium, our, our local general manager has a virtual effort. TIF every Friday obviously skipped the one this week. But, uh, you know, there's, there's ways to be very creative with the technology and the quality of the technology that the network enables, um, you know, to, to get the best of both worlds. Right? >>So I just, we're going to wrap the segment. I want to give you guys both the last word you both been at Cisco for a while and, you know, Susie, we, and the team on dev net has really grown this thing. I think we were there at the very beginning couple of four, five, six years ago. I can't keep track of time anymore, but you know, it's really, really grown and, you know, the timing is terrific to get into this more software defined world, which is where we are. I wonder if you could just, you know, kind of share a couple thoughts as you know, with a little bit of perspective and you know, what you're excited about today and kind of what you see coming down the road since you guys have been there for a while you've been in this space, uh, let's start with Yukon. >>I think the possibility it creates, I think really programmability software defined is really about the art of the possible it's what you can dream up and then go code. Um, uh, Eric talked about the relevance of it and how it maximizes that relevance on a customer basis. Um, you know, and then it is the evolution of, of the teams in terms of the creativity that they can bring to it. Uh, we're seeing really people dive into that and customers, um, co-creating with us. And I think that's where we're going in terms of like the evolution of the value proposition there in terms of what technology >>Can provide, but also how it impacts people. Has it been discussed and redefines process? >>I love that the art of the possible, which is a lot harder to execute in a, in hardware than software certainly takes a lot longer. I'd love to get your, uh, your thoughts. >>Absolutely. So I started my career at Cisco, uh, turning, uh, putting IP phones onto the network. And back then, you know, it was, you know, 2001, 2002, when, uh, the idea of putting telephones onto the network was such a, um, just such an objectionable idea. And so many purists were telling us all the reasons it wouldn't work. Now, if we go forward again, 19 years, the idea of not having them plugging into the network is a ridiculous idea. So we have a, we're looking at an inflection point in this industry, and it's really, it's not about programming. It's not necessarily about programming. It's about doing it smarter. It's about being more efficient. It's about driving automation, but again, it is, it's about unlocking the value of what the network is. We've moved so far past. What can, you know, just connectivity, the network touches everything and it's more workload moves to the cloud is more workload moves to things like containers. >>Um, the network is the really, the only common element that ties all of these things together. The network needs to take its rightful place, uh, in the end, the, it lexicon as being that critical or that poor critical insight provider, um, for, for how users are interacting with the network, how users are interacting with applications, how applications are interacting with them in another program, ability is a way to do that more efficiently, uh, with greater a greater degree of certainty with much greater relevance into the overall delivery of it services and digitization. So to me, I think we're going to look back 20 years from now, probably even 10 and say, man, we used to configure things manually. What was that like? And I think, I think really this is, this is the future. And I think we want to be aligned with where we're going versus where we've been. >>All right. Well, Coon, Eric, thank you for, for sharing your perspective. You know, it's, it's really nice to have, you know, some historical reference, uh, and it's also nice to be living in a new age where you can, you can, you know, stay at the same company and, and still refresh, you know, new challenges, new opportunities and grow this thing. Cause as you said, I remember those IP first IP phone days and I thought, well, mob bell must be happy because the old mother's day problem is finally solved when we don't have to have a dedicated connection between every mother and every child in the middle of may. So good news. So thank you very much for sharing your, uh, your insights and really, uh, really enjoyed the >>Thank you. >>We've been covering dev net create for a number of years. I think since the very first show and Susie, we and the team really built a practice, built a company, built a lot of momentum around software in the Cisco ecosystem and in getting devs really to start to build applications and drive kind of the whole software defined networking thing forward. And a big part of that is partners and working with partners and, and developing solutions and, you know, using brain power, that's outside of the four walls of Cisco. So we're excited to have, uh, our next guest, uh, a partner for someone is Brad Hoss. He is the engineering director for dev ops at Presidio, Brad. Great to see you. >>Hey Jeff, great to be here. >>Absolutely. And joining him is Chuck Stickney. Chuck is the business development architect for Cisco dev net partners. And he has been driving a whole lot of partner activity for a very long period of time. Chuck, great to see you. >>Thanks Jeff. Great to be here and looking forward to this conversation. >>Absolutely. So let's, let's start with you Chuck, because I think, um, you know, you're leading this kind of partner effort and, and you know, software defined, networking has been talked about for a long time and you know, it's really seems to be maturing and, and software defined everything right. Has been taking over, especially with, with virtualization and moving the flexibility and the customer program ability customability in software and Mo and taking some of that off the hardware. Talk about, you know, the programs that you guys are putting together and how important it is to have partners to kind of move this whole thing forward, versus just worrying about people that have Cisco badges. >>Yeah, Jeff, absolutely. So along this whole journey of dev net where we're, we're trying to leverage that customization and innovation built on top of our Cisco platforms, most of Cisco's businesses transacted through partners. And what we hear from our customers and our partners is they want to, our customers want to way to be able to identify, does this partner have the capabilities and the skills necessary to help me go down this automation journey I'm trying to do, do a new implementation. I want to automate that. How can I find a partner to, to get there? And then we have some of our partners that have been building these practices going along the step in that journey with us for the last six years, they really want to say, Hey, how can I differentiate myself against my competitors and give an edge to my customers to show them that, yes, I have these capabilities. I've built a business practice. I have technology, I have technologists that really understand this capability and they have the net certifications to prove it, help me be able to differentiate myself throughout our ecosystem. So that's really what our Danette partner specialization is all about. >>Right. That's great. And Brad, you're certainly one of those partners and I want to get your perspective because partners are oftentimes a little bit closer to the customer cause you've got your kind of own set of customers that you're building solutions and just reflect on, we know what happened, uh, back in March 15th, when basically everybody was told to go home and you can't go to work. So, you know, there's all the memes and social media about who, you know, who pushed forward your digital transformation, the CEO, the CMO or COVID. And we all know what the answer is, whatever you can share some information as to what happened then, and really for your business and your customers, and then reflect now we're six months into it months plus, and, and you know, this new normal is going to continue for a while. How's the customer attitudes kind of changed now that they're kind of buckled down past the light switch moment and really we need to put in place some foundation to carry forward for a very long time potentially. >>Yeah, it's really quite interesting actually, you know, when code first hit, we got a lot of requests to help with automation of provisioning our customers and in the whole digital transformation got really put on hold for a little bit there and I'd say it became more of, of the workplace transformation. So we were quickly, uh, you know, migrating customers to, you know, new typologies where instead of the, the, you know, users sitting in those offices, they were sitting at home and we had to get them connected rapidly in a, we have a lot of success there in those beginning months with, you know, using automation and programmability, um, building, you know, provisioning portals for our customers to get up and running really fast. Um, and that, that, that was what it looked like in those early days. And then over time, I'd say that's the asks from our customers has started to transition a little bit. >>You know, now they're asking, you know, how can I take advantage of the technology to, you know, look at my offices in a different way, you know, for example, you know, how many people are coming in and out of those locations, you know, what's the usage of my conference rooms. Um, are there, uh, are there, um, situations where I can use that information? Like how many people are in the building and at a certain point in time and make real estate decisions on that, you know, like, do I even need this office anymore? So, so the conversations have really changed in ways that you couldn't have imagined before March. Right. >>And I wonder with, with you Chuck, in terms of the Cisco point of view, I mean, the network is amazing. It had had, COVID struck five years ago, 10 years ago, 15 years ago, you know, clearly there's a lot of industries that are suffering badly entertainment, um, restaurant, business, transportation, they, you know, hospitality, but for those of us in kind of the information industry, the switch was pretty easy. Um, you know, and, and the network enables the whole thing. And so I wonder if, you know, kind of from your perspective as, as suddenly, you know, the importance of the network, the importance of security and the ability now to move to this new normal very quickly from a networking perspective. And then on top of that, having, you know, dev net with, with the software defined on top, you guys were pretty much in a good space as good as space as you could be given this new challenge thrown at you. >>Yeah, Jeff, we completely agree with that. A new Cisco has pushed the idea that the network is transformational. The network is the foundation, and as our customers have really adopted that message, it is enabled that idea for the knowledge workers to be able to continue on. So for myself, I've, I've worked for home the entire time I've been at Cisco. So the last 13 years, this is, you know, the, the change to the normalcy is I never get on a plane anymore, but my day to day functions are still the same. And it's built because of the capabilities we have with the network. I think the transition that we've seen in the industry, as far as kind of moving to that application type of economy, as we go to microservices, as we go to a higher dependency upon cloud, those things have really enabled the world really to be able to better respond to this, to this COVID situation. And I think it's helped to, to justify the investments that's that our customers have made as well as what our partners have been, being able to do to deliver on that multicloud capability, to take those applications, get them closer to the end user instead of sitting in a common data center and then making it more applicable to, to users wherever they may be, not just inside of that traditional form. >>Right. Right. It's interesting that Brad, you, you made a comment on another interview. I was watching getting ready for this one in terms of, uh, applications now being first class citizens was, was what you said. And it's kind of interesting coming from an infrastructure point of view, where before it was, you know, what do I have and what can I build on it now really it's the infrastructure that responds back to the application. And even though you guys are both in the business of, of networking and infrastructure, it's still this recognition that apps first is the way to go, because that gives people the competitive advantage that it gives them the ability to react in the marketplace and to innovate and move faster. So, you know, it's, it's a really interesting twist to be able to support an application first, by having a software defined in a more programmable infrastructure stack. >>Yeah, no doubt. And, you know, I think that the whole push to cloud was really interesting in the early days, it was like, Hey, we're going to change our applications to be cloud first. You know? And then I think the terminology changed over time, um, to more cloud native. So when we, when we look at what cloud has done over the past five years with customers moving, you know, their, their assets into the cloud in the early days that we were all looking at it just like another data center, but what it's really become is a place to host your applications. So when we talk about cloud migrations with our customers now, we're, we're no longer talking about, you know, the assets per se, we're talking about the applications and what did those applications look like? And even what defines an application right now, especially with the whole move to cloud native and microservices in the automation that helps make that all happen with infrastructure as code. >>You're now able to bundle the infrastructure with those applications together as a single unit. So when you define that application, as infrastructure, as code the application in this definition of what those software assets for the infrastructure are, all are wrapped together and you've got change control, version control, um, and it's all automated, you know, it's, it's a beautiful thing. And I think it's something that we've all kind of hoped would happen. You know, in, when I look back at the early definitions of software defined networking, I think everybody was trying to figure it out and they didn't really fully understand what that meant now that we can actually define what that network infrastructure could look like as it's, as it's wrapped around that application in a code template, maybe that's Terraform or Ansible, whatever that might be, whatever method or tool that you're using to bring it all together. It's, you know, it's really interesting now, I think, I think we've gotten to the point where it's starting to make a lot more sense than, you know, those early days of SDN, uh we're out, you know, it was, was it a controller or is it a new version of SNMP? You know, now it makes sense it's actually something tangible. >>Right, right. But still check, as you said, right. There's still a lot of API APIs and there's still a lot of component pieces to these applications that are all run off the network that all have to fit, uh, that had to fit together. You know, we cover PagerDuty summit and you know, their whole thing is trying to find out where the, where the problems are within the very few microseconds that you have before the customer abandons their shopping cart or whatever the particular application. So again, the network infrastructure and the program ability super important. But I wonder if you could speak to the automation because there's just too much stuff going on for individual people to keep track of and they shouldn't be keeping track of it because they need to be focusing on the important stuff, not this increasing amount of bandwidth and traffic going through the network. >>Yeah, absolutely. Jeff said the bandwidth that's necessary in order to support everybody working from home to support this video conference. I mean, we used to do this sitting face to face. Now we're doing this over the internet. The amount of people necessary to, to be able to facilitate that type of traffic. If we're doing it the way we did 10 years ago, we would not scale it's automation. That makes that possible. That allows us to look higher up the ability to do that. Automatic provisional provisioning. Now that we're in microservices now, everything is cloud native. We have the ability to, to better, to better adjust, to and adapt to changes that happen with the infrastructure below hand. So if something goes wrong, we can very quickly spend something ups to take that load off where traditionally it was open up a ticket. Let me get someone in there, let me fix it. >>Now it's instantaneously identify the solution, go to my playbook, figure out exactly what solution I need to deploy and put that out there. And the network engineering team, the infrastructure engineering team, they just simply need to get notified that this happened. And as long as there's traceability and a point that Brad made, as far as you being able to go through here doing the automation of the documentation side of it. I know when I was a network engineer, one of the last things we ever did was documentation. But now that we have the API is from the infrastructure. And then the ability to tie that into other systems like an IP address management or a change control, or a trouble ticketing system, that whole idea of I made an infrastructure change. And now I can automatically do that documentation update and record. I know who did it. I know when they did it and I know what they did, and I know what the test results were even five years ago, that was fantasy land. Now, today that's just the new normal, that's just how we all operate. Right. >>Right, right. So I want to get your take on the other side, >>Cloud multicloud >>Public cloud, you know, as, as I think you said Brad, when public cloud first came out, there was kind of this, this rush into, we're going to throw everything in there then for, for, for different reasons. People decided maybe that's not the best, the best solution, but really it's horses for courses. Right. And, and I think it was pretty interesting that, that you guys are all supporting the customers that are trying to figure out where they're going to put their workloads. And Oh, by the way, that might not be a static place, right. It might be moving around based on, you know, maybe I do my initial dev and, and, and Amazon. And then when I go into production, maybe I want to move it into my data center and then maybe I'm having a big promotion or something I want to flex capability. So from, from your perspective in helping customers work through this, cause still there's a lot of opinions about what is multicloud, what is hybrid cloud and you know, it's horses for courses, how are you helping people navigate that? And what does having programmable infrastructure enable you to do for helping customers kind of sort through, you know, everybody talks about their journey. I think there's still, you know, kind of bumbling down, bumbling down paths, trying to find new things, what works, what doesn't work. And I think it's still really early days and trying to mesh all this stuff together. Yeah, >>Yeah. No doubt. It is still early days. And you know, I, I, I go back to it being application centric because, you know, being able to understand that application, when you move to the cloud, it may not look like what it used to look like when you, when you move it over there, you may be breaking parts off of it. Some of them might be running on a platform as a service while other pieces of it are running as infrastructure as service. And some of it might still be in your data center. Those applications are becoming much more complex than they used to be because we're breaking them apart into different services. Those services could live all over the place. So with automation, we really gain the power of being able to combine those things. As I mentioned earlier, those resources, wherever they are and be defined in that infrastructure as code and automation. >>But you know, aside from, I think we focus a lot about provisioning. When we talk about automation, we also have these amazing capabilities on, on the side of, uh, operations too. Like we've got streaming telemetry, and the ability to gain insights into what's going on in ways that we didn't have before, or at least in the, in, you know, in the early days of monitoring software, right? You knew exactly what that device was, where it was. It probably had a friendly name, like maybe it was, uh, something from the Hobbit right now. You've got things coming up and spinning and spinning up and spinning down, moving all over the place. In that thing. You used to know what that was. Now you have to quickly figure out where it went. So the observability factor is a huge thing that I think everybody, um, should be paying attention to attention, to moving forward with regards to when you're moving things to the cloud or even to other data centers or, you know, in your premise, I'm breaking that into microservices. >>You really need to understand what's going on. And the, you know, programmability and API APIs and, you know, yang models are tied into streaming telemetry. Now there's just so many great things coming out of this, you know, and it's all like a data structure that, that people who are going down this path and the dev net path there, they're learning these data structures and being able to rationalize and make sense of that. And once you understand that, then all of these things come together, whether it's cloud or a router or switch, um, Amazon, you know, it doesn't matter. You're on, you're all speaking a common language, which is that data structure. >>That's great. Chuck, I want to shift gears a little bit. Cause there was something that you said in another interview when I was getting ready for this one about, about in a dev net, really opening up a whole different class of partners for Cisco, um, as, as really more of a software, a software lead versus kind of the traditional networking lead. I wonder if you can put a little more color on that. Um, because clearly as you said, partners are super important. It's your primary go to market and, and Presidios, I'm sure the best partner that you have in the whole world that's and you know, you said there's some, there's some, you know, non traditional people that would not ever be a Cisco partner that suddenly you guys are playing with because of really the software lead. >>Yeah. Jeff that's exactly right. So as we've been talking to folks with dev nets and whether it'd be at one of the Cisco live events in the dev net zone or the prior dev net create events, we'll have, we'll have people come up to us who Cisco today views as a, as a customer because they're not in our partner ecosystem. They want to be able to deliver these capabilities to our customers, but they have no interest in being in the resell market. This what we're doing with the doublet that gives us the ability to bring those partners into the ecosystem, share them with our extremely large dev net community so they can get access to those, to those potential customers. But also it allows us to do partner to partner type of integration. So Brad and Presidio, they built a fantastic networking. They always have the fantastic networking business, but they've built this fantastic automation business that's there, but they may come into, into a scenario where it's working with a vertical or working with the technology case that they may not have an automation practice for. >>We can leverage some of these software specific partners to come in there and do a joint, go to markets where, so they can go where that traditional channel partner can leverage their deep Cisco knowledge in those customer relationships that they have and bring in that software partner almost as a subcontractor to help them deliver that additional business value on top of that traditional stack, that brings us to this business outcomes that the customers are looking for and a much faster fashion and a much more collaborative fashion. That's terrific. Well, again, it's a, it's, it's unfortunate that we can't be in person. I mean, the, the Cisco dev net shows, you know, they're still small, they're still intimate. There's still a lot of, uh, information sharing and, you know, great to see you. And like I said, we've been at the computer museum, I think the last couple of years and in, in San Francisco. So I look forward to a time that we can actually be together, uh, maybe, maybe for next year's event, but, uh, thank you very much for stopping by and sharing the information. Really appreciate it. Happy to be here from around the globe. It's the cube presenting, accelerating automation with Devin brought to you by Cisco. >>When I'm Sean for the cube, your host for accelerating automation with dev net, with Cisco, and we're here to close out the virtual event with Mindy Whaley, senior director, Mandy, take it away. >>Thank you, John. It's been great to be here at this virtual event and hearing all these different automation stories from our different technology groups, from customers and partners. And what I'd like to take a minute now is to let people know how they can continue this experience at DevNet create, which is our free virtual event happening globally. On October 13th, there's going to be some really fun stuff. We're going to have our annual demo jam, which is kind of like an open mic for demos, where the community gets to show what they've been building. We're also going to be, um, giving out and recognizing our dev net creator award winners for this year, which is a really great time where we recognize our community contributors who have been giving back to the community throughout the year. And then we find really interesting channels. We have our creators channels, which is full of technical talks, lightening talks. >>This is where our community, external Cisco people come in share what they've been working on, what they've been working learning during the year. We also have a channel called API action, which is where you can go deep into, you know, IOT or collaboration or data center automation and get demos talks from engineers on how to do certain use cases. And also a new segment called street from engineering, where you get to hear from the engineers, building those products as well. And we have a start now for those people just getting started, who may need to dive into some basics around coding, API APIs and get that's a whole channel dedicated to getting them started so that they can start to participate in some of the fun challenges that we're going to have during the event. And we're going to have a few fun things. Like we have some definite advocate team members who are awesome, musically talented. They're going to share some performances with us. So, um, we encourage everyone to join us there. Pick your favorite channel, uh, join us in whichever time zone you live in. Cause we'll be in three different time zones. And, um, we would love for you to be there and to hear from you during the event. Thanks so much. >>That's awesome. Very innovative, multiple time zones, accelerating automation with dev net. Thank you so much for watching and we'll see you at dev net create thanks for watching.