>> the CUBE presents Dell Technologies World brought to you by Dell. >> Hey everyone, welcome back to the CUBE'S coverage day one, Dell Technologies World 2022 live from The Venetian in Las Vegas. Lisa Martin, with Dave Vellante. We've been here the last couple of hours. You can hear probably the buzz behind me. Lots of folks here, we're think around seven to eight thousand folks in this solution expo, the vibe is awesome. We've got two guests helping to round out our day one coverage. Ryan Fournier joins us, senior director of product management Edge Solutions at Dell Technologies. And MuneyB Minttazuddin vice president of Edge Computing at VMware. Guys, welcome to the program. >> Oh, glad to be here. >> Yeah. >> Isn't it great to be here in person? >> Oh man, yes. >> The vibe, the vibe of day one is awesome. >> Yes. >> Oh yeah. >> I think it's fantastic. >> Like people give energy off to each other, right? >> Absolutely. So lots of some good news coming out today so far on day one. Let's talk about, Ryan let's start with you. With Edge, it's not new. We've been talking about it for a while, but what are some of the things that are new? What are some of the key trends that you are seeing that are driving changes at the Edge? >> Great, good question. We've been talking to a lot of customers. Okay, a lot of the customers you know, the different verticals really find that is a common theme happening around a massive digital transformation and really based on the pandemic, okay. Which caused some acceleration in some, but also not, but many are kind of laggers left behind. And one primary reason is the culture of the OT, IT, you know, lack of barriers or something like that. The OT is obviously the business outcomes, okay. Focused where the IT is more enabling the function and it'll take retail. For example, that's accelerated a significant usage of an in-store frictionless experience, okay. As well as supply chain automation, warehousing logistics, connected inventory, a lot of the new use cases in this new normal post that pandemic. It's really that new retail operating landscape. >> Consumers we are so demanding, we want the same experience that we have online and we want that in the store and that's really driving a lot of this out of consumer demand. >> Oh yeah, no. I think, you know, retail you know, the way you shop for milk and bread change during the pandemic, right? There was pre-pandemic. The online shopping in the United States was only 5%, but during the pandemic and afterwards that's going to caught up to 25, 30%. That's huge. How do you bring new processes in? How do you create omnichannel consumer experiences where online well as physical are blended together? Becomes a massive challenge for the retailers. So yes, Edge has been there for a long time. Innovation hasn't happened, but a simple credit card swipe When you used to pre-pandemic, just to go do your checkout now has become into a curbside pickup. Integration with like, it's just simple payment card processing is not complicated like, you know, crazy. So people are forced to go in a way and that's happening in manufacturing because they're supply chain issues, could be not. So a lot of that has accelerated this investment and what's kind of driving Edge Computing is if everything ran out of the cloud, then you almost need infinite bandwidth. So suddenly people are realizing that everything runs out of cloud. I can't process my video analytics in a store. That's a lot of video, right? >> So we often ask ourselves, okay, who's going to win the edge? You know, we have that conversation. The cloud guys? VMware? You know, Dell? How are they going to go at it? And so to your point, you're not going to do a round trip to the cloud too expensive, too slow. Now cloud guys will try to bring their cloud basically on prem or out to the edge. You're kind of bringing it from the data center. So how do you see that evolution? >> No, great question. As the edge market happens, right? So there's market data now which says enterprise edge workloads in the next five years are going to be the fastest growing workloads. But then you have different communities coming to solve that problem. Like you just said, John is, you know, hyperscalers are going, Hey, all of the new workloads were built on us, let's bring them to the edge. Data center workloads move to the edge. >> Now important community here are, you know, Telcos and Service Providers because they have assets that are highly distributed at the edge. However, they're networking assets like cell towers and stuff like that. There's opportunity to convert them into computer and storage assets. So you can provide edge computing POPs. So you're seeing a convergence of lot of industry segments, traditional IT, hyperscalers, telcos, and then OT like Ryan pointed out is naturally transforming itself. There's almost this confluence of this pot where all these different technologies need to come together. From VMware and Dell perspective, our mission is a multi-cloud edge. We want to be able to support multi-cloud services because you've heard this multiple times, is at the edge consumers and customers will require services from all the hyperscalers. They don't want buy a one hyperscaler suit to suit solution. They want to mix and match. So not bound. We want be multi-cloud south bound to support IT and OT environments. So that becomes our value proposition in the middle. >> Yep. >> So Ryan, you were talking about that IT, OT schism. And we talk about that a lot. I wonder if you could help us parse that a little bit, because you were using, for instance retail, as an example. Sometimes I think about in the industrial. >> And I think the OT people are kind of like having an engineering mindset. Don't touch my stuff. Kind of like the IT guys too, but different, you know. So there's so much opportunity at the edge. I wonder how you guys think about that? How you segment it? How you prioritize it? Obviously retail telco are big enough. >> Yep. >> That you can get your hands around them, but then there's to your point about all this data that's going to going to compute. It's going to come in pockets. And I wonder how you guys think about that schism and the other opportunity. >> Yeah, out there. It's also a great question, you know, in manufacturing. There's the true OT persona. >> Yeah. >> Okay, and that really is focused on the business outcomes. Things like predictive maintenance use cases, operational equipment effectiveness, like that's really around bottleneck analysis, and the process that go through that. If the plant goes down, they're fine, okay. They can still work on their own systems, but they're not needing that high availability solution. But they're also the decision makers and where to buy the Edge Computing, okay. So we need to talk more to the OT persona from a Dell perspective, okay. And to add on to Ryan, right. So industrial is an interesting challenge, right? So one of the things we did, and this is VMware and Dell working together at vMware it was virtual. We announced something called edge compute stack. And for the first time in 23 years of vMware history, we made the hypervisor layer real-time. >> Yep. >> What that means is in order to capture some of these OT workloads, you need to get in and operate it between the industrial PC and the program of logical controllers at a sub millisecond performance level, because now you're controlling robotic arms that you cannot miss a beat. So we actually created this real time functionality. With that functionality in the last six months, we've been able to virtualize PLCs, IPCs. So what I'm getting at is we're opening up an entire wide space of operational technology workloads, which we was not accessible to our market for the last 20 plus years. >> Now we're talking. >> Yeah. And that allows us that control plane infrastructure to edge compute. There's purpose built for edge allows us to pivot and do other solutions like analytics with the adoption of AI Analytics with our recent announcement of Deep North, okay. That provides that in store video analytics functionality. And then we also partner with PTC based on a manufacturing solution, working with that same edge compute stack. Think of that as that control plane, where again, like I said, you can pivot off a different solutions. Okay, so we leverage PTCs thing works. >> So, okay, great. So I wanted to go to that. So real-time's really interesting. >> 'Cause most of much of AI today is modeling done in the cloud. >> Yes. >> The real opportunity is real time inferencing at the edge. >> You got it. >> Okay, now this is why this gets so interesting. And I wonder if Project Monterey fits into this at all. because I feel like so why did Intel win? Intel won, it crushed all the Unix systems out there because it had PC volumes. And the edge volume's going to dwarf anything we've ever seen before. >> Yeah. >> So I feel like there's this new cocktail, you guys describe this convergence and this mixture and it's unknown. What's going to happen? That's why Project Monterey is so interesting. >> Of course. >> Yeah. >> Right? Because you're bringing together kind of hedging a lot of bets and serving a lot of different use cases. Maybe you could talk about where that might fit here. >> Oh absolutely. So the edge compute stack is made up of vSphere, Tanzu, which is vSphere's you know, VM container and Tanzu's our container technology and vSphere contains Monterey in it, right. And we've added vSAN a for storage at the edge. And connectivity is SD-WAN because a lot of the times it's far location. So you're not having a large footprint, you have one or two hoses, it's more wide area, narrow area. So the edge compute stack supports real-time, non-real-time time workloads. VMs and containers, CPU GPU, right. >> NPU, accelerators, >> NPU, DPU all of them, right. Because what you're dealing with here is that inferencing real time, because to Ryan's point, when you're doing predictive maintenance, you got to pick these signals up in like milliseconds. >> Yes. >> So we've gone our stack down to microseconds and we pick up and inform because if I can save this predictive maintenance in two seconds, I save millions of dollars in you know, wastage of product, right? >> And you may not even persist that data, right? You might just let it go, I mean, how much data does Tesla save? Right? I mean. >> You're absolutely right. A lot of the times, all you're doing is this volume of data coming at you. You're matching it to an inferencing pattern. If it doesn't match, you just drop, right. It's not persistent, but the moment you hit a trigger, immediately everything lights go off, you're login, you're applying outcome. So like super interesting at the edge. >> And the compute is going to go through the roof. So yeah, my premise is that, you know, general purpose x86 running SAP is not going to be the architecture for the edge. >> You're absolutely right. >> Going to be low cost, low power, super performance. 'Cause when you combine the CPU, GPU, NPU, you're going to blow away the performance that we've ever seen on the curves. >> There's also a new application pattern. I've called out something called edge-native applications. We went through this client-server architecture era. We built all this, you know, a very clear in architecture. We went through cloud native where everything was hyperscaled in the cloud. Both of the times we optimize our own compute. >> Yeah. >> At the edge, we got to optimize our owns data because it's not ephemeral compute that you have in hyperscale compute space, you have ephemeral data you got to deal with. So a new nature of application workloads are emerging. We call it edge-native apps. >> Yep. >> And those have very different characteristics, you know, to client server apps or you know, cloud native apps, which is amazing. It's driven by data analysts like developers, not like dot net Java developers. It's actually data analysts who are trying to mine this with fast patents and come out with outcomes, right? >> Yeah, I love that edge-native apps Lisa, that's a new term for me. >> Right, just trademark it on me. I made made it up. (panel laughing) >> Can you guys talk about a joint customer that you've really helped to dramatically transform in the last six months? >> You want to shout or I can go-- >> I think my industry is fine. >> Yeah, yeah. So, you know, at VMworld we talked about Oshkosh, which is again, like in the manufacturing space, we have retailers and manufacturers and we also brought in, you know, Proctor and Gamble and et cetera, et cetera, right? So the customers look at us jointly because you know edge doesn't happen in its own silo. It's a continuum from the data center to the cloud, to the edge, right. There's the continuum exists. So if only edge was in its own silo, you would do things. But the key thing about all of this, there's no right place, it's about that workload placement. Where do I place the workload for the most optimal business outcome? Now for real-time applications, it's at the edge. For non-real-time stuff it could be in the data center, it could be in a cloud. It doesn't really matter, where VMware and Dell strengths comes in with Oshkosh or all of those folks. We have the end-to-end. From you want place it in the data center, You want to place it in your charge to public cloud, You want to derive some of these applications. You want to place it at the far edge, which is a customer prem or a near edge, which is a telco. We've done joint announcements with telcos, like South Dakota Telecom, where we've taken their cell towers and converted them into compute and storage. So they can actually store it at the near edge, right. So this is 5G solutions. I also own the 5G part of the vMware business, but doesn't matter. Compute network storage, we got to find the right mix for placing the workload at the right place. >> You call that the near edge. I think of it as the far edge, but that's what you mean, right? >> Yeah, yeah. >> Way out there in the (mumbles), okay. >> It's all about just optimizing operations, reducing cost, increasing profitability for the customer. >> So you said edge, not its own silo. And I agree. >> it's not a silo. Is mobile a valid sort of example or a little test case because when we developed mobile apps, it drove a lot of things in the data center and in the cloud. Is that a way to think of about it as opposed to like PCs work under their own silo? Yeah, we connect to the internet, but is mobile a reasonable proxy or no? >> Mobile is an interesting proxy. When you think about the application again, you know, you got a platform by the way, you'll get excited by this. We've got mobile developers, mobile device manufacturers. You can count them in your fingers. They want to now have these devices sitting in factory floors because now these devices are so smart. They have sensors, temperature controls. They can act like these multisensory device at the edge, but the app landscape is quite interesting. I think John, where you were going was they have a very thin shim app layer that can be pushed from anywhere. The, the notion of these edge-native applications could be virtual machines, could be containers, could be, you know, this new thing called Web Assembly Wasm, which is a new type of technology, very thin shim layer which is mobile like app layer. But you know, all of these are combination of how these applications may get expressed. The target platforms could be anywhere from mobile devices to IOT gateways, to IOT devices, to servers, to, you know, massive data centers. So what's amazing is this thing can just go everywhere. And our goal is consistent infrastructure, consistent operations across the board. That's where VMware and Dell win together. >> Yeah. >> Yeah, excellent. And I was just talking to a customer today, a major airline manufacturer, okay. About their airport and the future with the mobile device just being frictionless, okay, no one wants to touch anything anymore. You can use your mobile device to do your check-in and you've got to you avoid kiosks, okay. So they're trying to figure out how to get rid of the kiosk. Now you need a kiosk for like checking baggage, okay. You can't get in the way of that, but at least that frictionless experience, for that airport in the future, but it brings in some other issues. >> It does, but I like the sound of that. Last question guys, where can customers go to learn more information about the joint solutions? >> So you can go to like our public websites obviously search on edge. And if you hear at the show, there's a lot of hands on labs, okay. There's a booth over there. A lot of Edge Solutions that we offer. >> Yeah, no, this is I guess as Ryan pointed our websites have these. We've had a lot of partnership in announcements together because you know, one of the things as we've expressed, manufacturing, retail, you know, when you get in the use cases, they involve ISPs, right? So they you know, they bring the value of you know, not just having a horizontal AI platform. We like opinionated models of fraud detection. So we're actually working with ecosystem of partners to make this real. >> So we may even hear more. >> The rich vertical solution, I call it the ISVs. They enrich our vertical solutions. >> Right. >> Oh, WeMo is going to be revolutionary. >> All right, can't wait. Guys thank you so much for joining David and me today and talking about what Dell and vMware are doing together and helping retailers manufacturers really convert the edge to incredible success. We appreciate your time. >> Thank you very much. Thanks Lisa, thanks John for having us. >> For Dave Vellante, I'm Lisa Martin. You're watching the CUBE. We are wrapping up day one of our coverage of Dell Technologies World 2022. We'll be back tomorrow, John Farrer and Dave Nicholson will join us. We'll see you then. (soft music)

(upbeat music) >> From around the globe, it's theCUBE. With digital coverage of Postgres Vision 2021 brought to you by EDB. >> Well, good day, everybody. John Walls here on theCUBE. We continue our coverage here at Postgres Vision in 2021. Talking today with Andy Harris, who is the Chief Technology Officer at Osirium, a leader in the Privileged Access Management Space, and Andy, good day to you. Thanks for joining us here on theCUBE. >> Good morning to you and good afternoon, yes. >> That's right. Joining us from overseas over in England, we're on this side of the big pond, but nonetheless, we're joined by the power of Zoom. So again, thanks for the time. Andy, for those who aren't familiar who are watching about Osirium, share a little bit about your various service levels of what you provide, the kind of solutions you provide, and how you've achieved a great success in this space. >> Okay. I know these things, mine will be boring. So I'll just put a little slide up now, which is the minimum I think I can get away with which is that we're all about managing privilege. So that's privileged at the endpoint, Privileged Access Management, and Privileged Process Automation. So wherever a CIS admin has to do something on a machine that needs privilege, we like to be involved. Obviously, we like to be able to delegate all the way down to the business functions with Privileged Process Automation and with the EDB or the BDR part of that functionality in EDB that really fits in to our Privileged Access Management. So what I'll do just to take you away from our product. So I'll just quickly show you a slide of the architecture, which is as simple as we have these nodes. If you like the running ADB BDR and they can perform log-ins to a target device using privileged credentials, which we control when we might be really long up to about 128 characters. >> So Andy, if you would, I think you had put together a little show and tell you a demonstration for how when these systems are perhaps under siege if you will. That there are ways in which obviously you've developed to counter this and to be able to continue secure communications, which in the privilege assets world as you know is paramount. >> Yes, indeed. So I'll show you another slide, which gives you a kind of a overview of everything that's going on and you're going to see a little demonstration of two nodes here that has the BDL technology on and they can make these logins, and we have these characters, Bob and Allison. I've just noticed how it marks in department turn Alice to Allison. they should really be Alice because you get Bob, Alice, Carol, Dave, which are the standard encryption users. And what we're going to do is we're going to demonstrate that you can have breaks in the network. So I'm just sharing the network breaks slide. I'm showing the second network break slide. And then we have this function that we've built which we're going to demonstrate for you today, which is called evil beatings. And what it does is whilst there is a politician in the network, we are going to refresh many thousands of times the credentials on the target device. And then we're going to heal the break in the network and then prove that everything is still working. So right now, I'm going to zoom over to my live connection, terminal connections to the machine. And I'm going to run this command here, which is Python EV3. And I'm going to put a hundred cycles in it which is going to do around about 10,000 password refreshes. Okay. And I'm then going to go over to Chrome, and I should have a system here waiting for me. And in this system, you'll see that I've got the device demo and I've got this come online, SSH. And if I click on this I've got a live connection to this machine. Even whilst I have a huge number of queued up and I'll just show you the queued out connections through the admin interface. The system is working extremely hard at the moment. And in fact, if I show you this slide here, you can see that I have all of these queued credential resets and that is giving our system an awful lot of grief. Yeah. I can go back to the device connection and it is all here still top. Why not? And as you can see, it is all working perfectly. And if I was a user of EDB, I think this has to be one of the demonstrations I'd be interested in because it's one of the first things that we did when we dropped that functionality into our products. We wanted to know how well it would work under extreme conditions because you don't think of extreme conditions as normal working, but whenever you have 10 nodes in different countries, there will always be a network break somewhere and someone will always need to be refreshing passwords a ridiculous rates of knots. So Andy let's talk about this kind of the notion that you're providing here, this about accountability and visibility, audit-ability, all these insights that you're providing through this kind of demonstration you've given us how critical is that today, especially when we know there are so many possible intrusions and so many opportunities with legacy systems and new apps and all of this. I mean talking about those three pillars, if you will, the importance of that and what we just saw in terms of providing that peace of mind that everybody wants in their system. >> That's a cracking question. I'm going to enjoy that question. Legacy systems, that's a really good question. If you, we have NHS, which is our national health service and we have hospitals and you have hospitals every country has hospitals. And the equipment that they use like the MRI scanners, the electro-microscope, some of the blood analysis machines, the systems in those costs multiple Gillions of dollars or should use dollars euros, dollars, pounds and the operating systems running those systems, the lifetime of that piece of equipment is much much longer than the lifetime of an operating system. So we glibly throw around this idea of legacy systems and to a hospital that's a system that's a mere five years old and has got to be delivering for another 15 years. But in reality, all of this stuff gets, acquires vulnerabilities because our adversaries the people that want to do organizations bad things ransomware and all the rest of it they are spending all that time learning about the vulnerabilities of old systems. So the beauty of what we do is being able to take those old legacy systems and put a zero trust safety shell around them, and then use extremely long credentials which can't be cracked. And then we make sure that those credentials don't go anywhere near any workstations. But what they do do, is they're inside that ADB database encrypted with a master encryption key, and they make that jump just inside the zero trust boundary so that Bob and Alice outside can get administration connections inside for them to work. So what we're doing is providing safety for those legacy systems. We are also providing an environment for old apps to run in as well. So we have something called a map server which I didn't think you'd asked us that question. I'd have to find you some slides or presentations, which we want to do. We have a map server, which is effectively a very protected window server, and you can put your old applications on them and you can let them age gracefully and carry on running. Dot net 3.5 and all of those old things. And we can map your connection into the older application and then map those connections out. But in terms of the other aspects of it is the hospital stay open 24 hours a day banks run 24 hours a day and they need to be managed from anywhere. We're in a global pandemic, people are working from home. That means that people are working from laptops and all sorts of things that haven't been provisioned by centrality and could all have all sorts of threats and problems to them. And being able to access any time is really important. And because we are changing the credentials on these machines on a regular basis, you cannot lose one. It's absolutely critical. You cannot go around losing Windows active directory domain credentials it just can't be done. And if you have a situation where you've just updated a password and you've had a failure one of those 10 nodes has the correct set of credentials. And when the system heals, you have to work out which one of the 10 it is and the one that did it last must be the one that updates all the other 10 nodes. And I think the important thing is as Osirium we have the responsibility for doing the updates and we have the responsibility for tracking all those things. But we hand the responsibility of making sure that all the other 10 nodes are up to date which just drop it into bi-directional replication and it just happens. And you've seen it happen. I mean, might be just for the fun of it, We'll go back to that demonstration Chrome, and you can see we're still connected to that machine. That's all still running fine but we could go off to our management thing, refresh it and you see that everything there is successful. I can go to a second machine and I can make a second connection to that device. Yet, in the meantime that password has been changed, Oh, I mean, I wouldn't like to tell you how many times it's been changed. I need to be on a slightly different device. I was going to do a reveal password for you, I'll make another connection but the passwords will be typically, do a top on that just to create some more load. But the passwords will typically be... I'll come back to me. They'll typically be 128 characters long. >> Andy, if I could, I mean, 'cause I think you're really showing this very complex set of challenges that you have these days, right? In terms of providing access to multiple devices across, in multiple networking challenges, when you talk to your prospective clients about the kind of how this security perimeters changed, it's very different now than it was four or five years ago. What are the key points that you want them to take away from your discussion about how they have to think about security and access especially in this day and age when we've even seen here in the States. Some very serious intrusions that I think certainly get everybody's attention. >> That's a great question again. They're all... The way that I would answer that question would definitely depend on the continent that I was talking to. But my favorite answer will be a European answer, so I'll give you a European answer. One of the things that you're doing when you come along and provide Privileged Access Management to a traditional IT team, is your taking away the sysadmins right now, before privilege access, they will know the passwords. They will be keeping the passwords in a password vault or something like this. So they own the passwords, they own the credentials. And when you come along with a product like privilege access management you're taking over management of those credentials and you're protecting those systems from a whole wide range of threats. And one of those threats is from the system administrators themselves. And they understand that. So what I would say, it's an interesting question. 'Cause I'm like, I'm thinking I've got two ways of answering I can answer as if I'm talking to management or as if I'm talking to the people who are actually going to use the products and I feel more aligned with the, I feel more aligned with the actual users. >> Yeah, I think let's just, we'll focus on that and I'll let you know, we just have a moment or two left. So if you could maybe boil it down for me a little bit. >> Boiling it down, I would say now look here CIS admins. It's really important that you get your job done but you need to understand that those privileged accounts that you're using on those systems are absolute gold dust if they get into the hands of your adversaries and you need protections income away from those adversaries, but we trust you and we are going to get you the access to your machines as fast as possible. So we're a little bit like a nightclub bouncer but we're like the Heineken of nightclub bounces. When you arrive, we know it's you and we're going to get you to your favorite machine logged on as domain admin, as fast as possible. And while you're there, we're going to cut that session recording of you. And just keep you safe and on the right side. >> All right, I'm going to enjoy my night in the nightclub. Now I can sleep easy tonight knowing that Andy Harris and Osirium are on the case. Thanks, Andy. Andy Harris speaking with us. So the Chief Technology Officer from Osirium as part of our Postgres vision, 2021, coverage here on theCUBE. (upbeat music) >> From theCUBE studios in Palo Alto, in Boston connecting with thought leaders all around the world. This is theCUBE conversation.

>>Welcome back to the cubes coverage of dr khan 2021. I'm john for your host of the cube. We're here with Amanda Silver, corporate vice president, product developer division at Microsoft. Amanda, Great to see you you were on last year, Dr khan. Great to see you again a full year later were remote. Thanks for coming on. I know you're super busy with build happening this week as well. Thanks for making the time to come on the cube for Dr khan. >>Thank you so much for having me. Yeah, I'm joining you like many developers around the globe from my personal home office, >>developers really didn't skip a beat during the pandemic and again, it was not a good situation but developers, as you talked about last year on the front lines, first responders to creating value quite frankly, looking back you were pretty accurate in your prediction, developers did have an impact this year. They did create the kind of change that really changed the game for people's lives, whether it was developing solutions from a medical standpoint or even keeping systems running from call centres to making sure people got their their their goods or services and checks and and and kept sanity together. So. >>Yeah absolutely. I mean I think I think developers you know get the M. V. P. Award for this year because you know at the end of the day they are the digital first responders to the first responders and the pivot that we've had to make over the past year in terms of supporting remote telehealth, supporting you know online retail, curbside pickup. All of these things were done through developers being the ones pushing the way forward remote learning. You know my kids are learning at home right behind me right now so you might hear them during the interview that's happening because developers made that happen. >>I don't think mom please stop hogging the band with, they've got a gigabit. Stop it. Don't be streaming. My kids are all game anyway, Hey, great to have you on and you have to get the great keynote, exciting to see you guys continue the collaboration with Docker uh with GIT hub and Microsoft, A great combination, it's a 123 power punch of value. You guys are really kind of killing it. We heard from scott and dan has been on the cube. What's your thoughts on the partnership with the developer division team at Microsoft with Doctor, What's it all about this year? What's the next level? >>Well, I mean, I think, I think what's really awesome about this partnership is that we all have, we all are basically sharing a common mission. What we want to do is make sure that we're empowering developers, that we're focused on their productivity and that we're delivering value to them so they can do their job better so that they can help others. So that's really kind of what drives us day in and day out. So what we focus on is developer productivity. And I think that's a lot of what dana was talking about in her session, the developer division. Specifically, we really try to make sure that we're improving the state of the art from modern developers. So we want to make sure that every keystroke that they take, every mouse move that they make, it sounds like a song but every every one of those matter because we want to make sure that every developers writing the code that only they can write and in terms of the partnership and how that's going. You know my team and the darker team have been collaborating a ton on things like dr desktop and the Doctor Cli tool integrations. And one of the things that we do is we think about pain points and various workflows. We want to make sure that we're shaving off the edges of all of the user experience is the developers have to go through to piece all of these applications together. So one of the big pain points that we have heard from developers is that signing into the Azure cloud and especially our sovereign clouds was challenging. So we contributed back to uh back to doctor to actually make it easier to sign into these clouds. And so dr developers can now use dr desktop and the Doctor Cli to actually change the doctor context so that its Azure. So that makes it a lot easier to connect the other. Oh, sorry, go ahead. No, I was just >>going to say, I love the reference of the police song. Every breath you take, every >>mouth moving. Great, >>great line there. Uh, but I want to ask you while you're on this modern cloud um, discussion, what is I mean we have a lot of developers here at dr khan. As you know, you guys know developers in your ecosystem in core competency. From Microsoft, Kublai khan is a very operator like focus developed. This is a developer conference. You guys have build, what is the state of the art for a modern cloud developer? Could you just share your thoughts because this comes up a lot. You know, what's through the art? What's next jan new guard guard? It's his legacy. What is the state of the art for a modern cloud developer? >>Fantastic question. And extraordinarily relevant to this particular conference. You know what I think about often times it's really what is the inner loop and the outer loop look like in terms of cycle times? Because at the end of the day, what matters is the time that it takes for you to make that code change, to be able to see it in your test environment and to be able to deploy it to production and have the confidence that it's delivering the feature set that you need it to. And it's, you know, it's secure, it's reliable, it's performance, that's what a developer cares about at the end of the day. Um, at the same time, we also need to make sure that we're growing our team to meet our demand, which means we're constantly on boarding new developers. And so what I take inspiration from our, some of the tech elite who have been able to invest significant amounts in, in tuning their engineering systems, they've been able to make it so that a new developer can join a team in just a couple of minutes or less that they can actually make a code change, see that be reflected in their application in just a few seconds and deploy with confidence within hours. And so our goal is to actually be able to take that state of the art metric and democratize that actually bring it to as many of our customers as we possibly can. >>You mentioned supply chain earlier in securing that. What are you guys doing with Docker and how to make that partnership better with registries? Is there any update there in terms of the container registry on Azure? >>Yeah, I mean, you know, we, we we have definitely seen recent events and and it almost seems like a never ending attacks that that you know, increasingly are getting more and more focused on developer watering holes is how we think about it. Kind of developers being a primary target um for these malicious hackers. And so what it's more important than ever that every developer um and Microsoft especially uh really take security extraordinarily seriously. Our engineers are working around the clock to make sure that we are responding to every security incident that we hear about and partnering with our customers to make sure that we're supporting them as well. One of the things that we announced earlier this week at Microsoft build is that we've actually taken, get have actions and we've now integrated that into the Azure Security Center. And so what this means is that, you know, we can now do things like scan for vulnerabilities. Um look at things like who is logging in, where things like that and actually have that be tracked in the Azure security center so that not just your developers get that notification but also your I. T. Operations. Um In terms of the partnership with dR you know, this is actually an ongoing partnership to make sure that we can provide more guidance to developers to make sure that they are following best practices like pulling from a private registry like Docker hub or at your container registry. So I expect that as time goes on will continue to more in partnership in this space >>and that's going to give a lot of confidence. Actually, productivity wise is going to be a big help for developers. Great stuff is always good, good progress. They're moving the needle. >>Last time we >>spoke we talked about tools and setting Azure as the doctor context duty tooling updates here at dot com this year. That's notable. >>Yeah, I mean, I think, you know, there's one major thing that we've been working on which has a big dependency on docker is get help. Code space is now one of the biggest pain points that developers have is setting up a new DEV box, which they often have to do when they are on boarding a new employee or when they're starting a new project or even if they're just kicking the tires on a new technology that they want to be able to evaluate and sometimes creating a developer environment can actually take hours um and especially when you're trying to create a developer environment that matches somebody else's developer environment that can take like a half a day and you can spend all of your time just debugging the differences in environment variables, for example, um, containers actually makes that much easier. So what you can do with this, this services, you can actually create death environment spun up in the cloud and you can access it in seconds and you get from there are working coding environment and a runtime environment and this is repeatable via containers. So it means that there's no inadvertent differences introduced by each DEV. And you might be interested to know that underneath this is actually using Docker files and dr composed to orchestrate the debits and the runtime bits for a whole bunch of different stacks. And so this is something that we're actually working on in collaboration with the with the doctor team to have a common the animal format. And in fact this week we actually introduced a couple of app templates so that everybody can see this all in action. So if you check out a ca dot m s forward slash app template, you can see this in action yourself. >>You guys have always had such a strong developer community and one thing I love about cloud as it brings more agility, as we always talk about. But when you start to see the enterprise grow into, the direction is going now, it's almost like the developer communities are emerging, it's no longer about all the Lennox folks here and the dot net folks there, you've got windows, you've got cloud, >>it's almost >>the the the solidification of everyone kind of coming together. Um and visual studio, for instance, last year, I think you were talking about that to having to be interrogated dr composed, et cetera. >>How do you see >>this melting pot emerging? Because at the end of the day, you pick the language you love and you got devops, which is infrastructure as code doesn't matter. So give us your take on where we are with that whole progress of of making that happen. >>Well, I mean I definitely think that, you know, developer environments and and kind of, you know, our approach to them don't need to be as dogmatic as they've been in the past. I really think that, you know, you can pick the right tool and language and stand developer stack for your team, for your experience and you can be productive and that's really our goal. And Microsoft is to make sure that we have tools for every developer and every team so that they can build any app that they want to want to create. Even if that means that they're actually going to end up ultimately deploying that not to our cloud, they're going to end up deploying it to AWS or another another competitive cloud. And so, you know, there's a lot of things that we've been doing to make that really much easier. We have integrated container tools in visual studio and visual studio code and better cli integrations like with the doctor context that we had talked about a little bit earlier. We continue to try to make it easier to build applications that are targeting containers and then once you create those containers it's much easier to take it to another environment. One of the examples of this kind of work is now that we have WsL and the Windows subsystem for Lennox. This makes it a lot easier for developers who prefer a Windows operating system as their environment and maybe some tools like Visual Studio that run on Windows, but they can still target Lennox with as their production environment without any impedance mismatch. They can actually be as productive as they would be if they had a Linux box as their Os >>I noticed on this session, I got to call this out. I want to get your reaction to it interesting. Selection of Microsoft talks, the container based development. Visual studio code is one that's where you're going to show some some some container action going on with note and Visual Studio code. And then you get the machine learning with Azure uh containers in the V. S. Code. Interesting how you got, you know, containers with V. S. And now you've got machine learning. What does that tell the world about where Microsoft's at? Because in a way you got the cutting edge container management on one side with the doctor integration. Now you get the machine learning which everyone's talking about shifting, left more automation. Why are these sessions so important? Why should people attend? And what's the what's the bottom line? >>Well, like I said, like containers basically empower developer productivity. Um that's what creates the reputable environments, that's what allows us to make sure that, you know, we're productive as soon as we possibly can be with any text act that we want to be able to target. Um and so that's kind of almost the ecosystem play. Um it's how every developer can contribute to the success of others and we can amor ties the kinds of work that we do to set up an environment. So that's what I would say about the container based development that we're doing with both visual studio and visual studio code. Um in terms of the machine learning development, uh you know, the number of machine learning developers in the world is relatively small, but it's growing and it's obviously a very important set of developers because to train a machine learning uh to train an ml model, it actually requires a significant amount of compute resources, and so that's a perfect opportunity to bring in the research that are in a public cloud. Um What's actually really interesting about that particular develop developer stack is that it commonly runs on things like python. And for those of you who have developed in python, you know, just how difficult it is to actually set up a python environment with the right interpreter, with the right run time, with the right libraries that can actually get going super quickly, um and you can be productive as a developer. And so it's actually one of the hardest, most challenging developer stacks to actually set up. And so this allows you to become a machine learning developer without having to spend all of your time just setting up the python runtime environment. >>Yeah, it's a nice, nice little call out on python, it's a double edged sword. It's easier to sling code around on one hand, when you start getting working then you gotta it gets complicated can get well. Um Well the great, great call out there on the island, but good, good, good project. Let me get your thoughts on this other tool that you guys are talking about project tie. Uh This is interesting because this is a trend that we're seeing a lot of conversations here on the cube about around more too many control planes. Too many services. You know, I no longer have that monolithic application. I got micro micro applications with microservices. What the hell is going on with my services? >>Yeah, I mean, I think, you know, containers brought an incredible amount of productivity in terms of having repeatable environments, both for dev environments, which we talked about a lot on this interview already, but also obviously in production and test environments. Super important. Um and with that a lot of times comes the microservices architecture that we're also moving to and the way that I view it is the microservices architecture is actually accompanied by businesses being more focused on the value that they can actually deliver to customers. And so they're trying to kind of create separations of concerns in terms of the different services that they're offering, so they can actually version and and kind of, you know, actually improve each of these services independently. But what happens when you start to have many microservices working together in a SAS or in some kind of aggregate um service environment or kind of application environment is it starts to get unwieldy, it's really hard to make it so that one micro service can actually address another micro service. They can pass information back and forth. And you know what used to be maybe easy if you were just building a client server application because, you know, within the server tear all of your code was basically contained in the same runtime environment. That's no longer the case when every microservices actually running inside of its own container. So the question is, how can we improve program ability by making it easier for one micro service that's being used in an application environment, be to be able to access another another service and kind of all of that context. Um and so, you know, you want to be able to access the service is the the api endpoint, the containers, the ingress is everything, make everything work together as though it felt just as easy as as um you know, server application development. Um And so what this means as well is that you also oftentimes need to get all of these different containers running at the same time and that can actually be a challenge in the developer and test loop as well. So what project tie does is it improves the program ability and it actually allows you to just write a command like thai run so that you can actually in stan she ate all of these containers and get them up and running and basically deploy and run your application in that environment and ultimately make the dev testing or loop much faster >>than productivity gain. Right. They're making it simple to stand up. Great, great stuff. Let me ask you a question as we kind of wrap down here for the folks here at Dakar Con, are >>there any >>special things you'd like to talk about the development you think are important for the developers here within this space? It's very dynamic. A lot of change happening in a good way. Um, but >>sometimes it's hard to keep >>track of all the cool stuff happening. Could you take a minute to, to share your thoughts on what you think are the most important develops developments in this space? That that might be interesting to ducker con attendees. >>I think the most important things are to recognize that developer environments are moving to containerized uh, environments themselves so that they can be repeated, they can be shared, the work, configuring them can be amortized across many developers. That's important thing. Number one important thing. Number two is it doesn't matter as much what operating system you're running as your chrome, you know, desktop. What matters is ultimately the production environment that you're targeting. And so I think now we're in a world where all of those things can be mixed and matched together. Um and then I think the next thing is how can we actually improve microservices, uh programming development together um so that it's easier to be able to target multiple micro services that are working in aggregate uh to create a single service experience or a single application. And how do we improve the program ability for that? >>You know, you guys have been great supporters of DACA and the community and open source and software developers as they transform and become quite frankly the superheroes for the transformation, which is re factoring businesses. So this has been a big thing. I'd love to get your thoughts on how this is all coming together inside Microsoft, you've got your division, you get the developer division, you got GIT hub, got Azure. Um, and then just historically, and he put this up last year army of an ecosystem. People who have been contributing encoding with Microsoft and the partners for many, many decades. >>Yes. The >>heart Microsoft now, how's it all working? What's the news? I get Lincoln, Lincoln, but there's no yet developer model there yet, but probably is soon. >>Um Yeah, I mean, I think that's a pretty broad question, but in some ways I think it's interesting to put it in the context of Microsoft's history. You know, I think when I think back to the beginning of my career, it was kind of a one stack shop, you know, we was all about dot net and you know, of course we want to dot net to be the best developer environment that it can possibly be. We still actually want that. We still want that need to be the most productive developer environment. It could we could possibly build. Um but at the same time, I think we have to recognize that not all developers or dot net developers and we want to make sure that Azure is the most productive cloud for developers and so to do that, we have to make sure that we're building fantastic tools and platforms to host java applications, javascript applications, no Js applications, python applications, all of those things, you know, all of these developers in the world, we want to make sure it can be productive on our tools and our platforms and so, you know, I think that's really kind of the key of you know what you're speaking of because you know, when I think about the partnership that I have with the GIT hub team or with the Azure team or with the Azure Machine learning team or the Lincoln team, um A lot of it actually comes down to helping empower developers, improving their productivity, helping them find new developers to collaborate with, um making sure that they can do that securely and confidently and they can basically respond to their customers as quickly as they possibly can. Um and when, when we think about partnering inside of Microsoft with folks like linkedin or office as an example, a lot of our partnership with them actually comes down to improving their colleagues efficiency. We build the developer tools that office and lengthen are built on top of and so every once in a while we will make an improvement that has, you know, 5% here, 3% there and it turns into an incredible amount of impact in terms of operations, costs for running these services. >>It's interesting. You mentioned earlier, I think there's a time now we're living in a time where you don't have to be dogmatic anymore, you can pick what you like and go with it. Also that you also mentioned just now this idea of distributed applications, distributed computing. You know, distributed applications and microservices go really well together. Especially with doctor. >>Can you share >>your thoughts on the framework that you guys released called Dapper? >>Yeah, yeah. We recently released Dapper. It's called D A P R. You can look it up on GIT hub and it's a programming model for common microservices pattern, two common microservices patterns that make it really easy and automatic to create those kinds of microservices. So you can choose to work with your favorite state stores or databases or pub sub components and get things like cloud events for free. You can choose either http or g R B C so that you can get mesh capabilities like service discovery and re tries and you can bring your own secret store and easily be able to call it from any environment variable. It's also like I was talking about earlier, multi lingual. Um so you don't need to embrace dot net, for example, as you're programming language to be able to benefit from Dapper, it actually supports many programming languages and Dapper itself is actually written and go. Um and so, you know, all developers can benefit from something like Dapper to make it easier to create microservices applications. >>I mean, always great to have you on great update. Take a minute to give an update on what's going on with your division. I know you had to build conference this week. V. S has got the new preview title. We just talked about what are the things you want to get to plug in for? Take a minute to get to plug in for what you're working on, your goals, your objectives hiring, give us the update. >>Yeah, sure. I mean, you know, we we built integrated container tools in visual studio uh and the Doctor extension and Visual Studio code and cli extensions. Uh and you know, even in this most recent release of our Visual Studio product, Visual Studio 16 10, we added some features to make it easier to use DR composed better. So one of the examples of this is that you can actually have uh Oftentimes you need to be able to use multiple doctor composed files together so that you can actually configure various different container environments for a single single application. But it's hard sometimes to create the right Yeah. My file so that you can actually invoke it and invoke the the container and the micro services that you need. And so what this allows you to do is to actually have just a menu of the different doctor composed files so that you can select the runtime and test environment that you need for the subset of the portion of the application that you're working on at the end of the day. This is always about developer productivity. You know, like I said, every keystroke matters. Um and we want to make sure that you as a developer can focus on the code that only you can Right. >>Amanda Silver, corporate vice president product development division of Microsoft. Always great to see you and chat with you remotely soon. We'll be back in in real life with real events soon as we come out of the pandemic and thanks for sharing your insight and congratulations on your success this year and and congratulations on your announcement here at Dakar Gone. >>Thank you so much for having me. >>Okay Cube coverage for Dunkirk on 2021. I'm John for your host of the Cube. Thanks for watching. Mhm

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America 2020 Virtual brought to you by Red Hat The Cloud, Native Computing Foundation and Ecosystem Partners. Hello, everyone. And welcome back to the cubes Ongoing coverage of Cuba con North America. Joe Fernandez is here. He's with Stephanie, Cheras and Joe's, the V, P and GM for core cloud platforms. That red hat and Stephanie is this s VP and GM of the Red Hat Enterprise. Lennox bu. Two great friends of the Cube. Awesome seeing you guys. How you doing? >>It's great to be here, Dave. Yeah, thanks >>for the opportunity. >>Hey, so we all talked, you know, recently, uh, answerable fest Seems like a while ago, but But we talked about what's new? Red hat really coming at it from an automation perspective. But I wonder if we could take a view from open shift and what's new from the standpoint of you really focus on helping customers, you know, change their operations and operationalize. And Stephanie, Maybe you could start, and then, you know, Joe, you could bring in some added color. >>No, that's great. And I think you know one of the things we try and do it. Red hat clearly building off of open source. We have been focused on this open hybrid cloud strategy for, you know, really years. Now the beauty of it is that hybrid cloud and open hybrid cloud continues to evolve right with bringing in things like speed and stability and scale and now adding in other footprints, like manage services as well as edge and pulling that all together across the whole red hat portfolio from the platforms, right? Certainly with Lennox and roll into open shift in the platform with open shift and then adding automation, which certainly you need for scale. But it's ah, it's continues to evolve as the as the definition of open hybrid cloud evolves. >>Great. So thank you, Stephanie jokes. You guys got hard news here that you could maybe talk about 46? >>Yeah. Eso eso open shift is our enterprise kubernetes platform. With this announcement, we announced the release of open ship 4.6 Eso eso We're doing releases every quarter tracking the upstream kubernetes release cycle. So this brings communities 1.19, which is, um but itself brings a number of new innovations, some specific things to call out. We have this new automated installer for open shift on bare metal, and that's definitely a trend that we're seeing is more customers not only looking at containers but looking at running containers directly on bare metal environments. Open shift provides an abstraction, you know, which combines Cuban. And he's, uh, on top of Lennox with RL. I really across all environments, from bare metal to virtualization platforms to the various public clouds and out to the edge. But we're seeing a lot of interest in bare metal. This is basically increasing the really three automation to install seamlessly and manage upgrades in those environments. We're also seeing a number of other enhancements open shifts service mesh, which is our SDO based solution for managing, uh, the interactions between micro services being able to manage traffic against those services. Being able to do tracing. We have a new release of that on open shift Ford out six on then, um, some work specific to the public cloud that we started extending into the government clouds. So we already supported AWS and Azure. With this release, we added support for the A W s government cloud as well. Azaz Acela's Microsoft Azure government on dso again This is really important to like our public sector customers who are looking to move to the public cloud leveraging open shift as an abstraction but wanted thio support it on the specialized clouds that they need to use with azure gonna meet us Cup. >>So, joke, we stay there for a minute. So so bare metal talking performance there because, you know, you know what? You really want to run fast, right? So that's the attractiveness there. And then the point about SDO in the open, open shift service measure that makes things simpler. Maybe talk a little bit about sort of business impact and what customers should expect to get out of >>these two things. So So let me take them one at a time, right? So so running on bare metal certainly performances a consideration. You know, I think a lot of fixed today are still running containers, and Cuban is on top of some form of virtualization. Either a platform like this fear or open stack, or maybe VMS in the in one of the public clouds. But, you know containers don't depend on a virtualization layer. Containers only depend on Lennox and Lennox runs great on bare metal. So as we see customers moving more towards performance and Leighton see sensitive workloads, they want to get that Barry mental performance on running open shift on bare metal and their containerized applications on that, uh, platform certainly gives them that advantage. Others just want to reduce the cost right. They want to reduce their VM sprawl, the infrastructure and operational cost of managing avert layer beneath their careers clusters. And that's another benefit. So we see a lot of uptake in open shift on bare metal on the service match side. This is really about You know how we see applications evolving, right? Uh, customers are moving more towards these distributed architectures, taking, you know, formally monolithic or enter applications and splitting them out into ah, lots of different services. The challenge there becomes. Then how do you manage all those connections? Right, Because something that was a single stack is now comprised of tens or hundreds of services on DSO. You wanna be able to manage traffic to those services, so if the service goes down, you can redirect that those requests thio to an alternative or fail over service. Also tracing. If you're looking at performance issues, you need to know where in your architecture, er you're having those degradations and so forth. And, you know, those are some of the challenges that people can sort of overcome or get help with by using service mash, which is powered by SDO. >>And then I'm sorry, Stephanie ever get to in a minute. But which is 11 follow up on that Joe is so the rial differentiation between what you bring in what I can just if I'm in a mono cloud, for instance is you're gonna you're gonna bring this across clouds. I'm gonna You're gonna bring it on, Prem And we're gonna talk about the edge in in a minute. Is that right? From a differentiation standpoint, >>Yeah, that That's one of the key >>differentiations. You know, Read has been talking about the hybrid cloud for a long time. We've we've been articulating are open hybrid cloud strategy, Andi, >>even if that's >>not a strategy that you may be thinking about, it is ultimately where folks end up right, because all of our enterprise customers still have applications running in the data center. But they're also all starting to move applications out to the public cloud. As they expand their usage of public cloud, you start seeing them adopted multi cloud strategies because they don't want to put all their eggs in one basket. And then for certain classes of applications, they need to move those applications closer to the data. And and so you start to see EJ becoming part of that hybrid cloud picture on DSO. What we do is basically provide a consistency across all those environments, right? We want run great on Amazon, but also great on Azure on Google on bare metal in the data center during medal out at the edge on top of your favorite virtualization platform. And yeah, that that consistency to take a set of applications and run them the same way across all those environments. That is just one of the key benefits of going with red hat as your provider for open hybrid cloud solutions. >>All right, thank you. Stephanie would come back to you here, so I mean, we talk about rail a lot because your business unit that you manage, but we're starting to see red hats edge strategy unfolded. Kind of real is really the linchpin I wanna You could talk about how you're thinking about the edge and and particularly interested in how you're handling scale and why you feel like you're in a good position toe handle that massive scale on the requirements of the edge and versus hey, we need a new OS for the edge. >>Yeah, I think. And Joe did a great job of said and up it does come back to our view around this open hybrid cloud story has always been about consistency. It's about that language that you speak, no matter where you want to run your applications in between rela on on my side and Joe with open shift and and of course, you know we run the same Lennox underneath. So real core os is part of open shift that consistently see leads to a lot of flexibility, whether it's through a broad ecosystem or it's across footprints. And so now is we have been talking with customers about how they want to move their applications closer to data, you know, further out and away from their data center. So some of it is about distributing your data center, getting that compute closer to the data or closer to your customers. It drives, drives some different requirements right around. How you do updates, how you do over the air updates. And so we have been working in typical red hat fashion, right? We've been looking at what's being done in the upstream. So in the fedora upstream community, there is a lot of working that has been done in what's called the I. O. T Special Interest group. They have been really investigating what the requirements are for this use case and edge. So now we're really pleased in, um, in our most recent release of really aid relate 00.3. We have put in some key capabilities that we're seeing being driven by these edge use cases. So things like How do you do quick image generation? And that's important because, as you distribute, want that consistency created tailored image, be able to deploy that in a consistent way, allow that to address scale, meet security requirements that you may have also right updates become very important when you start to spread this out. So we put in things in order to allow remote device mirroring so that you can put code into production and then you can schedule it on those remote devices toe happen with the minimal disruption. Things like things like we all know now, right with all this virtual stuff, we often run into things like not ideal bandwidth and sometimes intermittent connectivity with all of those devices out there. So we put in, um, capabilities around, being able to use something called rpm Austria, Um, in order to be able to deliver efficient over the air updates. And then, of course, you got to do intelligent rollbacks for per chance that something goes wrong. How do you come back to a previous state? So it's all about being able to deploy at scale in a distributed way, be ready for that use case and have some predictability and consistency. And again, that's what we build our platforms for. It's all about predictability and consistency, and that gives you flexibility to add your innovation on top. >>I'm glad you mentioned intelligent rollbacks I learned a long time ago. You always ask the question. What happens when something goes wrong? You learn a lot from the answer to that, but You know, we talk a lot about cloud native. Sounds like you're adapting well to become edge native. >>Yeah. I mean, I mean, we're finding whether it's inthe e verticals, right in the very specific use cases or whether it's in sort of an enterprise edge use case. Having consistency brings a ton of flexibility. It was funny, one of our talking with a customer not too long ago. And they said, you know, agility is the new version of efficiency. So it's that having that sort of language be spoken everywhere from your core data center all the way out to the edge that allows you a lot of flexibility going forward. >>So what if you could talk? I mentioned just mentioned Cloud Native. I mean, I think people sometimes just underestimate the effort. It takes tow, make all this stuff run in all the different clouds the engineering efforts required. And I'm wondering what kind of engineering you do with if any with the cloud providers and and, of course, the balance of the ecosystem. But But maybe you could describe that a little bit. >>Yeah, so? So Red Hat works closely with all the major cloud providers you know, whether that's Amazon, Azure, Google or IBM Cloud. Obviously, Andi, we're you know, we're very keen on sort of making sure that we're providing the best environment to run enterprise applications across all those environments, whether you're running it directly just with Lennox on Ralph or whether you're running it in a containerized environment with Open Chef, which which includes route eso eso, our partnership includes work we do upstream, for example. You know, Red Hat help. Google launched the Cuban community, and I've been, you know, with Google. You know, we've been the top two contributors driving that product that project since inception, um, but then also extends into sort of our hosted services. So we run a jointly developed and jointly managed service called the Azure Red Hat Open Shift Service. Together with Microsoft were our joint customers can get access to open shift in an azure environment as a native azure service, meaning it's, you know, it's fully integrated, just like any other. As your service you can tied into as you're building and so forth. It's sold by by Azure Microsoft's sales reps. Um, but you know, we get the benefit of working together with our Microsoft counterparts and developing that service in managing that service and then in supporting our joint customers. We over the summer announced sort of a similar partnership with Amazon and we'll be launching are already doing pilots on the Amazon Red Hat Open ship service, which is which is, you know, the same concept now applied to the AWS cloud. So that will be coming out g a later this year, right? But again, whether it's working upstream or whether it's, you know, partnering on managed services. I know Stephanie team also do a lot of work with Microsoft, for example, on sequel server on Lenox dot net on Lenox. Whoever thought be running that applications on Linux. But that's, you know, a couple of years old now, a few years old, So eso again. It's been a great partnership, not just with Microsoft, but with all the cloud providers. >>So I think you just shared a little little He showed a little leg there, Joe, what's what's coming g A. Later this year. I want to circle back to >>that. Yeah, eso we way announced a preview earlier this year of of the Amazon Red Hat Open ships service. It's not generally available yet. We're you know, we're taking customers. We want toe, sort of be early access, get access to pilots and then that'll be generally available later this year. Although Red Hat does manage our own service Open ship dedicated that's available on AWS today. But that's a service that's, you know, solely, uh, operated by Red Hat. This new service will be jointly operated by Red Hat and Amazon together Idea. That would be sort of a service that we are delivering together as partners >>as a managed service and and okay, so that's in beta now. I presume if it's gonna be g a little, it's >>like, Yeah, that's yeah, >>that's probably running on bare metal. I would imagine that >>one is running >>on E. C. Two. That's running an A W C C T V exactly, and >>run again. You know, all of our all of >>our I mean, we you know, that open shift does offer bare metal cloud, and we do you know, we do have customers who can take the open shift software and deploy it there right now are managed. Offering is running on top of the C two and on top of Azure VM. But again, this is this is appealing to customers who, you know, like what we bring in terms of an enterprise kubernetes platform, but don't wanna, you know, operated themselves, right? So it's a fully managed service. You just come and build and deploy your APS, and then we manage all of the infrastructure and all the underlying platform for you >>that's going to explode. My prediction. Um, let's take an example of heart example of security. And I'm interested in how you guys ensure a consistent, you know, security experience across all these locations on Prem Cloud. Multiple clouds, the edge. Maybe you could talk about that. And Stephanie, I'm sure you have a perspective on this is Well, from the standpoint of of Ralph. So who wants to start? >>Yeah, Maybe I could start from the bottom and then I'll pass it over to Joe to talk a bit. I think one of these aspects about security it's clearly top of mind of all customers. Um, it does start with the very bottom and base selection in your OS. We continue to drive SC Lennox capabilities into rural to provide that foundational layer. And then as we run real core OS and open shift, we bring over that s C Lennox capability as well. Um, but, you know, there's a whole lot of ways to tackle this we've done. We've done a lot around our policies around, um see ve updates, etcetera around rail to make sure that we are continuing to provide on DCA mitt too. Mitigating all critical and importance, providing better transparency toe how we assess those CVS. So security is certainly top of mind for us. And then as we move forward, right there's also and joke and talk about the security work we do is also capabilities to do that in container ization. But you know, we we work. We work all the way from the base to doing things like these images in these easy to build images, which are tailored so you can make them smaller, less surface area for security. Security is one of those things. That's a lifestyle, right? You gotta look at it from all the way the base in the operating system, with things like sc Lennox toe how you build your images, which now we've added new capabilities. There And then, of course, in containers. There's, um there's a whole focus in the open shift area around container container security, >>Joe. Anything you want to add to that? >>Yeah, sure. I >>mean, I think, you know, obviously, Lennox is the foundation for, you know, for all public clouds. It's it's driving enterprise applications in the data center, part of keeping those applications. Security is keeping them up to date And, you know, through, you know, through real, we provide, you know, securing up to date foundation as a Stephanie mentioned as you move into open shift, you're also been able to take advantage of, uh, Thio to take advantage of essentially mutability. Right? So now the application that you're deploying isn't immutable unit that you build once as a container image, and then you deploy that out all your various environments. When you have to do an update, you don't go and update all those environments. You build a new image that includes those updates, and then you deploy those images out rolling fashion and, as you mentioned that you could go back if there's issues. So the idea, the notion of immutable application deployments has a lot to do with security, and it's enabled by containers. And then, obviously you have cured Panetti's and, you know, and all the rest of our capabilities as part of open Shift managing that for you. We've extended that concept to the entire platform. So Stephanie mentioned, real core West Open shift has always run on real. What we have done in open shift for is we've taken an immutable version of Ralph. So it's the same red hat enterprise Lennox that we've had for years. But now, in this latest version relate, we have a new way to package and deploy it as a relic or OS image, and then that becomes part of the platform. So when customers want toe in addition to keeping their applications up to date, they need to keep their platform up to dates. Need to keep, you know, up with the latest kubernetes patches up with the latest Lennox packages. What we're doing is delivering that as one platform, so when you get updates for open shift, they could include updates for kubernetes. They could include updates for Lennox itself as well as all the integrated services and again, all of this is just you know this is how you keep your applications secure. Is making sure your you know, taking care of that hygiene of, you know, managing your vulnerabilities, keeping everything patched in up to date and ultimately ensuring security for your application and users. >>I know I'm going a little bit over, but I have I have one question that I wanna ask you guys and a broad question about maybe a trends you see in the business. I mean, you look at what we talk a lot about cloud native, and you look at kubernetes and the interest in kubernetes off the charts. It's an area that has a lot of spending momentum. People are putting resource is behind it. But you know, really, to build these sort of modern applications, it's considered state of the art on. Do you see a lot of people trying to really bring that modern approach toe any cloud we've been talking about? EJ. You wanna bring it also on Prem And people generally associate this notion of cloud native with this kind of elite developers, right? But you're bringing it to the masses and there's 20 million plus software developers out there, and most you know, with all due respect that you know they may not be the the the elites of the elite. So how are you seeing this evolve in terms of re Skilling people to be able, handle and take advantage of all this? You know, cool new stuff that's coming out. >>Yeah, I can start, you know, open shift. Our focus from the beginning has been bringing kubernetes to the enterprise. So we think of open shift as the dominant enterprise kubernetes platform enterprises come in all shapes and sizes and and skill sets. As you mentioned, they have unique requirements in terms of how they need toe run stuff in their data center and then also bring that to production, whether it's in the data center across the public clouds eso So part of it is, you know, making sure that the technology meets the requirements and then part of it is working. The people process and and culture thio make them help them understand what it means to sort of take advantage of container ization and cloud native platforms and communities. Of course, this is nothing new to red hat, right? This is what we did 20 years ago when we first brought Lennox to the Enterprise with well, right on. In essence, Carozza is basically distributed. Lennox right Kubernetes builds on Lennox and brings it out to your cluster to your distributed systems on across the hybrid cloud. So So nothing new for Red Hat. But a lot of the same challenges apply to this new cloud native world. >>Awesome. Stephanie, we'll give you the last word, >>all right? And I think just a touch on what Joe talked about it. And Joe and I worked really closely on this, right? The ability to run containers right is someone launches down this because it is magical. What could be done with deploying applications? Using a container technology, we built the capabilities and the tools directly into rural in order to be able to build and deploy, leveraging things like pod man directly into rural. And that's exactly so, folks. Everyone who has a real subscription today can start on their container journey, start to build and deploy that, and then we work to help those skills then be transferrable as you movinto open shift in kubernetes and orchestration. So, you know, we work very closely to make sure that the skills building can be done directly on rail and then transfer into open shift. Because, as Joe said, at the end of the day, it's just a different way to deploy. Lennox, >>You guys are doing some good work. Keep it up. And thanks so much for coming back in. The Cube is great to talk to you today. >>Good to see you, Dave. >>Yes, Thank you. >>All right. Thank you for watching everybody. The cubes coverage of Cuba con en a continues right after this.

>>from around the globe. It's the queue with digital coverage of AWS public sector online brought to you by Amazon Web services. >>Everyone welcome back to the Cube's virtual coverage of AWS Public sector summit online. That's the virtual conference. Public Sector Summit is the big get together for Teresa Carlson and her team and Amazon Web services from the public sector, which includes all the government agencies as well as education state governments here in United States and also abroad for other governments and countries. So we're gonna do an analysis of Teresa's keynote and also summarize the event as well. I'm John Furrow, your host of the Cube. I'm joined with my co host of the Cube, Dave Volante Stew Minimum. We're gonna wrap this up and analyze the keynote summit a really awkward, weird situation going on with the Summit because of the virtual nature of it. This event really prides itself. Stew and Dave. We've all done this event. It's one of our favorites. It's a really good face to face environment, but this time is virtual. And so with the covert 19 that's the backdrop to all this. >>Yeah, so I mean, a couple of things, John. I think first of all, A Z, you've pointed out many times. The future has just been pulled forward. I think the second thing is with this whole work from home in this remote thing obviously was talking about how the cloud is a tailwind. But let's face it. I mean, everybody's business was affected in some way. I think the cloud ultimately gets a tail wind out of this, but but But I think the third thing is security. Public sector is always heavily focused on security, and the security model has really changed overnight to what we've been talking about for years that the moat that we've built the perimeter is no longer where organizations need to be spending money. It's really to secure remote locations. And that literally happened overnight. So things like a security cloud become much, much more important. And obviously endpoint security and other other things that we've talked about in the Cube now for last 100 days. >>Well, Steve, I want to get your thoughts cause you know, we all love space. Do we always want to go the best space events that they're gonna be virtual this year as well? Um, But the big news out of the keynote, which was really surprising to me, is Amazon's continued double down on their efforts around space, cyber security, public and within the public sector. And they're announcing here, and the big news is a new space business segment. So they announced an aerospace group to serve those customers because space to becoming a very important observation component to a lot of the stuff we've seen with ground station we've seen at reinvent public sector. These new kinds of services are coming out. It's the best, the cloud. It's the best of data, and it's the best of these new use cases. What's your thoughts? >>Yeah, interesting. John, of course. You know, the federal government has put together Space Forces, the newest arm of the military. It's really even though something it is a punchline. There's even a Netflix show that I believe got the trademark board because they registered for it first. But we've seen Amazon pushing into space. Not only there technology being used. I had the pleasure of attending the Amazon re Marcia last year, which brought together Jeff Bezos's blue origin as well as Amazon AWS in that ecosystem. So AWS has had a number of services, like ground Station that that that are being used to help the cloud technology extend to what's happening base. So it makes a lot of sense for for the govcloud to extend to that type of environment aside you mentioned at this show. One of the things we love always is. You know, there's some great practitioner stories, and I think so many over the years that we've been doing this show and we still got some of them. Theresa had some really good guests in her keynote, talking about transformation and actually, one of the ones that she mentioned but didn't have in the keynote was one that I got to interview. I was the CTO for the state of West Virginia. If you talk about one of those government services that is getting, you know, heavy usage, it's unemployment. So they had to go from Oh my gosh, we normally had people in, you know, physical answering. The phone call centers to wait. I need to have a cloud based contact center. And they literally did that, you know, over the weekend, spun it up and pulled people from other organizations to just say, Hey, you're working from home You know you can't do your normal job Well, we can train your own, we can get it to you securely And that's the kind of thing that the cloud was really built for >>and this new aerospace division day this really highlights a lot of not just the the coolness of space, but on Earth. The benefits of there and one of Amazon's ethos is to do the heavy lifting, Andy Jassy told us on the Cube. You know, it could be more cost effective to use satellites and leverage more of that space perimeter to push down and look at observation. Cal Poly is doing some really interesting work around space. Amazon's worked with NASA Jet Propulsion Labs. They have a lot of partnerships in aerospace and space, and as it all comes together because this is now an augmentation and the cost benefits are there, this is going to create more agility because you don't have to do all that provisioning to get this going spawned. All kinds of new creativity, both an academic and commercial, your thoughts >>Well, you know, I remember the first cloud first came out people talked a lot about while I can do things that I was never able to do before, you know, The New York Times pdf example comes to mind, but but I think what a lot of people forget is you know the point to a while. A lot of these mission critical applications Oracle databases aren't moving to the cloud. But this example that you're giving and aerospace and ground station. It's all about being able to do new things that you weren't able to do before and deliver them as a service. And so, to me, it shows a great example of tam expansion, and it also shows things that you never could do before. It's not just taking traditional enterprise APs and sticking them in the cloud. Yeah, that happens. But is re imagining what you can do with computing with this massive distributed network. And you know, I O. T. Is clearly coming into into play here. I would consider this a kind of I o t like, you know, application. And so I think there are many, many more to come. But this is a great example of something that you could really never even conceive in enterprise Tech before >>you, Dave the line on that you talked about i o t talk a lot about edge computing. Well, if you talk about going into space, that's a new frontier of the edge that we need to talk about >>the world. Glad it's round. So technically no edge if you're in space so again not to get nuance here and nerdy. But okay, let's get into the event. I want to hold on the analysis of the keynote because I think this really society impact public service, public sector, things to talk about. But let's do a quick review of kind of what's happened. We'll get to the event. But let's just review the guests that we interviewed on the Cube because we have the cube virtual. We're here in our studios. You guys were in yours. We get the quarantine cruise. We're still doing our job to get the stories out there. We talked to Teresa Carlson, Shannon Kellogg, Ken Eisner, Sandy Carter, Dr Papa Casey Coleman from Salesforce, Dr Shell Gentleman from the Paragon Institute, which is doing the fairground islands of researcher on space and weather data. Um, Joshua Spence math you can use with the Alliance for Digital Innovation Around some of this new innovation, we leave the Children's National Research Institute. So a lot of great guests on the cube dot net Check it out, guys. I had trouble getting into the event that using this in Toronto platform and it was just so hard to navigate. They've been doing it before. Um, there's some key notes on there. I thought that was a disappointment for me. I couldn't get to some of the sessions I wanted to, um, but overall, I thought the content was strong. Um, the online platform just kind of wasn't there for me. What's your reaction? >>Well, I mean, it's like a Z. That's the state of the art today. And so it's essentially a webinar like platforms, and that's what everybody's saying. A lot of people are frustrated with it. I know I as a user. Activity clicks to find stuff, but it is what it is. But I think the industry is can do better. >>Yeah, and just to comment. I'll make on it, John. One of things I always love about the Amazon show. It's not just what AWS is doing, But, you know, you walk the hallways and you walk the actual So in the virtual world, I walk the expo floor and its okay, Here's a couple of presentations links in an email address if you want to follow up, I felt even the A previous AWS online at a little bit more there. And I'm sure Amazon's listening, talking to all their partners and building out more there cause that's definitely a huge opportunity to enable both networking as well. As you know, having the ecosystem be able to participate more fully in the event >>and full disclosure. We're building our own platform. We have the platforms. We care about this guys. I think that on these virtual events that the discovery is critical having the available to find the sessions, find the people so it feels more like an event. I think you know, we hope that these solutions can get better. We're gonna try and do our best. Um, so, um well, keep plugging away, guys. I want to get your thoughts. They have you been doing a lot of breaking analysis on this do and your interviews as well in the technology side around the impact of Covert 19 with Teresa Carlson and her keynote. Her number one message that I heard was Covad 19 Crisis has caused a imperative for all agencies to move faster, and Amazon is kind of I won't say put things to the side because they got their business at scale. Have really been honing in on having deliverables for crisis solutions. Solving the problems and getting out to Steve mentioned the call centers is one of the key interviews. This is that they're job. They have to do this cove. It impacts the public services of the public sector that she's that they service. So what's your reaction? Because we've been covering on the commercial side. What's your thoughts of Teresa and Amazon's story today? >>Yeah, well, she said, You know, the agencies started making cloud migrations that they're at record pace that they'd never seen before. Having said that, you know it's hard, but Amazon doesn't break out its its revenue in public sector. But in the data, I look at the breaking analysis CTR data. I mean, it definitely suggests a couple of things. Things one is I mean, everybody in the enterprise was affected in some way by Kobe is they said before, it wouldn't surprise me if there wasn't a little bit of a pause and aws public sector business and then it's picking up again now, as we sort of exit this isolation economy. I think the second thing I would say is that AWS Public sector, based on the data that I see, is significantly outpacing the growth of AWS. Overall number one number two. It's also keeping pace with the growth of Microsoft Azure. Now we know that AWS, on balance is much bigger than Microsoft Azure and Infrastructures of Service. But we also know that Microsoft Azure is growing faster. That doesn't seem to be the case in public sector. It seems like the public sector business is is really right there from in terms of growth. So it really is a shining star inside of AWS. >>Still, speed is a startup game, and agility has been a dev ops ethos. You couldn't see more obvious example in public sector where speed is critical. What's your reaction to your interviews and your conversations and your observations? A keynote? >>Yeah, I mean something We've all been saying in the technology industry is Just imagine if this had happened under 15 years ago, where we would be So where in a couple of the interviews you mentioned, I've talked to some of the non profits and researchers working on covert 19. So the cloud really has been in the spotlight. Can I react? Bask scale. Can I share information fast while still maintaining the proper regulations that are needed in the security so that, you know, the cloud has been reacting fast when you talk about the financial resource is, it's really nice to see Amazon in some of these instances has been donating compute occasional resource is and the like, so that you know, critical universities that are looking at this when researchers get what they need and not have to worry about budgets, other agencies, if you talk about contact centers, are often they will get emergency funding where they have a way to be able to get that to scale, since they weren't necessarily planning for these expenses. So you know what we've been seeing is that Cloud really has had the stress test with everything that's been going on here, and it's reacting, so it's good to see that you know, the promise of cloud is meeting that scale for the most part, Amazon doing a really good job here and you know, their customers just, you know, feel The partnership with Amazon is what I've heard loud and clear. >>Well, Dave, one of these I want to get your reaction on because Amazon you can almost see what's going on with them. They don't want to do their own horn because they're the winners on the pandemic. They are doing financially well, their services. All the things that they do scale their their their position, too. Take advantage. Business wise of of the remote workers and the customers and agencies. They don't have the problems at scale that the customers have. So a lot of things going on here. These applications that have been in the i t world of public sector are old, outdated, antiquated, certainly summer modernize more than others. But clearly 80% of them need to be modernized. So when a pandemic hits like this, it becomes critical infrastructure. Because look at the look of the things unemployment checks, massive amount of filings going on. You got critical service from education remote workforces. >>these are >>all exposed. It's not just critical. Infrastructure is plumbing. It's The applications are critical. Legit problems need to be solved now. This is forcing an institutional mindset that's been there for years of, like, slow two. Gotta move fast. I mean, this is really your thoughts. >>Yeah. And well, well, with liquidity that the Fed put into the into the market, people had, You know, it's interesting when you look at, say, for instance, take a traditional infrastructure provider like an HP era Dell. Very clearly, their on Prem business deteriorated in the last 100 days. But you know HP Q and, well, HBO, you had some some supply chain problem. But Dell big uptick in this laptop business like Amazon doesn't have that problem. In fact, CEOs have told me I couldn't get a server into my data center was too much of a hassle to get too much time. It didn't have the people. So I just spun up instances on AWS at the same time. You know, Amazon's VD I business who has workspaces business, you know, no doubt, you know, saw an uptick from this. So it's got that broad portfolio, and I think you know, people ask. Okay, what remains permanent? Uh, and I just don't see this This productivity boom that we're now finally getting from work from home pivoting back Teoh, go into the office and it calls into question Stu, when If nobody is in the corporate office, you know the VP ends, you know, the Internet becomes the new private network. >>It's to start ups moving fast. The change has been in the past two months has been, like, two years. Huge challenges. >>Yeah, John, it's an interesting point. So, you know, when cloud first started, it was about developers. It was about smaller companies that the ones that were born in the cloud on The real opportunity we've been seeing in the last few months is, you know, large organizations. You talk about public sector, there's non profits. There's government agencies. They're not the ones that you necessarily think of as moving fast. A David just pointing out Also, many of these changes that we're putting into place are going to be with us for a while. So not only remote work, but you talk about telehealth and telemedicine. These type of things, you know, have been on our doorstep for many years, but this has been a forcing function toe. Have it be there. And while we will likely go back to kind of a hybrid world, I think we have accelerated what's going on. So you know, there is the silver lining in what's going on because, you know, Number one, we're not through this pandemic. And number two, you know, there's nothing saying that we might have another pandemic in the future. So if the technology can enable us to be more flexible, more distributed a xai I've heard online. People talk a lot. It's no longer work from home but really work from anywhere. So that's a promise we've had for a long time. And in every technology and vertical. There's a little bit of a reimagining on cloud, absolutely an enabler for thinking differently. >>John, I wonder if I could comment on that and maybe ask you a question. That's okay. I know your host. You don't mind. So, first of all, I think if you think about a framework for coming back, it's too said, You know, we're still not out of this thing yet, but if you look at three things how digital is an organization. How what's the feasibility of them actually doing physical distancing? And how essential is that business from a digital standpoint you have cloud. How digital are you? The government obviously, is a critical business. And so I think, you know, AWS, public Sector and other firms like that are in pretty good shape. And then there's just a lot of businesses that aren't essential that aren't digital, and those are gonna really, you know, see a deterioration. But you've been you've been interviewing a lot of people, John, in this event you've been watching for years. What's your take on AWS Public sector? >>Well, I'll give an answer that also wants to do away because he and I both talk to some of the guests and interview them. Had some conversations in the community is prep. But my take away looking at Amazon over the past, say, five or six years, um, a massive acceleration we saw coming in that match the commercial market on the enterprise side. So this almost blending of it's not just public sector anymore. It looks a lot like commercial cause, the the needs and the services and the APS have to be more agile. So you saw the same kind of questions in the same kind of crazy. It wasn't just a separate division or a separate industry sector. It has the same patterns as commercial. But I think to me my big takeaways, that Theresa Carlson hit this early on with Amazon, and that is they can do a lot of the heavy lifting things like fed ramp, which can cost a $1,000,000 for a company to go through. You going with Amazon? You onboard them? You're instantly. There's a fast track for you. It's less expensive, significantly less expensive. And next thing you know, you're selling to the government. If you're a start up or commercial business, that's a gold mine. I'm going with Amazon every time. Um, and the >>other >>thing is, is that the government has shifted. So now you have Covad 19 impact. That puts a huge premium on people who are already been setting up for digital transformation and or have been doing it. So those agencies and those stakeholders will be doing very, very well. And you know that Congress has got trillions of dollars day. We've covered this on the Cube. How much of that coverage is actually going for modernization of I T systems? Nothing. And, you know, one of things. Amazon saying. And rightfully so. Shannon Kellogg was pointing out. Congress needs to put some money aside for their own agencies because the citizens us, the taxpayers, we got to get the services. You got veterans, you've got unemployment. You've got these critical services that need to be turned on quicker. There's no money for that. So huge blind spot on the whole recovery bill. And then finally, I think that there's a huge entrepreneurial thinking that's going to be a public private partnership. Cal Poly, Other NASA JPL You're starting to see new applications, and this came out of my interviews on some of the ones I talked to. They're thinking differently, the doing things that have never been done before. And they're doing it in a clever, innovative way, and they're reinventing and delivering new things that are better. So everything's about okay. Modernize the old and make it better, and then think about something new and completely different and make it game changing. So to me, those were dynamics that are going on than seeing emerge, and it's coming out of the interviews. Loud and clear. Oh, my God, I never would have thought about that. You can only do that with Cloud Computing. A super computer in the Cloud Analytics at scale, Ocean Data from sale Drone using satellite over the top observation data. Oh, my God. Brilliant. Never possible before. So these are the new things that put the old guard in the Beltway bandits that check because they can't make up the old excuses. So I think Amazon and Microsoft, more than anyone else, can drive change fast. So whoever gets there first, well, we'll take most of the shares. So it's a huge shift and it's happening very fast more than ever before this year with Covert 19 and again, that's the the analysis. And Amazon is just trying to like, Okay, don't talk about us is we don't want to like we're over overtaking the world because outside and then look opportunistic. But the reality is we have the best solution. So >>what? They complain they don't want to be perceived as ambulance station. But to your point, the new work loads and new applications and the traditional enterprise folks they want to pay the cow path is really what they want to dio. And we're just now seeing a whole new set of applications and workloads emerging. What about the team you guys have been interviewing? A lot of people we've interviewed tons of people at AWS reinvent over the years. We know about Andy Jassy at all. You know, his his lieutenants, about the team in public sector. How do they compare, you know, relative to what we know about AWS and maybe even some of the competition. Where do you Where do you grade them? >>I give Amazon and, um, much stronger grade than Microsoft. Microsoft still has an old DNA. Um, you got something to tell them is bring some fresh brand there. I see the Jedi competition a lot of mud slinging there, and I think Microsoft clearly got in fear solution. So the whole stall tactic has worked, and we pointed out two years ago the number one goal of Jet I was for Amazon not to win. And Microsoft looks like they're gonna catch up, and we'll probably get that contract. And I don't think you're probably gonna win that out, right? I don't think Amazon is gonna win that back. We'll see. But still doesn't matter. Is gonna go multi cloud anyway. Um, Teresa Carlson has always had the right vision. The team is exceptional. Um, they're superb experience and their ecosystem partners Air second and NASA GPL Cal Poly. The list goes on and on, and they're attracting new talent. So you look at the benchmark new talent and unlimited capability again, they're providing the kinds of services. So if we wanted to sell the Cube virtual platform Dave, say the government to do do events, we did get fed ramp. We get all this approval process because Amazon customer, you can just skate right in and move up faster versus the slog of these certifications that everyone knows in every venture capitalists are. Investor knows it takes a lot of time. So to me, the team is awesome. I think that the best in the industry and they've got to balance the policy. I think that's gonna be a real big challenge. And it's complex with Amazon, you know, they own the post. You got the political climate and they're winning, right? They're doing well. And so they have an incentive to to be in there and shape policy. And I think the digital natives we are here. And I think it's a silent revolution going on where the young generation is like, Look at government served me better. And how can I get involved? So I think you're going to see new APS coming. We're gonna see a really, you know, integration of new blood coming into the public sector, young talent and new applications that might take >>you mentioned the political climate, of course. Pre Cove. It'll you heard this? All that we call it the Tech lash, right, The backlash into big tech. You wonder if that is going to now subside somewhat, but still is the point You're making it. Where would we be without without technology generally and big tech stepping up? Of course, now that you know who knows, right, Biden looks like he's, you know, in the catbird seat. But there's a lot of time left talking about Liz more on being the Treasury secretary. You know what she'll do? The big tech, but But nonetheless I think I think really it is time to look at big tech and look at the Tech for good, and you give them some points for that. Still, what do you think? >>Yeah, first of all, Dave, you know, in general, it felt like that tech lash has gone down a little bit when I look online. Facebook, of course, is still front and center about what they're doing and how they're reacting to the current state of what's happening around the country. Amazon, on the other hand, you know, a done mentioned, you know, they're absolutely winning in this, but there hasn't been, you know, too much push back if you talk culturally. There's a big difference between Amazon and AWS. There are some concerns around what Amazon is doing in their distribution facilities and the like. And, you know, there's been lots of spotlights set on that, um, but overall, there are questions. Should AWS and Amazon that they split. There's an interesting debate on that, Dave, you and I have had many conversations about that over the past couple of years, and it feels like it is coming more to a head on. And if it happens from a regulation standpoint, or would Amazon do it for business reason because, you know, one of Microsoft and Google's biggest attacks are, well, you don't want to put your infrastructure on AWS because Amazon, the parent company, is going to go after your business. I do want to pull in just one thread that John you and Dave were both talking about while today you know, Amazon's doing a good job of not trying todo ambulance case. What is different today than it was 10 or 20 years ago. It used to be that I t would do something and they didn't want to talk to their peers because that was their differentiation. But Amazon has done a good job of explaining that you don't want to have that undifferentiated heavy lifting. So now when an agency or a company find something that they really like from Amazon talking all their peers about it because they're like, Oh, you're using this Have you tried plugging in this other service or use this other piece of the ecosystem? So there is that flywheel effect from the cloud from customers. And of course, we've talked a lot about the flywheel of data, and one of the big takeaways from this show has been the ability for cloud to help unlock and get beyond those information silos for things like over 19 and beyond. >>Hey, John, if the government makes a ws spin out or Amazon spin out AWS, does that mean Microsoft and Google have to spin out their cloud businesses to? And, uh, you think that you think the Chinese government make Alibaba spin out its cloud business? >>Well, you know the thing about the Chinese and Facebook, I compare them together because this is where the tech lash problem comes in. The Chinese stolen local property, United States. That's well documented use as competitive advantage. Facebook stole all the notional property out of the humans in the world and broke democracy, Right? So the difference between those bad tech actors, um, is an Amazon and others is 11 enabling technology and one isn't Facebook really doesn't really enable anything. If you think about it, enables hate. It enables some friends to talk some emotional reactions, but the real societal benefit of historically if you look at society, things that we're enabling do well in free free societies. Closed systems don't work. So you got the country of China who's orchestrating all their actors to be state driven, have a competitive advantage that's subsidised. United States will never do that. I think it's a shame to break up any of the tech companies. So I'm against the tech lash breakup. I think we should get behind our American companies and do it in an open, transparent way. Think Amazon's clearly doing that? I think that's why Amazon's quiet is because they're not taking advantage of the system that do things faster and cheaper gets that's there. Ethos thinks benefits the consumer with If you think about it that way, and some will debate that, but in general Amazon's and enabling technology with cloud. So the benefits of the cloud for them to enable our far greater than the people taking advantage of it. So if I'm on agency trying to deliver unemployment checks, I'm benefiting the citizens at scale. Amazon takes a small portion of that fee, so when you have enabling technologies, that's how to me, The right capitalism model works Silicon Valley In the tech companies, they don't think this way. They think for profit, go big or go home and this has been an institutional thing with tech companies. They would have a policy team, and that's all they did. They didn't really do anything t impact society because it wasn't that big. Now, with networked economies, you're looking at something completely different to connected system. You can't handle dissidents differently is it's complex? The point is, the diverse team Facebook and Amazon is one's an enabling technology. AWS Facebook is just a walled garden portal. So you know, I mean, some tech is good, some text bad, and a lot of people just don't know the difference what we do. I would say that Amazon is not evil Amazon Web services particular because they enable people to do things. And I think the benefits far outweigh the criticisms. So >>anybody use AWS. Anybody can go in there and swipe the credit card and spin up compute storage AI database so they could sell the problems. >>The problems, whether it's covert problems on solving the unemployment checks going out, are serving veterans or getting people getting delivering services. Some entrepreneurs develop an app for that, right? So you know there's benefits, right? So this you know, there's not not Amazon saying Do it this way. They're saying, Here's this resource, do something creative and build something solve a problem. And that was the key message of the keynote. >>People get concerned about absolute power, you know, it's understandable. But if you know you start abusing absolute power, really, I've always believed the government should come in, >>but >>you know, the evidence of that is is pretty few and far between, so we'll see how this thing plays out. I mean, it's a very interesting dynamic. I point about why should. I don't understand why AWS, you know, gets all the microscopic discussion. But I've never heard anybody say that Microsoft should spend on Azure. I've never heard that. >>Well, the big secret is Azure is actually one of Amazon's biggest customers. That's another breaking analysis look into that we'll keep on making noted that Dave's do Thanks for coming to do great interviews. Love your conversations. Final words to I'll give you What's the big thing you took away from your conversations with your guests for this cube? Virtual coverage of public sector virtual summit >>so biggest take away from the users is being able to react to, you know, just ridiculously fast. You know it. Talk about something where you know I get a quote on Thursday on Friday and make a decision, and on Monday, on up and running this unparalleled that I wouldn't be able to do before. And if you talk about the response things like over nine, I mean enabling technology to be able to cut across organizations across countries and across domains. John, as you pointed out, that public private dynamic helping to make sure that you can react and get things done >>Awesome. We'll leave it there. Stew. Dave. Thanks for spending time to analyze the keynote. Also summarize the event. This is a does public sector virtual summit online Couldn't be face to face. Of course. We bring the Cube virtual coverage as well as content and our platform for people to consume. Go the cube dot net check it out and keep engaging. Hit us up on Twitter if any questions hit us up. Thanks for watching. >>Yeah, yeah, yeah, yeah, yeah, yeah

>>from the Cube Studios in Palo Alto and Boston connecting with thought leaders all around the world. This is a cube conversation. Hi, I'm stupid, man. And welcome to a cube conversation. I'm coming to you from our Boston area studio, and we're gonna be talking about the networking giant. So, uh, joining me is the first time on the program some of the members been on and the cover launch of Pensando so vivid Jane, his CTO and co founder of Pensando Bipin thanks so much for joining us. >>Thank you. It was very nice talking to you. >>All right, so in a big theme we've been talking about for a number of years now is multi cloud. And, you know, I go back and think about you know, that the concept of cloud and even, you know, I've been around long enough You think about the and one of the challenges you look at is well, security is always a challenge. The other things network bandwidth is not infinite. The speed of light has not been solved, though you know, help us understand is you know the first I guess give our audience a little bit of your background. As I said, anybody in the networking world knows less team, though. Tell us, you know, have you been on the journey with them for all of that? Or And you know what brought you and Sandy? >>Yes. Yes. Um, I mean, I've been in the journey with the team since 2000 and six, so it's pretty long, I would say 14 years now, and it's been tremendous. Um uh, at heart, I'm an engineer who takes, you know, Brian brilliant things and taking upon challenges. And I've got multiple startups before this been in a new era, The more startups before that. And of course, you know, they were not experience more independent startups. And, you know, all through the course, I have gained appreciation for, like, you know, starting all the way from silicon to build a distributed systems and a u io all the way up to the fully consumable, you know, system. So I I totally understand the the angle I need to look at this time in a holistic manner. Having contributed to Cisco, UCS of and Nexus products on. Before joining pensando, I was, um I was contributing with my own open source container networking project, which is quite exciting to see How do you evangelize, You know, my own my own core, and that was fun. And that's where I come from, But, uh, but I I'm I'm a software engineer. To start off it started contributing to a six, then started going into the application world with containers trying to pull a container networking with, Ah, we did a server product with Cisco UCS and on and pretty much all over the stack with respect, participation. So that's my background. Um, but it's being exciting to consider what's next for me. And I was largely trying to see >>so, so definitive, actually, if I If I could jump in there, right, you know, I think back the UCS it was, You know, some of those ways I gather virtualization had been around for quite a number of years at that point. But, you know, how do you optimize it you're in. How do you transform infrastructure toe live for those environments, though? You know, UCS, You know, remember, people get back saying, you know, Cisco getting into services like Well, they are. They are because they're changing that compute model really caught that. You know, Cisco led that way. If the urge instructor, so many things you talked about that we'll get to later in the interview open for station. When I look out today, you know infrastructure's paint a lot and cloud obviously, is a huge impact, but also the application. So help us understand kind of the the waves that were writing together And, you know, what was it that you know in Santo decided to build in order to meet what you know, the customers of a require >>Um So I think, you know, going back to the UCS common that you had We started off thinking, for example, what are what were the challenges with respect is scaling out the deployment of servers and we quickly realized that manageability is number one challenge on. And of course, you know when we speak about manageability, it comes down to the underpinnings of what you're building. Are you Are you able to see the entire infrastructure together, or are you still seeing those big pieces? And that's when I think UCS was born to say that Look, we need to bring everything together that could be consumed in a holistic manner. And for that you have to have all those components there are There are somewhat independent to be consumed as a unified thing. And which is why I think it was a unified computing system. UCS. Um and then I think, you know, and Sanders a journey that takes it to probably not just that concept, but in general, the the challenges and the disruptions that we're seeing to the next level. So, I mean, just to summarize, I would say we started off looking at all the disruptions that are happening in the industry. And there are many of those I'm happy to talk about, which means we looked at, uh and then we looked at What are the consumption models that people are largely, you know, finding it very appealing these days because the days in which you're going to write a spirit to do something is still pretty old you want to be able to consume and most this after consumable way, How can we build, you know, how can you build systems that are programmable in the field? Those kind of things? The consumption model reliability software is the friendly factor there, and highly appealing to you guys and all their last one. You know, at least we also we also wanted to be really heard in the game, competitiveness wise. So those were like the the overarching set of things there that we started to think about, like, what descriptions are we going to solve, um, and how the consumption model needs to be for or ah, for the future of infrastructure. And how can we get that key, which is which is far ahead and better than anything that exists out there? So that's where we started to look at. Let's bring something which is bigger B sphere and and something. Even if we have the possibility of feeling it. Let's go ahead and they're doing their anything. >>Yeah, and absolutely. There's been so much discussion over the last decade or so about about software's eating the world and what's going on there yet you know, your your team mates. It's a lot of times it's been the chip set. There have been some huge ripples in the industry, you know, major acquisitions by some of the big, disruptive companies out there. Apple made a silicon acquisition, you know, everybody paid and that will have. You can't talk about disruption today without talking about Amazon. And, of course, when Amazon bought Annapurna Labs, you know, those of us looking at the Enterprise and the clouds base was like, Keep an eye on this. And absolutely, it's been something over the last year or so now, where we've seen Amazon roll things out and, of course, a critical component of what Amazon's doing from outposts. So with that as the stage there, you talked about wanting to be interesting leading, you know Amazon, you know, is really sick, and it's setting the bar that everyone is measured against. And when I look at the solution pensando, the kind of best comparable analogy that we've seen is, you know, look at what Nitro chip can do. This is an alternative for all of the other 1000 for customers that might not want to get them from Amazon. Is that a fair comparison? And how would you line up what founder is doing compared to what Amazon has done there? >>Um, so you know, what you've seen in the Amazon announcement really is possible. Amazon is a great benchmark to beat eso No make mistakes. We are very happy to say that, you know, we are We are doing by comfortably so But then, you know, Amazon is more than more than just the just the chips that are that they are building. I mean, what you consume is what they're building and underneath the engines are really part up by by the nicety off all these things that they're very, um, having said that, you know, And Sandra was consisting off both the you know, it's recognized us as a team which has been in traditionally building chips. But yet I think you know, the the Iot or the the previous venture from Mpls Team was somewhat of an eye opening as to how bringing things together is much more value in op, ex and and simplifying things is a huge, huge value compared to just putting performance and those things. So why this is important? That is another aspect which is important in trying to simplify things and make it consumable like software. And Sandra itself has probably, you know, I would say, Ah, good chunk, like about 60% of people in software team and not the, you know, basic harbor t This is not to say that, you know, we, you know, we are under emphasizing one versus the other. Software is a bigger beast when you start trying to build all those programs on a programmable and doing that here and start to roll out those applications on. So that's why I think the emphasis on software is there. Having said that, you know, it's the software that runs the data path pipeline. There's also a layer of software that we're building that can help manage all you know, all the product in a more cohesive manner and unified. >>Okay, that's Ah, thank you for laying that out. You mentioned you've got some background and open for definitely an area where, for a number of years, you know, Amazon has not exactly, uh, open source. Not exactly been a strength for AWS. They have put a lot of effort. They've done some president IRS over the last couple of years. >>And >>how do you see open source fitting into the space? What is I kind of the philosophy of pensando when it comes to open source. And where do you see it playing in the You know, this network piece of the multi cloud. >>Yeah, no, I think it's It's ah, it's a squared, relevant in a way that you know of the cloud native movement on how applications with very Onda normalization of AP eyes across multiple clouds. Israel, We are all seeing the benefits offered. And I think that that trend will continue and which is all driven through open source Ah, you know, community that exist in, you know, in the heart of the word. So personally for me, I think I learned a whole lot of things in the open source community. You know, the importance off evangelizing whatever you're working on, the reason to have convinced other people about contributing into what you're working on on. Frankly, I also learned how difficult it is to make revenues in an open source based part of that strategy. So I think you know that those were the things that I got away from it when I was doing my own open source project of container networking. Um, but at the same time, pensando, uh, you know, we have to make sure that we are 100% aligned with anything that's happening in open source. Never replicated, Um, anything that might be that might be happening in open source instead tried to make people use those things in the best possible way and in the most efficient way and the easiest possible way to use those. So our strategy largely is that, you know, embrace open source which exists are there from an infrastructure point of view, we are collaborating and communicating with less of the users are Hello. I think we're going to standardize most of things we're looking in before community. So our stands largely is that, you know, if we are building a programmable platform than the community is what is gonna driver and we are very much working towards a step by step, of course, trying to get through, you know, a stable state where we could we could not just empower people who are who are taking up the open source efforts which are going on. But at the same time, we can also contribute our program are programs into the open source community and defining the right abstractions into into the community. Um, because we came out of stealth pretty recently, you'll start seeing that and helping those activity as Well, >>excellent. Well, you know the launch of Pensando you had a phenomenal lineup. Not only you know, John Chambers obviously has the relationship with your theme, but you know, oh, am partners of Hewlett Packard, Enterprise and IBM, as well as the Marquis of Goldman Sachs. Things look a little bit different in the first half of 2020 and then they didn't end of 29 teams. So, you know, curious, You know that the global pandemic, the rippling financial implications, you know, what does that mean? The pensando. How has that impacted conversations that you're having with your >>Well, one thing I know at a broader level, let me cover, um, where things are heading. And in that sense, you know, I see that network and the infrastructure in general cloud infrastructure networking it's going to become. And we have realized it's this during during during recent early 20 twenties that that is going to be very important to have the have a new underpinning infrastructure that is not just working efficiently, securely, but is, you know, highly cost effective and very high performance, you know, ranging from people who are trying to connect from home to people who are trying to use videoconferencing and people who are going to be more and more use cloud based services even to order simple of the data being, you know, going to source for so network will become essential, you know, essential element for four things as we go forward. And we do see that being embraced by our customers and and things where we were trying to communicate that, you know, look, you will need performance and cost benefits are becoming more and more real Now. It's like, oh, things that we were having things in the pipeline for us. We need to work on that now. And the reason is because the things that we anticipated the demand increase, which is gonna happen over the fear of years, is happening literally in a few months. And so that is what we see. We are definitely, you know, very well poised to take advantage of their of their demand for sure. But also the fact that you know it needs to be done super efficiently. And so I think we are. You know, we are right. Well, I would say, you know, situated to be able to take advantage of start. >>Yeah, absolutely. You know, one thing you can't control as a company is you know what the global situation is when you come out of stealth and, you know, move through some of those early phases, you know, you've been part of You said a number of startups you've been part of been in give us a little bit of the inside baseball of, you know, being part of Rondo. You know, any stories on a little some of the ups and downs on the multi year journey to get where you are today? >>Definitely. I think. You know, um, minutes aren't good. They are largely an execution play. Relatively independent startup is is going to be about you know, how we cracked the overall market market fit and, ah, on execution, Of course, on deal with maybe in a competition in a different way, of course, like maybe big companies are our great partners. At the same time, you have to navigate that. So the overall the overall landscape in Spain and forces forces not is it's quite different. We can be much more border than we are independent company In trying to disrupt almost anything because we don't have any point of view to define per se. We do exactly, You know, what could be the most disruptive way, too, to potentially benefit the users on day? That's a big, you know, big change. I would say, um, we are being but paranoid as well at the same time, impractical to look at. You know how how we could navigate this situation in a very practical may. And the journey off, often independent startup is, you know, personally, for me, this is this is my fourth in different and start and best off. Off off, all independent. Once, I would stay largely because the kind of tradition that we're getting being an independent company is so huge. I'm just concerned about those things. But what We're really trying to trying to ensure that, you know, we can't get our stuff, but I want you and we started. >>Excellent. Guess what? One of the other things about being a startup is You know what you know adjustments You need to make along the way. So I'm curious. As you know, you've gone to some of your early customers. Any feedback or adjustments in some of the use cases or, you know, things that you've learned along the way that you can share. >>Um, fundamentally, at a base level, we haven't shifted from what we started off. We look at disruptions on on how consumption models are going to be changing, how speeds and feeds are gonna become important because, you know, because most law is going to be almost operating, how we how we deliver things into and containers are going to be a primary, you know, vehicle to deliver and build applications. So we recognize those disruptions, and we haven't changed, But normally from those disruptions that we wanted people after her. Uh, but at the same time, I think, you know, as we went and socialize our ideas and on architecture and designs with customers, we realized that that they are giving us lots more feedback on work all we could do and ah, and starting to become like we could take on different segments of market and not just one. So why stick ourselves to the data center power? Why not work on something on edge, blur wine or wine are real solutions for five G where latency and and performance is super crucial. Why don't take up on, you know, branch that use cases. So there are many things that are opening up. Um, and largely the you know, the shift. Or I would say the the inclination of what we should change versus not is happening with respect to where our customers are driving us. And and it is very important to make sure that you know the users of our lives Articulating all of the shift happens as opposed to, uh, you know, as opposed to anything else. We listen to them like super, super carefully, uh, and at the same time trying to make sure that we not only meet their means for you there their demands. So, um, definitely, you know, from the from the overall landscape of things, we are starting to get a lot more than what we are capture, which is good news For the same time, we're trying to also, uh, take on one part. I'm you know, >>all right, Vivienne, I can't let you off the hook as the cto without talking a little bit about that. You know, I think earlier in my career there was the old discussion and said you know, we should have started it, you know, a year or two ago. But, you know, we didn't. So we should start it today with changing pace of technology. You know, I've always said, you know, if I could I'd rather wait a year because I could take the next generation. I can take advantage of all these other things, but I can't wait, because then I'd never ship any things that I need to start now, Give us a little bit, you know, Look out in the future. How is your architecture designed to be able to take advantage of all the wonders coming with five G and everything there, Um, and anything that we should be looking at, You know, through the next kind of 12 18 months on the roadmap that you could share >>your Ah, yes. So, um, I would first of all say that we didn't build a part of, actually, what we build was a platform on which we can build multiple products. And we started we started off going there because we thought that, you know, the the platform that we're building is capable of capable of doing a lot more things than than one use case that we start off with. And so, to that point, I would say that yes. I mean, he started focusing on one product initially on the possibilities off. Trying to take it to multiple segments is is normally very much there. But we are already, you know, having those conversations to see what is the core set of use cases that we could we could get into for different segments. Besides the data center, you know, public Private Data center, you're looking at edge. We're looking by the looking at, Yeah, you mentioned this is as well as the, you know, storage and conversion infrastructure. So I would say that the food of all those things that we're starting to engage is going to start showing up in next 18 months. I could actually I think we are very well boys to take advantage of what we have. The hardware that we're shipping is going to be 100% compatible with four programs, but I don't those. So that is that is lot more possibilities are interesting. More use cases as people. The software's architecture that we have built is very extensible as well. Eh so we believe that. You know, uh, we believe that we can normally satisfy those use cases, but we're starting to you get into those things now, which will start to show up in and actually useful products of unusable for us with customer testimonials and then maybe 12 to 18 months from now. All >>right, well, thank you so much. It's great to catch up with. You really appreciate you coming on. >>Thank you to Because they're talking to you. And, you know, I appreciate your time. >>All right, I'm stew minimum. And be sure to check out the cube dot net for all the coverage. Go see the launch that we did. So in the second half of 2019. Thank you for watching you. Yeah, Yeah, yeah, yeah.

>>from the Cube >>Studios in Palo Alto and Boston connecting with thought leaders all around the world. This is a cube conversation. >>I am stupid, man. And welcome to a cube conversation. Really? Please welcome back to the program. One of our Cube alumni, Sony, Ge and Donnie. She is a co founder and also the business off of pensando. Tony, thanks so much for joining us. >>I thank you for having me here. >>All right. So, Sonny, we've had you on the program a few times. You know, those that have watched the program or followed your career? You've had a story career. You know, I've worked with you as a partner back through some of the spinning disk. You're one of the mpls group. And now, of course, Pensando we helped launch towards the end of 2019. I just want to take a step back and, you know, understand, You know, how did you find yourself in the startup world? >>You know, I got involved with startup ventures as part of the Mpls team. This is going back now. Gosh, 20 years ago, in calendar year 2000 my first venture was with Andy ammo. It was a very unique situation that Mario look up on myself or part of a set up on a startup venture. But all four of us, the Mpls group, did not have any equity in it. Look, and I basically what asked to operate within the with that venture to ensure its ultimate success from a product execution on the go to market perspective? Ah, lot of those elements did not exist from a go to market perspective in Cisco at that time, and it was basically a ground up effort for look and me to not have any financial association with the outcome off the Andy, um, a venture, but at the same time, take on the responsibility from the execution perspective and building up the whole go to market. >>Yeah, so, you know, talking about that these startups, you've been apart of two things. First of all, you were part of and, ya know, you ova in CNI. So did you need to learn Italian to be part of these projects? But more importantly, how did how did you work on that? You know, product customer fit, understanding what the build and, you know, you talk about right How do you make some things that festival? It is super challenging. >>Yeah, well, first and foremost, I think I've been fortunate in that the group that we're all part off it is definitely Italian Indian. And some folks, like from Indiana, for example, like Randy Pond, who is part of this venture with us at Pensando. If I if I would go back and take a look at the simple formula, I mean Mario look, and from, ah, they're veterans in this industry. And they typically focused on the conceiving off the idea and the brought up, uh, and starting with a clean slate approach. Of course, I participate from a market validation development, competitive landscape on a business on all related aspects, bringing the product to market on how that maps into customers and partners what we have consistently focused on market disruption. Particularly for the last two decades, the biggest focus has been on what are the market transitions occurring both from a business and a technology perspective on that is ultimately what creates the opportunity to emerge on and drive these concepts into reality and what yourself, in a market leadership position, is to capture the transition at the right time. >>Yeah, I think back. You know, some of your previous ventures and understand, you know, some of the waves of technologies coming together sometimes the maturity of a technology or being able to take advantage of something new to talk specifically about. Pensando what are you know, those waves of change and the technology coming together that makes the opportunity that you're in today? >>Well, I mean, if you go back and you take a look at really what has been exciting about this pensando opportunity has been to look at the unique ability that have been coming upon us. You know, with this market transition where the cloud is moving to the edge, what is ultimately driving this movement to the edge has been the application. Uh, the applications is is you know, whether it's driven by technology trends like five G, for example. Ah, and and the fact that bulk off what the customer's data is being driven is going to be at the edge. That when when you look at the cloud moving to the edge and evolving that with the transitions occurring, ah, this will require deep innovation. Deep innovation in the areas of distributed network processing security, like encryption, full observe ability while you have turned on encryption, traffic engineering and doing it at very low, predictable agency at the speeds of 100 gig and above all, doing it on a small footprint. We were really the only guys and gals who could do this. And we have done it, >>Yeah, so certainly some really big challenges that they laid out there bring >>us inside >>a little bit. You know, customers. You know, I think about, you know, when I've been watching edge computing for the last three or four years. Uh, you know, it's still relatively early days for customers, but there's a lot of technical challenges there, So help us understand how much you know it was you had technology that could help solve something and how much it is driven by some of the customers that you've been talking to over the years >>Now. One of the key things that we learned and this was going back to the early days of Cisco is that everything we were doing, we had the customer at the center off and at the heart off what innovation we were building from an engineering perspective. You want to build things that can have the most impact in the marketplace and within your customer base. So, uh, one of the early times we went back, who do getting our customers involved in the innovations we were bringing to bear. I still have recollections off a blueprint that we had iterated upon, uh, and sitting in a room, whether it was with the likes of Josh Matthew at Goldman Sachs all whether it was with some of our early cloud customers like the Oracle Cloud, to better understand with these innovation and these blueprints, what were their burning problems? What were they used, cases that we could really go and tackle? So it is one thing to think about market destructions. It's another to bring it to life and having customers engaged with you during the early phases. Off as you are incubating, something is a very important item because it helps you focus your biggest energy on the areas so that you can put your arms around what problems are worth solving. And how can you bring that to life with with customers? Use case. And this is something we have done time and over again. So this is a constant refinement off what we have been doing now for now, to over two decades. As I said, >>Yeah, it's, you know, fascinating here. And when you've got the chief business officer idle, Sony, You know, one of the biggest changes, obviously, is if I look back in the spin ins, you kind of understood how to go to market was what was involved the, you know, the Cisco execution machine that the sales process that they had in plug in a product, that they would help. All right, what you're doing now, you've got some, you know, feel, William partnerships. You have relationship with customers, help us understand a little bit. You know the update on the go to market, how you have. I have a solution that fits for not only the end users, but through multiple different, uh, you know, go to market partners. >>So I think it's, you know, it's very important that as a startup we stay very close to our customers and apart, not just men. We are thinking about what the innovation is and how can it solve their problems. But I think in a world where the way we want to go solve for what? The customer where we want the customer, where our customers want us to be our partnerships is a core part of it. I mean, if you look at from the early days we secured successfully funding from our customers and our strategic partners and it is these customers and strategic partners that are shaping the roadmap on are shaping the routes to market on. What we're doing is we're successfully not only delivering the product, so these strategic customers and partners, but we're also then replicating it across the verticals. If you think about in the enterprise space, our focus has been the focus on regulated market markets where security is essential. Real time, observe ability that can increase your security posture is a very important element. So taking the blueprints that we're taking into global financial services customers, the healthcare industry, the the education market on the federal market, then those are the industries that really care about, and I in regulated markets where we can take the blueprint that we have already built on an amplify across those customers. So there again includes alignment and a partnership with HP. We're working very closely that, while recognizing that we will be doing strategic elements only with partners like HP, we're also on boarding and getting certifications done with Dell because most enterprises have at least dual source vendors from a server, so that that is one aspect. The other aspect is working in a high touch model with the cloud customers and having the opportunity to deliver to them Ah, and onboard them from a production worthy perspective while taking that same blueprint and applying it to other cloud customers and other service provider edge providers that can take advantage of the similar capability. >>Yeah, um, I'm curious. Sony, you know, obviously, the cloud is a space that has been going through a lot of change and accelerating. You know, I'd say much faster than traditional networking did. So you know, curious what you see what you're hearing from customers when they talk about you know, their needs for your solution, what they're doing with multi cloud environment. What is that? That landscape you. And I guess we would love to hear a little bit about how you would compare and contrast yourself. The other solutions out there the one that comes to mind, of course, is you know, eight of us what they're doing with the Annapurna chip in there nitro offering as part of their out. >>You know, as I mentioned earlier, I think the cloud is pushing to the edge. There's a high demand for a lot of packet processing needs with these New Age applications. Customers want to build on and give the you know, we want to be in a position to provide through the democratization and open availability off our products to multiple cloud providers, our technology and as they are experiencing tremendous growth, they're seeking to build cloud with more capacity, with greater degree off security and services functionality. And the ability to process a lot of data at the edge is with millions of simultaneous connections happening at a very small footprint. And that's where we come in. The value that we are essentially providing who not only the existing cloud strategic partners but additional cloud customers we're taking into production this year is that we are enabling them to leapfrog the nitro technology on multiple, whether it is the ability to ah have predictably low latency on and consistently low jitter in the nanoseconds. That is the eight times superior than what a nitro can do today, or the ability to pack their toe process up to nine times more backend processes in the millions of on the ability to do it in a power footprint, which is almost 1/3 that of what you would need on AWS nitro, where they need five times more nitro elements than then we can with a single device, Um, or whether it is the ability now to handle not just power and latency, but millions off flows that can run simultaneously on maintaining the state of all of those and the power of the end, the ability to run multiple services. Uh, with security turned on at the same time are all elements that really differentiate us on. This technology is now readily available to all of us. >>All right, so I understand some of the technical issue items that you're stating there. What I'm curious about is when I look at out both, most customers don't really think about the night. It's that Amazon's providing an extension of their solution into my environment, and they manage everything and so you know, you can't talk about multi cloud environment without talking about Amazon is every customer almost everything right? More than one cloud in one of them is almost always Amazon, though. How does your solution fit into that whole discussion? And then? >>So I think that, you know, one of the things that becomes very important is that if I put my customer enterprise customer hat on, I want to be an enabling my private cloud the private cloud that I build. You have the ability to not just have the option to the port and Amazon cloud, but I typically already and minimal child and barn. So while Outpost and Nitro Nitrogen really enabling, are supposed to deliver those services on our customer's premises, it's only allowing that customer to be locked into one way off dealing with one public cloud company. But if I had to go and think about as I build out my hybrid cloud strategy as an enterprise customer, I want to have the same building blocks on the same policy models that are consistent with all the with the entire dress off cloud vendors that I'm dealing with. The bulk of our customers are essentially telling us I don't want to be locked into a single public cloud company from a hybrid strategy. I want to have the ability to drive a public, private cloud architect that is cloud like from a policy delivery perspective. But at the same time, I want to have the flexibility off deploying a multi cloud and BART, and what we would provide them is the consistency off that same policy model that you would only find in a public cloud with the freedom to not have to buy themselves or lock themselves up into a single public cloud costs. >>So your team, you said, over two decades of experience, there have been some global impacts that have happened during that you got together in 2000. 2001 was right there in front of you that the 2008 you know, down in there, though you're in 2020 obviously the global endemic, as you know, broad financial ripples. How's this impacting Dondo? How's that impacting your discussions with your partners and your customers? >>Well, you know, honestly, I would say that we, like everyone else, have been affected by the pandemic, and we pray that everyone recovers soon with minimum lost to themselves and their families. And this is something very personal. This is here. I feel very passionate about hoping that everybody comes through with this on and their families are all OK. That's all the most important thing in my mind now for us, from a pandemic perspective. What this has done is it has made us more resolute to continue to execute remotely to the best of our ability to meet our customers. Expectations. The advice that I would give to other startups is Keep your head down. Focus on the 80 20 rule, execute on 20% of the things that need to be done, that we'll have 80% of the impact to your business, including undeterred product execution. Stay close to your customers and your partners. Spend your cash judiciously. You know, be very careful on where you're spending your money to make it last. As long as you can ride this pandemic out and double down on being close to your partners and customers. Fortify your sales plans. Meet your customers where they are not where you thought they were, but where they really are and partner with them on this journey and partner with your supply chain. You're going to need that. So this is your time to really be a partner to them, as opposed to see how can you change them? No, no. The really partner with your supply chain Because you're gonna need that. >>Yeah, that's a very sound advice there, Sony. While we're talking advice that, you know, you're very successful career, I'm wondering what advice you would give the other women look at pursuing careers. In fact, specifically, if you know they wanted, you know, start a startup, be a founder, whether that in Silicon Valley or outside, what advice would >>you know? My advice would be to have an undeterred focus. Focus is extremely important. Look, I used to always remind me, Sony, when you're focused on two things, you're d focus. So focus on data. Focus, be driven. Believe in the vision that you have set out for yourself and your team on and keep your eye on the customer. I think in customers successful on your success. That's the message I would give. I would give that same message. My female and the male colleagues. >>Alright, well, we know that you and your team. Sony are very focused, so I'll give you the final word. Gives a little look forward if we go forward. You know, 18 to 24 months. What should we be expecting to see from PENSANDO and your solution? >>Well, in the next 18 to 24 months, we would like to meet and hopefully also exceed our customer's expectation in terms of product execution and the ramp off course. Profitability will be a very important aspect that we're going to keep a very close eye. I think it's too early to be thinking of an ideal, and our focus remains to be on customer success. We have been in the market for a little over. I was a little less than six months. Ah, with the product, September 2019 October 2019 is really when we launched the company on and, uh, the customer always is at the center of everything we do. So that's where we're gonna be focusing on product execution and ramp ramp off product, ramp off estimates. >>Well, so needy. And Dani, it's a pleasure to catch up with you. Thank you so much in the state. >>Thank you. You too. >>Alright. Be sure to check out the cube dot net for all the interviews, you can go see the launch videos that did at go back office in New York City from 2019. If you go to the cube dot net and many more interviews from Sony and her team, I'm stew Minimum. And thank you for watching you. Yeah, yeah, yeah, yeah, yeah.

>> from Cambridge, Massachusetts. It's three Cube covering M I T. Chief data officer and information quality Symposium 2019. Brought to you by Silicon Angle Media. >> Welcome back. We're here to wrap up the M I T. Chief data officer officer, information quality. It's hashtag m i t CDO conference. You're watching the Cube. I'm David Dante, and Paul Gill is my co host. This is two days of coverage. We're wrapping up eyes. Our analysis of what's going on here, Paul, Let me let me kick it off. When we first started here, we talked about that are open. It was way saw the chief data officer role emerged from the back office, the information quality role. When in 2013 the CEO's that we talked to when we asked them what was their scope. We heard things like, Oh, it's very wide. Involves analytics, data science. Some CEOs even said Oh, yes, security is actually part of our purview because all the cyber data so very, very wide scope. Even in some cases, some of the digital initiatives were sort of being claimed. The studios were staking their claim. The reality was the CDO also emerged out of highly regulated industries financialservices healthcare government. And it really was this kind of wonky back office role. And so that's what my compliance, that's what it's become again. We're seeing that CEOs largely you're not involved in a lot of the emerging. Aye, aye initiatives. That's what we heard, sort of anecdotally talking to various folks At the same time. I feel as though the CDO role has been more fossilized than it was before. We used to ask, Is this role going to be around anymore? We had C I. Ose tell us that the CEO Rose was going to disappear, so you had both ends of the spectrum. But I feel as though that whatever it's called CDO Data's our chief analytics off officer, head of data, you know, analytics and governance. That role is here to stay, at least for for a fair amount of time and increasingly, issues of privacy and governance. And at least the periphery of security are gonna be supported by that CD a role. So that's kind of takeaway Number one. Let me get your thoughts. >> I think there's a maturity process going on here. What we saw really in 2016 through 2018 was, ah, sort of a celebration of the arrival of the CDO. And we're here, you know, we've got we've got power now we've got an agenda. And that was I mean, that was a natural outcome of all this growth and 90% of organizations putting sea Dios in place. I think what you're seeing now is a realization that Oh, my God, this is a mess. You know what I heard? This year was a lot less of this sort of crowing about the ascendance of sea Dios and Maura about We've got a big integration problem of big data cleansing problem, and we've got to get our hands down to the nitty gritty. And when you talk about, as you said, we had in here so much this year about strategic initiatives, about about artificial intelligence, about getting involved in digital business or customer experience transformation. What we heard this year was about cleaning up data, finding the data that you've got organizing it, applying meditator, too. It is getting in shape to do something with it. There's nothing wrong with that. I just think it's part of the natural maturation process. Organizations now have to go through Tiu to the dirty process of cleaning up this data before they can get to the next stage, which was a couple of three years out for most of >> the second. Big theme, of course. We heard this from the former head of analytics. That G s K on the opening keynote is the traditional methods have failed the the Enterprise Data Warehouse, and we've actually studied this a lot. You know, my analogy is often you snake swallowing a basketball, having to build cubes. E D W practitioners would always used to call it chasing the chips until we come up with a new chip. Oh, we need that because we gotta run faster because it's taking us hours and hours, weeks days to run these analytics. So that really was not an agile. It was a rear view mirror looking thing. And Sarbanes Oxley saved the E. D. W. Business because reporting became part of compliance thing perspective. The master data management piece we've heard. Do you consistently? We heard Mike Stone Breaker, who's obviously a technology visionary, was right on. It doesn't scale through this notion of duping. Everything just doesn't work and manually creating rules. It's just it's just not the right approach. This we also heard the top down data data enterprise data model doesn't works too complicated, can operationalize it. So what they do, they kick the can to governance. The Duke was kind of a sidecar, their big data that failed to live up to its promises. And so it's It's a big question as to whether or not a I will bring that level of automation we heard from KPMG. Certainly, Mike Stone breaker again said way heard this, uh, a cz well, from Andy Palmer. They're using technology toe automate and scale that big number one data science problem, which is? They spend all their time wrangling data. We'll see if that if that actually lives up >> to his probable is something we did here today from several of our guests. Was about the promise of machine learning to automate this day to clean up process and as ah Mark Ramsay kick off the conference saying that all of these efforts to standardize data have failed in the past. This does look, He then showed how how G s K had used some of the tools that were represented here using machine learning to actually clean up the data at G S. K. So there is. And I heard today a lot of optimism from the people we talked to about the capability of Chris, for example, talking about the capability of machine learning to bring some order to solve this scale scale problem Because really organizing data creating enterprise data models is a scale problem, and the only way you can solve that it's with with automation, Mike Stone breaker is right on top of that. So there was optimism at this event. There was kind of an ooh, kind of, ah, a dismay at seeing all the data problems they have to clean up, but also promised that tools are on the way that could do that. >> Yeah, The reason I'm an optimist about this role is because data such a hard problem. And while there is a feeling of wow, this is really a challenge. There's a lot of smart people here who are up for the challenge and have the d n a for it. So the role, that whole 360 thing. We talked about the traditional methods, you know, kind of failing, and in the third piece that touched on, which is really bringing machine intelligence to the table. We haven't heard that as much at this event. It's now front and center. It's just another example of a I injecting itself into virtually every aspect every corner of the industry. And again, I often jokes. Same wine, new bottle. Our industry has a habit of doing that, but it's cyclical, but it is. But we seem to be making consistent progress. >> And the machine learning, I thought was interesting. Several very guest spoke to machine learning being applied to the plumbing projects right now to cleaning up data. Those are really self contained projects. You can manage those you can. You can determine out test outcomes. You can vet the quality of the of the algorithms. It's not like you're putting machine learning out there in front of the customer where it could potentially do some real damage. There. They're vetting their burning in machine, learning in a environment that they control. >> Right, So So, Amy, Two solid days here. I think that this this conference has really grown when we first started here is about 130 people, I think. And now it was 500 registrants. This'd year. I think 600 is the sort of the goal for next year. Moving venues. The Cube has been covering this all but one year since 2013. Hope to continue to do that. Paul was great working with you. Um, always great work. I hope we can, uh we could do more together. We heard the verdict is bringing back its conference. You put that together. So we had column. Mahoney, um, had the vertical rock stars on which was fun. Com Mahoney, Mike Stone breaker uh, Andy Palmer and Chris Lynch all kind of weighed in, which was great to get their perspectives kind of the days of MPP and how that's evolved improving on traditional relational database. And and now you're Stone breaker. Applying all these m i. Same thing with that scale with Chris Lynch. So it's fun to tow. Watch those guys all Boston based East Coast folks some news. We just saw the news hit President Trump holding up jet icon contractors is we've talked about. We've been following that story very closely and I've got some concerns over that. It's I think it's largely because he doesn't like Bezos in The Washington Post Post. Exactly. You know, here's this you know, America first. The Pentagon says they need this to be competitive with China >> and a I. >> There's maybe some you know, where there's smoke. There's fire there, so >> it's more important to stick in >> the eye. That's what it seems like. So we're watching that story very closely. I think it's I think it's a bad move for the executive branch to be involved in those type of decisions. But you know what I know? Well, anyway, Paul awesome working with you guys. Thanks. And to appreciate you flying out, Sal. Good job, Alex Mike. Great. Already wrapping up. So thank you for watching. Go to silicon angle dot com for all the news. Youtube dot com slash silicon angles where we house our playlist. But the cube dot net is the main site where we have all the events. It will show you what's coming up next. We've got a bunch of stuff going on straight through the summer. And then, of course, VM World is the big kickoff for the fall season. Goto wicked bond dot com for all the research. We're out. Thanks for watching Dave. A lot day for Paul Gillon will see you next time.

>> from the Silicon Angle Media Office in Boston, Massachusetts. It's the cue. Now, here's your host. Day Volonte. >> Hi, >> everybody. Welcome to this cute conversation. I'm Dave Volonte and Stew Minuteman is here with me. We're gonna break down a w s kind of give you Ah, midyear What's happened so far this year with all the events that we've been covering and what to look forward to? Uh, the N Y C Summit is coming up stew. It's been a big year. Obviously. What we came off a re invent. Amazon's got $30,000,000,000 run rate business growing at 40 plus percent per year. That means they're putting 9,000,000,000 of incremental revenue every year into the cloud business. The marketplace, That growth that's roughly as large is tthe e entire Microsoft cloud business, which is astounding >> day that that that's that's the point Amazon definitely has been making for a couple of years. And you're absolutely right. Microsoft is definitely growing at a faster pace than Amazon, and they're running about 75 87 but off a much smaller number. So the incremental add that Amazon has been throwing off the last couple years. Every year they're adding more than an azure every year. So absolutely Amazon, you know, is the lead horse out there. And while you know, the horses on the track behind them are trying fast to catch up Amazon. If you talk about Infrastructures service, AWS is still the lead. >> Well, the big question is. Will that attenuate? And we were at Remember the Nutanix inaugural Nutanix Stop next? Do you rush Pandey, who's very smart guy, somebody we respect a lot. One of the fundamental assumptions they were making is eventually the law of large numbers will catch up to them and know it very well May. But it hasn't yet. I asked John Lovelock, can a company the size of Amazon $30,000,000,000 company grow it for 42% a year? Is that sustainable? And he said, Absolutely. There's nothing to stop them now. Who knows who has the crystal ball? What are your thoughts? >> Yeah, So, Dave, what we saw is Amazon's not sitting still. You know, they always like to say it's always Day one, and if you look at where they're going, the products that they keep throwing off the innovation that they keep moving on and the flywheel that they've had first of customer acquisition with all of the innovations that they're putting out there and the flight well. But I've been talking about the last couple of years the label of data, which is something we want to be a little concerned about. How much data Amazon actually does have both Amazon AWS and Amazon, with all those intelligent devices that are in your homes and connecting everything together. Some people are a little concerned about that. The government's a little bit concerned about that, but absolutely Amazon is going everywhere. We've seen Amazon going into sub segments of the market, going into verticals and going just really broad, really deep. So absolutely I don't see anything slowing a bit on down. It is a company that continues to impress one of >> the challenges. I think those do that that Amazon does have, and this came out of the reinforced >> conference a couple weeks ago in Boston, which was, Ah, conference for security practitioners, a lot of si SOS chief information security officers. The number one challenge that came out of that when you talk to practitioners was their ability to keep up with the innovations that Amazon is putting forth. So, you know, I wonder if we're gonna talk to some commercial customers. You'll see them down the summit probe to see if, in fact, that's part of their challenge. Just the pace at which Amazon brings out new features. But we've done Gosh, we've covered eight events or will have covered eight events this year. Eight productions. It started in the U. K. Where we covered a public sector health care. And then we did the AWS summit London really all about both public sector in the UK as well as the summit in the UK Innovations in the UK around cloud, etcetera, cloud adoption. 12,000 people at the AWS London summit. Now you covered re Mars, which was not the Cube wasn't there, but you were there. What was that show? >> Yes. So, first of all, it's an Amazon >> show, not a native US show, but absolutely showed underneath where eight of us fits into the fulfillment centers of Amazon. And it was about re Marceau Mars A play of course on space. But it was a machine learning automation, robotics in space. So you had the cool blue origin stuff that actually brought in. Robert Downey Jr talked about how he's going to save the planet with, you know, robotics and intelligence out there to help clean up pollution in the globe on and the like. But it was a phenomenal show, but what I said is actually going to show a little bit underneath the covers of Amazon similar what we've seen from eight of us at the reinvent shows over the years. Because, you know, we all know how many boxes air coming to our, you know, our place of home every day and how fast that's going. And so this is what's happening underneath the robotics and machine learning a lot of those Air AWS Service's that are powering that. So it was a fascinating show, Dave and absolutely showed other relationship between Amazon, the parent company. Eight of us, all those cloud service is that helped feed the bigger business. >> Now, June, the Cube covered the D. C. Public sector summit. This is Teresa Carlson's gig. She's the host. Actually, Andy Jassy was there this time. He wasn't there last year when you and I recovering it. And of course, that's all about bringing cloud to public sector, not just federal but all public sector. It includes AH, non profit and education, which talk about in a minute. The big story. There is a jet. I we're talking about tens of billions of dollars going to ah, contract. Oracle, of course, is fighting it. It's going into the courts. I guess they've been a number of reviews or could won't give up its oracle. Amazon clearly is the front runner. Last I read, it was down to AWS and Microsoft, with AWS being the lead contender there. We'll see what happens. I think the decision is coming down this month, July 2019. But it's really again about bringing cloud innovations to public sector. Public sector tends to take things a little bit later than the commercial like. For instance, last year they announced the the VM wear on AWS was available, so you'll see those kinds of things come maybe a year later. But its again. Another big show there 12. 13,000 people there at the D. C Convention center. >> Yeah, Davey, when you talked about the critique of what's happening in Amazon as Amazon goes deeper into all of these verticals How do they help get that information to the user in a way that they need to run their businesses? So my co host for New York City's Cory Quinn was listen to his podcast this morning and he said, That's where Amazon's got dozens of blog's. They've got so many announcements, they haven't done a really good job, something we've seen many companies do. How do I get to you know that business roll and put it in, you know, verbal that they understand, as opposed to just >> Hey, we had 1000 new features >> come out this year and they're awesome. Then you should use everything s o. You know, that's something that, you know the industry as a whole needs to do better at an Amazon. Just in the nature of how fast they're moving is something that they should be able to do a better job. >> And Jennifer is also gonna be in New York City. And one of things he was stressing at reinforce was the marketplace. We had Dave McCann on the just rocketing. I think it was 100,000 census of security subscriptions. I think it was 1,000,000 subscriptions in total so just an amazing ah momentum in the marketplace. But reinforce was all about security. Deep dives on security, chief information, security officers. What came out of that show the big takeaway was was head of AWS is, uh, security. The chief information security officer, Schmidt said. This narrative in the industry that the sky is falling doesn't do anybody any good. Um, it's not productive. We should be more positive. The state of the cloud union is good, like the president of states is State of the Union is strong. Um, having said that, Amazon talks about the shared security model. The practitioners that we talked to said, Yeah, shared model Amazon's going to secure the the infrastructure of the storage, the compute of the database. We are responsible for our end, and it really is on us to make sure that we are secure. So again, back to that point about the pace of innovation that Amazon is putting forth is a challenge for people. AWS imagine is also going down. I think this week what's that you're >> so it's in Seattle and it's you mentioned the public Sector one in D. C, which is government agencies, nonprofits and education. So imagine is a subset of that. My understanding is the education, a nonprofit piece of that from when you and I were in D. C. Last year for the Public sector summit. It's It is impressive how deep Amazon is going into these spaces, the affinity they have. And really, you know how happy the customers are to be able to move fast. So, you know, when you think about nonprofits and think about education, innovation is not the first thing that usually comes to mind because budgets are tight and I don't have enough people. And usually you've got, you know, whatever's left over. But imagine is them. How do we move these forward? How do we You know, we know we need to help transform education. It's so important to train the next generation. So, you know, imagine there are some great stories that come out of that. Jeffrey loves getting those stories, helping us tell those stories through the Cube platform. And so it's the second year we're doing >> Yes, it would be covering that. And then, of course, reinvent will have two sets again that reinvent this year. The Super >> Bowl of our industry, >> right? Sure. Um, something's going on. So unfortunate incidents in Southern California. Big earthquakes, actually. Multiple earthquakes, Right? You had the physical earthquake, and then you had CO I, leonard going to the Clippers. But so I'm interested in sort of poking at this notion of ground stations. So at reinvent last year, Amazon announced on his own ground station, which essentially was ground station is a service. So if I understand it, one of the challenges okay, You launched the satellites, but you still need a ground station to collect the data and then uploaded and analyze it. That's what AWS is is partnering to put in infrastructure that allows you to essentially rent ground station infrastructure. So, you know, they worry about building it in securing it yourself. Because you think about it. It's got to be a secure location. You gotta have fencing. You got a physical security. You got to get the data in. You gotta upload it to the toe. Where we gonna upload it? So Amazon is basically building this service out, saying Don't worry about the ground station piece. Rent that from us, you know, swipe your credit card. Your ground station as a service, and then we'll ingest that data uploaded to the cloud and then apply all of the tooling that we have to allow you to analyze that data. So if you think about the earthquake of devastation, if you don't have a ground station there, you can, in theory, go to AWS and actually spin up a ground station in jest. You know, on the ground, you know, the ground truth as we like to sometimes talk about and actually get satellite imaging and telemetry in that region, you know, this comes into play things like forest fires and all kinds of of natural disaster. >> Dave, even at the remarks show, I attended a session where one of the Amazon partners was talking about not only just getting the satellite data down, but Justus. They have the snowball edge today, which is, you know, for you know, I ot or some remote sites, but some of these satellites are gonna have the compute and storage at in satellite themselves. So if you think about I'm gonna have these geosynchronous satellites. I'm gonna have all this connectivity. And if I could get a gigabit of Ethernet, you know, traffic going to the satellites and I could do the processing at the edge, which is now up in space. I can process that. And you know, that edge that we talked about get to hold another dimension, you know, off off the terra firma to be able to do those kind of analysis. As you said, earthquakes, you know, all the all the climate discussion that's going on, we should be able to have tap into even more. Resource is, and we'll have to rename Cloud if it even goes beyond the Earth. >> And then, um, outpost is the other story that we've been tracking, attracting a lot of stories, but but outpost is starting to ship in beta form. We've seen instances of >> so, so seeing >> it. We just did a little quick right up. >> I mean, Dave, you know, just a ripple went through the >> industry when they showed Hey, here's Iraq and what they're like. This is the exact same rack that we have in the Amazon data centers and why it's a little surprising because we're allowed to see inside the Amazon Data Center. So it's like, Okay, this is what they're computed awaited to 24 in tracking, supposed to a 19 in track. But that line between the public cloud and my on premises environment absolutely is blurring. So everybody wants to see where Amazon's going. They have the big partnership with VM, where Veum, where is already shipping the solution? That is the same software for that Veum wear on AWS in my data center. So, you know, I can have you know, the Dell hardware with the Veum where code or I can have the Amazon hardware with the VM where code coming later this year without post. So that line between public in private is absolutely blurring. And where to my applications live, You know that that future of how fast is eight of us continue to grow? Absolutely. There are applications and data and things that will stay in my own data center and under my control. But that line is definitely blurring. And there's gonna be some re architectures. It's definitely still gonna take a couple of years to sort some of these things out. But we're at some of those inflection points where we'll see some of >> us. So I wrote a post its upon wicked bond kind of analyzing that video, and there's some interesting things that are unique. There's certainly a lot of goodness in there. Not some of the things they talk about are completely unique. Thio, aws. But things like Nitro and their special virtual ization engine and their special chip on Do you want to get a look at that? You take a look at that video and thence to New York City Summit this week. Um, we mentioned some of the innovations that we've seen up to date this year. A lot of talk I'm sure about the marketplace. >> Yeah, I'm wondering if there'll be any ripples, Dave, because the 1/2 of a chick you, too, was supposed to be in New York City. And now it's not, doesn't mean they don't have a strong presence in New York City like London and believe it's somewhere around 12 to 15,000 people. When I went to New York City two years ago was quite impressive. It is a free show, which means if your customer you get in for free. If you're a partner, of course, you're still paying for everything that goes there. But the regional summits are quite impressive and a great way to get in touch with Amazon and all that they're doing. If you don't want to go to the Super Bowl itself, which is, you know, 50,000 plus now in Las Vegas towards the end of the year. >> Yeah, these air, like many reinvents and they're actually quite good. A lot of a lot of practitioner focused on you're gonna you're gonna see that New York City >> did what I always love about every Amazon show I go to. There are customers that are interested learning new things. How can you do better with what I'm doing? But also, how can I change what I'm doing? How can I move forward? So even if it's not adopting the latest and greatest from AWS, the entire ecosystem is going there to meet with those customers and talk about digital transformation? Modern workforce? All of these hot trends definitely play out. Ground zero is the AWS. >> Yeah, and this is by design. As I said before, the pace of innovation is a challenge for people. It's an adoption blocker and so Amazon wants to educate and share the knowledge so that they can get more adoption. OK, stew. Thanks very much. Good luck. This week. Check out silicon angle dot com For all the news, the cube dot net is where the videos will live and watch. Do on John Ferrier and Corey Quinn. Live and check out the cuban dot com for all the research. Thanks for watching Everybody Day, Volonte and Stupid Event. We'll see you next time.

>> Live from Washington D.C. It's theCUBE, covering the AWS Public Sector Summit 2018. Brought to you by Amazon Web Services, and its eco-system partners. (upbeat music) >> Welcome back to the nation's capitol. I'm Stu Miniman and you're watching theCUBE's coverage of AWS Public Sector Summit 2018. Joining me for the wrap-up of day one, John Furrier, Dave Vellante. So John, thanks for bringing us down. So you were here last year. We've interviewed Teresa Carlson a number of times at Reinvent, but we've got to start with you. Since you were here last year, watching this explode. I said, this reminds me of Reinvent three years ago, how big it is, 14,500 people, wow. >> Yeah, so you're right on. This is definitely a Reinvent kind of vibe, in a way to describe what happened with Amazon Reinvent, their annual conference which we were at the 2nd year, 2013, and have been every year. Reinvent got bigger every year, and just became more prominent, and the solutions scaled, the number of announcements, as we know Amazon today is packed, it's bigger than ever. The public sector market, which is defined as government, education, and global public sector countries like Bahrain and other countries, are really the target. They have unique requirements. So what's happening is that that market is being disrupted, and there's been similar moments in the public sector here in the United States, as well known. The fail of the website that Obama. You know, the health care sight was one. The government initiatives that have been going on. The government is not modern and people are frustrated. The IT workers are living in cages, they're strapped in. It's like, not good. The tooling's old, old client server, old vendors like Oracle and IBM and others that are trying to keep that business, and they're not modernizing. So, this modernization wave has hit the public sector across the board, and what's happening is they can actually build newer systems faster, and get lower cost, more efficiency, done faster. And this is disrupting not only their business model, but how they buy technology, the role of the supplier in that piece of the equation, and also just overall faster innovation. So, this is driving it. The shocker of all of it is the security conversation has been up leveled, meaning it's not a real issue. Certainly the security is a real issue, but in terms of a barrier that stops everything, that's not the case anymore. The CIA is really the most notable that came on and said the worst day in cloud security is better than anything we got working today. So that's a really interesting thing and the Department of Defense Jedi project is billions of dollars that would have gone to say, an Oracle, IBM, and all the incumbents, or, beltway bandits, as they've been called. Those days are over. So that to me is a really exciting thing for the country. But, Amazon is running the tables too. So again, this year, more of the same, bigger. Big agencies. Small partners and big, all riding the wave of growth. And, it's a new operating model, and again, we'll predict it here in theCUBE, as we always say, and then we'll be right again. This is going to be a special market for Amazon going forward. >> I think government market is definitely a microcosm of the overall marketplace as John said. It's very bureaucratic, they're slower to move, you got to regime change every four or eight years, so a lot of turnover. It's really hard to get. Okay, we're going to go with strategy, cause the strategy as they start stop, it's a near to mid term strategies are affected in the government. Obviously, there's a greater focus on security. Cloud addresses a lot of those. We certainly heard that from the CIA. I don't think you can talk about cloud and federal, without talking about that milestone CIA deal. That really was a watershed moment. It was a wake up call to the old guard. IBM, as you might recall, tried to fight the government, because the CIA awarded the contract to Amazon. IBM lost that case, they were eviscerated by the judge. It forced IBM to go out and pay two billion dollars for software. It was years later that Oracle really got in. So, Amazon, to an earlier guest's point, has a huge lead. The estimate was five to 10 years, I heard, over some of the legacy suppliers. Interesting, not sure exactly where Microsoft fits in there. Stu, I'd love to get your thoughts. The thing about cloud that we've, John, you talk about being right, for years, we've talked about the economics of cloud, the scale of cloud, the marginal economics, looking much more like software. That's clearly been to Amazon's advantage. And, they're mopping the floor with guys who can't keep pace. And so, that's played out in a big way, and this seems to be a winner take all market. Or, a few companies take all market. >> Yeah, the thing that I actually wanted to comment on that's really interesting to dig in here, is if you talk about application modernization. Yes, it is super challenging, and it's not happening overnight, but, have heard universities, non profits, they're moving. It's not just mobility, moving to the web, but talking about how they are decoupling and creating cloud native microservices environments. So, was talking to a large, government healthcare organization that was super excited to show me how he was going to take his really old application, and start pulling together services at a time. And, he's like, I've got 130 services. And here's how I'll stick a router in here and I'll start pulling them off to the cloud. Talked to a big university and said, how are they going from, my data center, which I'm out of power, I'm out of capacity. I'm going to use the VMWare thing, but over time, I'm moving to containers, I'm moving to serverless. That modernization, we know it's not moving all of it to the public cloud, but that migration is happening. It is challenging and as I've said many times in many of these Amazon shows, Dave and John, it's the companies that come here. They're the ones that are trying cool stuff. They're are able to play in some of these environments and they make progress. So, the thing that really excites me too, is when you hear government agencies that are doing innovative, cool things. It's like, how do I leverage my data and give back to the communities I serve. Help charities, help our communities, and do it in cost effective ways. >> Stu, I got to say, Dave, Theresa Carlson just came by theCUBE, we gave her a wave. She's the CEO of Public Sector, as I call her, she's the chief, she's in charge. Andy Jackson's the CEO of AWS, but again, public sector's almost its own little pocket of AWS. Her leadership, I think, is a real driving force of why it was successful so fast. Theresa Carleson is hard charging, she knows the government game. She's super nice, but she can fight. And she motivates her team. But she listens to the customers, and she takes advantage of that Amazon vibe, which is solve a problem, lower prices, make things go faster, that's the flywheel of the culture. And she brings it to a whole nother level. She's brought together a group of people that are succeeding with her. She leans on her partners, so partners are making money. She's bringing in cloud native kind of culture. I mean, CrowdStrike, you can't get any better than seeing guys like CrowdStrike raise 200 million dollars, Dave, today announced, worth over three billion dollars, because they built their system to work for cloud scale. CloudChecker, another company. Purpose built for the cloud and is extremely successful because they're not trying to retrofit an enterprise technology and make it cloudified. They actually built it for the cloud. This, to me, is a signal of what has to happen on successful deployments, from a customer standpoint. And I think that's what attracting the customers and they will change their operations 'cause the benefits are multifold and they're pretty big. Financially, operationally, culturally, it's disruptive. So I think that's a key point. >> Yeah, and I think again, this a microcosm of the larger AWS, which is a microcosm of the larger Amazon, but, some of the things we heard today, some of the benchmarks and milestones from Theresa on the keynote. 60 consultancies that she put up on the slide, 200 ISVs ans SAAS companies, 950 third-party software providers, this is all GovCloud. And then Aurora now in GovCloud, which is, you know, you see here, it lags. >> Database. >> Amazon and Specter, you've heard a lot about database. Amazon and Specter, which manages security configurations. We heard about the intent to go forward with the VMWare partnership, the VMWare cloud in GovCloud. So, a little bit behind where you see the Amazon web services in commercial. But, taking basically the same strategy as John said. The requirements are different. I also think, Stu and John, it's important to point out just the progress of AWS. We're talking about tracking to 22 billion dollars this year. They're growing still at 15 percent, that massive number. 26 percent operating income. Their operating income is growing at 54 percent a year. So, just to compare Amazon web services to other so called infrastructure providers, HPE's operating income is eight percent, IBM's is nine percent, VMWare, which is a software company, is at 19 percent, Amazon's at 26 percent. It's Cisco level of profitability. Only companies like Oracle and Microsoft are showing better operating income. This is that marginal economics, that we've talked about for years. And Amazon is crushing it, just in terms of the economic model. >> Yeah, and they bring in the public sector. Can you imagine that disruption for that incumbent mindset of these government kind of agencies that have been the frog in boiling water for so many years around IT. It's like Boom, what a wake up call. If you know IT, you know what it's like. Older tools, huge budget cycles, massive amounts of technology trends in terms of time to value. I mean, Stu, you've seen this buoy before. >> Yeah, absolutely, and it's interesting. Some of the things we heard is there's challenge in the government sometimes, moving from capex to opex. The way that government is used to buying is they buy out of the GSA catalog, they are making that move. We actually had on the federal CTO for Cohesity, came from the GSA, and he said we're making progress as an industry on this. Dave, you mentioned a whole lot of stats here. I mean, year after year, Q1 Amazon was up 49 percent revenue growth. So, you know, you always hear on the news, it's like, oh well, market share is shifting. Amazon is still growing at such a phenomenal pace, and in the GovCloud, one of the things I thought Kind of interesting that gets overlooked is the GovCloud is about five years, no it launched in August of 2011, so it's coming up on seven years. It's actually based out of the West Coast. They have GovCloud, US East is coming later this year. And we talked in the VMWare interview that we did today about why some of the lag and you need to go through the certification and you need to make sure there's extra security levels. Because, there's not only GovCloud, then they've got the secret region, the top secret region, so special things that we need to make sure that you're FedRAMP compliant and all these things. Amazon is hitting it hard, and definitely winning in this space. >> Yeah, and they have a competitive advantage, I mean, they're running the table, literally. Because no body else has secret cloud, right? So, Amazon, Google, others, they don't have what the spec requires on these big agencies, like the DOD. So, it's not a sole source deal. And we saw the press that President Trump had dinner with Safra Catz, the CEO of Oracle. And, that Amazon, that people are crying foul. Making a multicloud, multivendor kind of, be fair, you know fairness. Amazon's not asking for sole source, they're just saying we're responding to the bid. And, we're the only ones that actually can do it. You know, John Wood, the CEO of Telos, said it best on theCUBE today, Amazon is well down the road, five years advantage over any cloud, five years he said. >> There's no compression algorithm for experience, right? >> Right, right, but this is a real conundrum for the government buyers, the citizens, and the vendors. So, typically, let's face it, technology, IBM, HPE, Oracle, Dell, they can all pretty much do the same thing. Granted, they got software, Cisco, whatever. They got their different spaces, but head to head, they all pretty much can do what the RFP requires. But what you just pointed out John, is Amazon's the only one that can do a lot of this stuff, and so, when they say, okay let's make it fair, what they're really saying is, let's revert back to the mean. Is that the right thing for the citizens? That's the kind of question that's on the table now. As a citizen, do you want the government pushing the envelope... >> That's what he said from CrowdStrike, why go backwards? >> Right, right, but that's essentially what the old guard is saying. Come back to us, make it fair, is that unfair? >> You're too successful, let the competition catch up, so it can be fair. No, they've got to match up the value proposition. And that fundamentally is going to put the feet to fire of government and it's going to be a real critical tell sign on how much teeth to the mission that the government modernization plan is. If that mission to be modernizing government has teeth, they will stay in the course. Now, if they have the way to catch up, that's great. I can already hear it on Twitter, John, you don't really know what you're talking about. Microsoft's right there. Okay, you can say you're doing cloud, but as they teach you in business school, there's diseconomies of scale, to try to match a trajectory of an experienced cloud vendor. Stu, you just mentioned that, let's explore that. If I want to match Amazon's years of experience, I can say I'm up there with all these services, but you can't just match that overnight. There's diseconomies of scale, reverse proxies, technical debt, all kinds of stuff. So, Microsoft, although looking good on paper, is under serious pressure and those diseconomies of scales creates more risk. That more risk is more downtime. They just saw 11 hours of downtime on Microsoft Azure in Europe, 11 hours. That's massive, it's not like, oh, something just happened for a day. >> Here's the behind the scenes narrative that you hear from certain factions. Is, hey, we hire people, let's say I'm talkin' about Microsoft, we hire people out of Amazon too, we know where they're at. We think we've narrowed that lead down to six months. You and I have both heard that. When you talk to people on the other side of the table, it's like, no way, there's no way. We're movin' faster, in fact, our lead is extended. So, the proof is in the pudding. In the results that you see in the marketplace. >> Well, and just to build on that, the customers. Amazon has the customers, you talk to anybody that's in these agencies, you know, like any industry, they're all moving around. Not only the federal, but, I had a great interview with Nutanix this morning, he said this was the best collection of state and local government that I ever had. It's like I got to meet all my customers in person last year when they came here. So, the fed kind of sets the bar, and then state, local, education, they all learn there. So, as you said, John, Theresa and her team have really built a flywheel of customers, and those customers, they understand the product. They're going deeper on that. >> But look, Microsoft has success where it has a software state. Clearly there are a lot of Microsoft customers in the government, and they're going to do very well there. But it's really different. We're talkin' about the inventor, essentially, of infrastructure as a service in Public Cloud and Amazon with a clean sheet of paper. >> Microsoft, Google and the others, they have to catch up. So, really if you look at, let's compare and contrast. Amazon, first mover, they did the heavy lifting up front. They win the CIA deal three, four years ago. Now they're going to win the DOD deal and more. So, they've got the boiler plate, and they've got scale, economies of scale. Microsoft's got to catch up, so, they've got diseconomies of scale. Google is kind of backing out, we heard. Some Google employees revolting cause they don't want to work on these AI projects for drones or what not. But, Google's approach is not tryin' to match Amazon speed for speed, they're thing is they have leverage. Their Android, their security, the data. So, Google's staying much more pragmatic. And they're humble, they're saying, look, we're not tryin' to match Amazon. But we're going to have a badass cloud from a Google perspective. Microsoft hasn't yet said that, they just try to level up. I think if Microsoft takes that approach, they will do well. >> Well, you got to give Microsoft a lot of credit, obviously for the transformation that's occurred. Again it's still tied to the company's software estate, in my view anyway. >> All right Stu, what's your impression, what's your take? >> So, John, like every Amazon show I've been to, I'm impressed, it set a high bar. We go to a lot of shows and not only are there more people here, but the quality of people, the energy, the passion, the discussion of innovation and change, is just super impressive. >> You and I cover cloud data pretty deep. We go to all the shows, obviously the Lennox Foundation and Amazon Reinvent, and others. Does the Public Sector have that vibe in your opinion? What's your sense of it? >> Oh, yeah, no, I've already had a couple of conversations about Kubernetes and Lambda, you know, more serverless conversations at this show than almost any show I go to, other than probably KubeCon or the Serverless conf. So, no, advanced users, these are not the ones, a couple of years ago, oh I'm checking what this is. No, no, no, they're in, they're deep, they're using. >> Yeah, I notice also, near the press room, they had the certification stickers, now levels of certifications. So, they're just movin' the ball down the field at Amazon. Dave, I want to go to you and ask you what your impression is. Obviously, you know, we've done shows like HPE Reinvent, which we didn't do this year. That's goin' down its own path. We've got other shows. >> HPE Discover you mean. >> What did I say? >> You said Reinvent. >> Okay, every year they break. >> There's two ends of the spectrum. >> You know, there's is going to try to transform. What's your take of this show, Public Sector? What's your view? >> Well, first of all, it's packed. And, the ecosystem here is really robust. I mean, you see the consultancies, you see every technology vendor, I mean, it's quite amazing. They got to figure out the logistics, right? I've never seen a line so long. The line to get into registration was longer than Disney lines this morning. I mean, really, it was amazing. >> It's a Disneyland for Public Sector. >> It really is, and people are excited here. I think you were touching upon it before. They've sort of been hit with this bureaucratic, you know, cemented infrastructure. And now, it's like they're takin' the gloves off and they're really excited. >> Stu and Dave, I really got to say, I'm not a big federal person, over the years in my career but my general impression over the past couple years, diggin' in here, is that most of the people in the agency want to do a good job. I saw that last year, it's like, these are real innovators. And finally they can break away, right, and do some real, good. Not do shadow IT, do it legit with a cloud. So, good stuff. Guys, thanks for commentating, Stu? >> Yeah, so let me bring it on home. I just want to say, this goes up in a podcast, if you go to your favorite podcast player and look for theCUBE Insights, you'll find this as well as the key analysis from our team from all of the shows. Of course, as always, go to theCube dot net to get all the research. If you want the exclusive, more detail on Theresa Carlson, just search John Ferrier in Forbes and you'll find that article. This is the end of Day One of two days live coverage from AWS Public Sector. Of course, theCUBE dot net, come find us, we've got stickers if you're at the show. For Dave Vellante, John Furrier, I'm Stu Miniman. And as always, thanks so much for watching theCUBE. (techno music)

>> Announcer: Live from the Moscone Center, it's theCUBE covering AWS Summit San Francisco, 2018, brought to you by Amazon Web Services. (techy music playing) >> Welcome back, I'm Stu Miniman joined by my cohost Jeff Frick, and this is theCUBE's live coverage of AWS Summit San Francisco. We are thrilled to welcome back to the program Sandy Carter, who's a vice president with Amazon Web Services. Been with the company about a year. We've had you on the program many times, but first time since you've been at AWS, so... >> That's right, I'm celebrating my year yesterday with Amazon Web Services. >> Stu: And no cake, all right. >> I had a cake yesterday, actually, cake and champagne, by the way. (laughing) >> Sandy, we always love to hear, you know, you talk to so many customers, you know, bring us back for a little bit. What brought you to AWS, what's exciting to your customers when you're talking to them today? >> Well, you know, I really love innovation, I love being innovative, and you know, bar none Amazon is the most innovative company out there today, but really what brought me to Amazon was their focus on the customer, really "obsession" on the customer. When they say obsession they really mean obsession. They work backwards from the customer. We really have this big, big thrust. In fact, one of my favorite stories is when I first came to Amazon we'd be in these meetings and people would say, "Well, what does Low Flying Hawk think about this," or "What does Low Flying Hawk think about that," and I was like, "Who is Low Flying Hawk?" Well, he's a person who would give comments on a forum and just a person who wasn't even spending millions of dollars with Amazon but just had a lot of big clout. We actually just opened a building named Low Flying Hawk, believe it or not. >> Jeff: Have you identified this person? >> They do know who he is, yes. (laughing) But it's really, it just symbolizes the focus that Amazon has on the customer and why that's so important. >> And Sandy, at re:Invent you actually, you spoke to the analyst, I was listening to the session. It's not just kind of, people think AWS they think public cloud. You work for Amazon, it's everything kind of across what you think of Amazon.com, AWS, everything from drones and using Kindles and everything like that. Can you give us a little bit of kind of that pan view of how Amazon looks at innovation? >> Yeah, so it's really interesting. Amazon is very methodical in the way that we innovate, and what we do is we really try to understand the customer. We work backwards from the customer, so we do a press release first, we do frequently asked questions next, and then we do a narrative-- >> You're saying you do an internal press release, yes, yes. >> Yeah, internal press release. Internal frequently asked questions, and then we review a six-page document, no PowerPoints whatsoever, which enables us to debate and learn from each other and just iterate on the idea that makes it better and better and better so that when we come out with it it's a really powerful idea and powerful concept, something that the customers really want. >> So, we'll ask you what you're doing now, but one more kind of transition question, what was your biggest surprise? You know, there's a lot of kind of mystery from people on the outside looking in in terms of culture, and we know it's car driving and innovative growing like crazy company, not only in business but in terms of people. What was your biggest surprise once you kind of got on the inside door? >> My biggest surprise was just how incredibly encouraging and supportive the team is at AWS. My boss is Matt Garman, he's been supportive since day one, you know, Andy, they just cheer you on. They want you to do well and I've really never been at a company that everybody's really pulling for you to be successful, not political infighting but really pulling for you to be successful. So, that's really was the biggest surprise to me, and then that customer obsession. Like, it's not customer focus, it really is customer obsession. >> Right, I think it's so well illustrated by the, again not AWS, but Amazon with the store, right, with no cash register, no people. >> Sandy: Amazon Go. >> To think about that-- >> Sandy: Yeah. >> From the customer point of view is nobody likes to stand in line at the grocery store, so it's such a clean illustration of a customer centric way to attack the problem. >> And I love that because what we did is we opened up the beta first for employees, so we would go in and play with it and test it out, and then we opened it up in Seattle and we would give customer tours. Now it's open to the public in Seattle, so it just again shows you that iterative process that Amazon uses and it's super cool, have you guys been? >> Jeff: Have not been. >> Ugh, in fact, my daughter went in. She put on a mask, she was going to fool the system but it wasn't fooled. All the ML and all the AI worked brilliantly. >> I love how everyone loves to get so creative and try to, you know, get through the system, right, try to break the system. >> I know, but my daughter, that's what I would figure for sure. (laughing) >> So, what are you working on now? You've been there a year, what are you working on? >> So, we are innovating around the enterprise workload, so we know that a lot of startups and cloud native companies have moved to the cloud, but we're still seeing a lot of enterprises that are trying to figure out what their strategy is, and so, Stu and Jeff, what I've been working on is how do we help enterprises in the best way possible. How can we innovate to get them migrated over as fast as possible? So for instance, we have Windows that runs on AWS. It's actually been running there longer than with any other vendor and we have amazing performance, amazing reliability. We just released an ML, machine learning OMI for Windows so that you can use and leverage all that great Windows support and applications that you have, and then you guys saw earlier I was talking to VMware. We know that a lot of customers want to do hybrid cloud on their journey to going all-in with the cloud, and so we formed this great partnership with VMware, produced an offering called VMware Cloud on AWS and we're seeing great traction there. Like Scribd's network just talked about how they're using it for disaster recovery. Other customers are using it to migrate. One CIO migrated 143 workloads in a weekend using that solution. So, it just helps them to get to that hybrid state before they go all-in on the cloud. >> So, are they, I was going to say, are they building a mirror instance of what their on-prem VMware stack is in the Amazon version? Is that how they're kind of negotiating that transition or how does that work? >> So, with VMware they don't have to refactor, so they can just go straight over. With Microsoft workloads what we're seeing a lot of times is maybe they'll bring a sequel app over and they'll just do a lift and shift, and then once they feel comfortable with the cloud they'll go to Aurora, which as you've found was the fastest growing service that AWS has ever had, and so we see a lot of that, you know, movement. Bring it over, lift and shift, learning and you know, if you think about it, if you're a large enterprise one of your big challenges is how do I get my people trained, how do I get them up to speed, and so we've done... Like, we've got a full dot net stack that runs on AWS, so their people don't even have to learn a new language. They can develop in Visual Studio and use PowerShell but work on AWS and bring that over. >> You know, Sandy, bring us inside your customers because the challenge for most enterprises is they have so many applications. >> Sandy: Yeah. >> And you mentioned lift and shift. >> Sandy: Yeah. >> You know, I know some consultant's out there like, "Lift and shift is horrible, don't do it." It's like, well, there's some things you'll build new in the cloud, there's some things you'll do a little bit, and there's some stuff today lift and shift makes sense and then down the road I might, you know, move and I've seen, you know, it was like the seven Rs that Amazon has as to do you re-platform, refactor-- >> That's right. >> You know, all that and everything, so I mean, there's many paths to get there. What are some of the patterns you're hearing from customers? How do they, how is it easier for them to kind of move forward and not get stuck? >> Well, we're seeing a lot of data center evacuations, so those tend to be really fast movement and that's typically-- >> Jeff: Data center evacuation-- >> Yeah, that's what-- >> I haven't heard that one. >> Yeah, that's what, evacuation, they've got to get out of their data center buyer for a certain date for whatever reason, right? They had a flood or a corporate mandate or something going on, and so we are seeing those and those are, Stu, like lift and shift quickly. We are seeing a lot of customers who will create new applications using containers and serverless that we talked about today a lot, and that's really around the innovative, new stuff that they're doing, right. So, Just Eat, for instance, is a large... They do online food service out of the UK. I love their solution because what they're doing is they're using Alexa to now order food, so you can say, "Alexa, I want a pizza delivered "in 20 minutes, what's the best pizza place "that I can get in 20 minutes?" Or "I want sushi tonight," and Alexa will come back and say, "Well, it's going to take "an hour and a half, you had sushi two days ago. "Maybe you want to do Thai food tonight." (laughing) And so it's really incredible, and then they even innovated and they're using Amazon Fire for group ordering. So, if there's a big football game or something going on they'll use Amazon Fire to do that group ordering. All that is coming in through Alexa, but the back end is still Windows on AWS. So, I love the fact that they're creating these new apps but they're using some of that lift and shift to get the data and the training and all that moving and grooving, too. >> Yeah, what do you, from the training standpoint, how, you know, ready are customers to retrain their people, you know, where are there shortages of skillsets, and how's Amazon, you know, helping in that whole movement? >> Well, training is essential because you've got so many great people at enterprises who have these great skills, so what we see a lot of people doing is leveraging things like dot net on AWS. So, they actually... They have something they know, dot net, but yet they're learning about the cloud, and so we're helping them do that training as they're going along but they still have something very familiar. Folks like Capital One did a huge training effort. They trained 1,000 people in a year on cloud. They did deep dives with a Tiger Team on cloud to get them really into the architecture and really understanding what was going on, so they could leverage all those great skills that they had in IT. So, we're seeing everything from, "I got to use some of the current tools that I have," to "Let me completely move to something new." >> And how have you, you've been in the Bay Area also for about a year, right, if I recall? >> Actually, I just moved, I moved to Seattle. >> Jeff: Oh, you did make the move, I was going to say-- >> I did. (laughing) >> "So, are they going to make you move up north?" >> I did because I was-- >> You timed it in the spring, not in November? >> I did, there you go. (laughing) When it's nice and sunny, but it's great. >> Exactly. >> It's great to live in Seattle. Amazon has such a culture that is in person, you know, so many people work there. It's really exhilarating to go into the office and brainstorm and whiteboard with people right there, and then our EBCs are there, so our executive briefing center is there, so customers come in all the time because they want to go see Amazon Go, and so it's really an exciting, energizing place to be. >> Yeah, I love the line that Warner used this morning is that AWS customers are builders and they have a bias for action. So, how do you help customers kind of translate some of the, you know, the culture that Amazon's living and kind of acting like a startup for such a large company into kind of the enterprise mindset? >> That's a great question, so we just proposed this digital innovation workshop. We are doing this now with customers. So, we're teaching them how to work backwards from the customer, how to really understand what a customer need is and how to make sure they're not biased when they're getting that customer need coming in. How to do, build an empathy map and how to write that press release, that internal press release and think differently. So, we're actually teaching customers to do it. It's one of our hottest areas today. When customers do that they commit to doing a proof of concept with us on AWS on one of the new, innovative ideas. So, we've seen a lot of great and exciting innovation coming out of that. >> All right, well, Sandy Carter, so glad we could catch up with you again. Thanks for bringing discussion of innovation, what's happening in the enterprise customers to our audience. For Jeff Frick, I'm Stu Miniman, we'll be back will lots more coverage here, you're watching theCUBE. (techy music playing)

>> Narrator: Live, from Santa Clara in the heart of Silicon Valley, it's theCUBE. Covering Cloud Foundry Summit 2017. Brought to you by the Cloud Foundry Foundation and Pivotal. >> Hi this is Stu Miniman, joined with my cohost, John Troyer. Happy to welcome to the program a first-time guest, Chip Childers, who's the CTO of the Cloud Foundry Foundation. Chip, fresh off the keynote stage, >> Yep. >> how's everything going? >> It's going great. We're really happy with the turnout of the conference. We are really happy with the number of large enterprises that are here to share their story. The really active vendor ecosystem around the project. It's great. It's a wonderful event so far. >> Yeah, I was looking back, I think the last time I came to the Cloud Foundry Show, it was before the Foundation existed, We were in the Hilton in San Francisco, it was obviously a way smaller group. Tell us kind of the goals of the Foundation, doing the event, bringing the community in. >> Yeah, you can think about our goals as being of course, we're the stewards of the intellectual property, the actual software that the vendors distribute. We see our role in the ecosystem as being really two key things. One: we're focused on supporting the users, the customers, and the direct uses of the Open Source software. That's first and foremost. Second though, we want to make sure there is a really robust market ecosystem that is wrapped around this project, right. Both in terms of the distribution, the regional providers that offer Cloud Foundry based services, but also large system integrators that are helping those customers go through digital transformation. Re-platform applications, you know really figure out their way through this process. So, it's all about supporting the users and then supporting the market around it. >> Yeah, as we go to a lot of these events, you know, there are certain themes that emerge. There were two big ones that both of them showed up in what you did in the Keynote. Number one is Multicloud, number two is you got all of these various open sourced pieces, >> Chip: Yep. you know, what fits together, what interlocks together, you know which ones sit side by side. Why don't we start with kind of the open source piece first? Because you're heavily involved in a lot of those. Cloud Foundry, you know, what are the new pieces that are bolting on, or sitting on top, or digging into it, and what's going on there? >> You know, I think first I want to start with a basic philosophy of our upstream community. There are billions of dollars that rely on this platform today. And that continues to grow. Right, because we're showing up in Fortune 500, Global 2000, as well as lots of small start-ups, that are using Cloud Foundry to get code shipped faster. So our community that builds the UpStream software, spends a lot of time being very thoughtful about their technical decisions. So what we release and that what gets productized by the down streams is a complete system. From operating system all the way up to including the various programming languages and frameworks and everything in between. And because we release a complete platform, at a really high velocity, so many people rely on it's quality, we're very thoughtful about when is the right time to build our own, when should we adopt and embrace and continue to support another OpenSource project, so we spend a lot of time really thinking about that. And the areas today that I highlight around specific collaborations include the Open Service Broker API which we actually spun out of being just a Club Foundry implementation. And we embrace other communities, and found a way to share the governance of that. So we move forward as a big industry together. >> Stu: Yeah and speaking on that a little bit more. Very interesting to see. I saw Red Hat for instance speaking with Open Shift, Kubernetes is there. So, how should customers think about this? Are the path wars over? Now you can choose all the pieces that you want? Or, it's probably oversimplifying it. >> I think it's over simplifying it, it depends. You can go try to build your own platform if you want, through a number of serious components, or you can just use something like Cloud Foundry, that has solve for that. But the important thing is that we have specifically designed Cloud Foundry to allow for the backing services to come from anywhere. And so, it's both a differentiator for the various distributions of Cloud Foundry, but also an opportunity for Cloud providers, and even more importantly, it's an opportunity for the enterprise users that live in complex worlds, right? They're going to have multiple platforms, they're going be multiple levels of abstraction from Bms to containers, you know, to the path abstraction even event driven frameworks. We want that all to work really well together. Regardless of the choices you make, because that's what's most valuable to the customers. >> Okay, the other piece, networking you talked about. Why don't you share. >> Yeah, yeah so, besides the Service Broker API, we've added support for what's called Container to Container Networking. I don't necessarily need to dig into the details there, but let's just say that when you're building microservices that the application that the user is experiencing is actually a combination of a lot of different applications. That all talk to each other and rely on each other. So we want to make sure there's a policy-based framework for describing how the webs here is going to talk to the authentication service or is going to talk to the booking service, or the inventory service. They all need to have rules about how they communicate with each other. And we want to do that in the most efficient way possible. So we've adopted the Containing Networking interface as the standard plugin that is now at CNCF, the Cloud Native Computing Foundation. We think it's the right abstraction, we think it's great. It gives us access to all the fascinating work that is going on around software networking, overlay networking, industry standard API plugin to our policy-driven framework. >> Along the same theme, Kubo, a big new news project also kind of integration of some Cloud Foundry concepts with a broader ecosystem, in this case another CNCF project, Kubernetes. Could you speak a little bit to that? >> The Kubernetes community is doing a great job creating great container driven experience. You know that abstraction is all about the container. It's not about, you know, the code. So it's different than Cloud Foundry. There are workloads that make sense to run in one or the other. And we want to make sure that they run really well. Right, so the problem that we're solving with the Kuber project is what deploys Kubernetes? What supports Kubernetes if there is an infrastructure adage and a node goes offline? Right, because it does a great job of restarting containers, but if you have ten nodes in a cluster, and then now you're down to nine, that's a problem. So what Bosh does, is it takes care of solving the node outage level problem. You can also do rolling upgrades that are seamless, no downtime for the Kubernetes cluster. It brings a level of operational maturity to the Kubernetes users that they may not have had otherwise. >> Chip, can you bring us inside a little bit the creation of Kubo, is that something that the market and customers drove towards you? I talked to a couple other Cloud Foundry ecosystem members that were doing some other ways of integrating in Kubernetes. So what lead to this way of deploying it with Bosh? >> Yeah, absolutely so, it came out of a direct collaboration between Pivotal and Google. And it was driven based on Pivotal customer demand. It also, if you speak with people from Google that are involved in the project, they also see it as a need, for the Kubernetes ecosystem. So it's driven based on real-world large financial services companies that wanted to have the multiple abstractions available, they wanted to do it with a common operational platform that is proven mature that they've already adopted. And then as that collaboration board, the fruit of the project, and it was announced by Pivotal and Google several months back, they realized that they needed to move it to the vendor neutral locations so that we can continue to expand the community that can work on it, that can build up the story. >> The other topic I raised at the beginning of the interview, was the Multicloud. So in a panel, Microsoft, Google, MTC for Amazon was there. All of the Cloud guys are going to tell you we have the best platform and can do the best things for you. >> Of course they do. >> How do you balance the "We want to live in a multicultural Cloud world" and be able to go there versus "Oh I'm going to take standard plus and get in a little bit deeper to make sure that we're stickier with the customers there." What role does Cloud Foundry play? What have you seen in the marketplace for that? >> Well the public lab providers are, if you look at the services that they offer, you can roughly categorize them with two things. One, are the infrastructure building blocks. Two, are the higher level services, like their database capabilities, their analytics capabilities, log aggregation, you know, and they all have a portfolio that varies, some have specific things that are very similar. So when we talk about MultiCloud we talk about Cloud Foundry as a way to make use of those common capabilities, now they're going to differentiate based on speeds and feeds, availability, whatever they choose to, but you can then as a user have choice. And then secondarily, that Open Service Broker initiative is what's really about saying "great, there's also all these really valuable additional capabilities, that, as a user, I may choose to integrate with a Google machine learning-service, or I may choose to integrate with a wonderful Microsoft capability, or an Amazon capability." And we just want to make that easy for a developer to make that choice. >> Chip, Cloud Founder was very early in terms of a concept of a platform of services, let's not call it platform as a service right now. But you know, this platform that going to make developers lives easier, multi-target, MultiCloud we call it now, on from your laptop to anywhere. And it's been a really interesting discussion over the last couple years as this parallel container thread can come up with Kubernetes and Mesosphere and all the orchestration tools, and the focus has been on orchestration tools. And I've always thought Cloud Foundry was kind of way ahead of the game in saying "wait a minute, there's a set of services that you're going to have for full life-cycles, day two operation, at scale that you all are going to have to pull together from components." As we're doing this interview here, and this year at Cloud Foundry Summit are there anything that you think people don't kind of realize that over and over again people who are using Cloud Foundry go, "Wow I'm really glad "I had logging or identity management," or what are some of the frameworks that people sometimes don't realize is in there that actually is a huge time-savor. >> Yeah, there are a lot of operational capabilities in the Cloud Foundry platform. When you include both our Bosh layer, as well as the elastic runtime which is in the developer centers experience-- >> John: Anything that people don't often realize is in there? >> Well, I think that the right way to think of it is, it's all the things you need in one application, right? So we've been doing this for years as developers. In the applications operators team, we've been doing it. We've just been doing it via bunch of tickets, we've been doing it via bunch of scripts. What Cloud Foundry does is it takes all of those capabilities you need to really trust a platform to operate something on your behalf, and give you the right view into it, right? The appropriate telemetry, log aggregation, and know that there's going to be help monitoring there. It makes it really easy. Right, so we were talking earlier about the haiku, that Onsi Fakhouri from Pivotal had authored, it's appropriate. It's a promise that a platform makes. And platforms designed to let a user trust that the declarative nature of asking a platform to do X, Y, or Z, will be delivered. >> Chip, we've been hearing Pivotal talks a lot about Spring, when Cloud Foundry's involved. Is it so much so that the Foundation needs to be behind that, or support that? How does that interact and work? >> Well, we're super supportive of all the languages in the framework communities that are out there. You know, even if you pick a particular vendor, Pivotal in this case has a very strong investment in the Spring, Spring Cloud, Spring Boot, they're doing really amazing things. But that's also, it's our software, you know, they steward that community, so all the other vendors actually get the advantage of that. Let's take Dot Net and Microsoft. Microsoft open sourced Dot Net. So now you can run Dot Net applications on Linux. They're embrace of the container details and the APIs and their operating system is making it so that now it can also run on Windows. So the whole Microsoft technology stack, languages and frameworks, they matter quite a bit to the enterprise as well. So we see ourselves as supportive of all of these communities, right? Even ones like the Ruby community. When there's an enterprise developer that chooses to use something like Ruby, with the Ruby on Rails framework, if they use Cloud Foundry, they're getting the latest and greatest version of that language, framework, they know that it's secure, they know that it's going to be patched for them. So it's actually a great experience for that developer, that's working with the language. So, we like to support all of them, we're big fans of any that work really well with the platform and maybe integrate deeper. But it's a polyglot platform. >> We want to give you the final word. People take away from Cloud Foundry Summit 2017, what would you want them to take away? >> Yeah the simple takeaway that I can give you is that this is an absolutely enterprise grade open source ecosystem. And you don't hear that often, right? Because normally we talk about products, being enterprise great. >> Did somebody say in the keynote enterprise great mean that there's a huge salesforce that's going to try sell you stuff? (Chip laughs) Well that's coming from the buying side of the market for years. And you know, it was a bit of a joke. What is "enterprise great?" Well, it means that there's a piece of paper that says, this product will cost x dollars and the salesperson is offering it to you. So of course it's going to be enterprise great. But really, we see it as four key things, right? It's about security, it's about being well-integrated, it's about being able to scale to the needs of even the largest enterprises, and it's also about that great developer experience. So, Cloud Foundry is an ecosystem and all of our downstream distributions get the advantage of this really robust and mature technical community that is producing this software. >> Chip, really appreciate you sharing all the updates with us, and appreciate the foundation's support to bring theCUBE here. We'll be back with lots more coverage here from The Cloud Foundry Summit 2017, you're watching theCUBE. (techno music)

the cube and hadoop summit 2014 is brought to you by anchor sponsor Hortonworks we do have do and headline sponsor when disco we make hadoop invincible okay welcome back and when we're here at the dupe summit live is looking valance the cube our flagship program we go out to the events expect a signal from noise i'm john per year but Jeff Rick drilling down on the topics we're here with wind disco welcome welcome Brett room Stein about senior director tell us what's going on for you guys I'll see you at big presence here so all the guys last night you guys have a great great booth so causing and the crew what's happening yeah I mean the show is going is going very well what's really interesting is we have a lot of very very technical individuals approaching us they're asking us you know some of the tougher more technical in-depth questions about how our consensus algorithm is able to do all this distributor replication which is really great because there's a little bit of disbelief and then of course we get to do the demonstration for them and then suspend disbelief if you will and and I think the the attendance has been great for our brief and okay I always get that you always we always have the geek conversations you guys are a very technical company Jeff and I always comment certainly de volada and Jeff Kelly that you know when disco doesn't has has their share pair of geeks and that dudes who know they're talking about so I'm sure you get that but now them in the business side you talk to customers I want to get into more the outcome that seems to be the show focused this year is a dupe of serious what are some of the outcomes then your customers are talking about when they get you guys in there what are their business issues what are they tore what are they working on to solve yeah I mean I think the first thing is to look at you know why they're looking at us and then and then with the particular business issues that we solve and the first thing and sort of the trend that we're starting to see is the prospects and the customers that we have are looking at us because of the data that they have and its data that matters so it's important data and that's when people start to come to is that's when they look to us as they have data that's very important to them in some cases if you saw some of the UCI stuff you see that the data is you know doing live monitoring of various you know patient activity where it's not just about about about a life and monitoring a life but potentially about saving the life and systems that go down not only can't save lives but they can potentially lose them so you have a demos you want to jump into this demo here what is this all about you know the demo that the demonstration that I'm going to do for you today is I want to show you our non-stop a new product i'm going to show you how we can basically stand up a single HDFS or a single Hadoop cluster across multiple data centers and I think that's one of the tough things that people are really having trouble getting their heads wrapped around because most people when they do multi data center Hadoop they tend to do two different clusters and then synchronize the data between the two of them the way they do that is they'll use you know flume or they'll use some form of parallel ingest they'll use technologies like dis CP to copy data between the data centers and each one of those has sort of an administrative burden on them and then some various flaws in their and their underlying architecture that don't allow them to do a really really detailed job as ensuring that all blocks are replicated properly that no mistakes are ever made and again there's the administrative burden you know somebody who always has to have eyes in the system we alleviate all those things so I think the first thing I want to start off with we had somebody come to our booth and we were talking about this consensus algorithm that we that we perform and the way we synchronize multiple name nodes across multiple geographies and and again and that sort of spirit of disbelief I said you know one of the key tenants of our application is it doesn't underlie it doesn't change the behavior of the application when you go from land scope to win scope and so I said for example if you create a file in one data center and 3,000 miles apart or 7,000 miles apart from that you were to hit the same create file operation you would expect that the right thing happens what somebody gets the file created and somebody gets file already exists even if at 7,000 miles distance they both hit this button at the exact same time I'm going to do a very quick demonstration of that for you here I'm going to put a file into HDFS the my top right-hand window is in Northern Virginia and then 3,000 miles distance from that my bottom right-hand window is in Oregon I'm going to put the etsy hosts file into a temp directory in Hadoop at the exact same time 3,000 miles distance apart and you'll see that exact behavior so I've just launched them both and again if you look at the top window the file is created if you look at the bottom window it says file already exists it's exactly what you'd expect a land scope up a landscape application and the way you'd expect it to behave so that is how we are ensure consistency and that was the question that the prospect has at that distance even the speed of light takes a little time right so what are some of the tips and tricks you can share this that enable you guys to do this well one of the things that we're doing is where our consensus algorithm is a majority quorum based algorithm it's based off of a well-known consensus algorithm called paxos we have a number of significant enhancements innovations beyond that dynamic memberships you know automatic scale and things of that nature but in this particular case every transaction that goes into our system gets a global sequence number and what we're able to do is ensure that those sequence numbers are executed in the correct order so you can't create you know you can't put a delete before a create you know everything has to happen in the order that it actually happened occurred in regardless of the UN distance between data centers so what is the biggest aha moment you get from customer you show them the demo is it is that the replication is availability what is the big big feature focus that they jump on yeah I think I think the biggest ones are basically when we start crashing nodes well we're running jobs we separate the the link between the win and maybe maybe I'll just do that for you now so let's maybe kick into the demonstration here what I have here is a single HDFS cluster it is spanning two geographic territory so it's one cluster in Northern Virginia part of it and the other part is in Oregon I'm going to drill down into the graphing application here and inside you see all of the name notes so you see I have three name nodes running in Virginia three name nodes running in Oregon and the demonstration is as follows I'm going to I'm going to run Terrigen and Terra sort so in other words i'm going to create some data in the cluster I'm then going to go to sort it into a total order and then I'm going to run Tara validate in the alternate data center and prove that all the blocks replicated from one side to the other however along the way I'm going to create some failures I am going to kill some of that active name nodes during this replication process i am going to shut down the when link between the two data centers during the replication paris's and then show you how we heal from from those kinds of conditions because our algorithm treats failure is a first class citizen so there's really no way to deal in the system if you will so let's start unplug John I'm active the local fails so let's go ahead and run the Terrigen in the terrorists or I'm going to put it in the directory called cube one so we're creating about 400 megabytes of data so a fairly small set that we're going to replicate between the two data centers now the first thing that you see over here on the right-hand side is that all of these name nodes kind of sprung to life that is because in an active active configuration with multiple name nodes clients actually load balance their requests across all of them also it's a synchronous namespace so any change that I make to one immediately Curzon immediately occurs on all of them the next thing you might notice in the graphing application is these blue lines over and only in the Oregon data center the blue lines essentially represent what we call a foreign block a block that is not yet made its way across the wide area network from the site of ingest now we move these blocks asynchronously from the site of in jeff's oh that I have land speed performance in fact you can see I just finished the Terrigen part of the application all at the same time pushing data across the wide area network as fast as possible now as we start to get into the next phase of the application here which is going to run terrace sort i'm going to start creating some failures in the environment so the first thing I'm going to do is want to pick two named nodes I'm going to fail a local named node and then we're also going to fail a remote name node so let's pick one of these i'm going to pick HD p 2 is the name of the machine so want to do ssh hd2 and i'm just going to reboot that machine so as I hit the reboot button the next time the graphing application updates what you'll notice here in the monitor is that a flat line so it's no longer taking any data in but if you're watching the application on the right hand side there's no interruption of the service the application is going to continue to run and you'd expect that to happen maybe in land scope cluster but remember this is a single cluster a twin scope with 3,000 miles between the two of them so I've killed one of the six active named nodes the next thing I'm going to do is kill one of the name nodes over in the Oregon data center so I'm going to go ahead and ssh into i don't know let's pick the let's pick the bottom one HTTP nine in this case and then again another reboot operation so I've just rebooted two of the six name nose while running the job but if again if you look in the upper right-hand corner the job running in Oregon kajabi running in North Virginia continues without any interruption and see we just went from 84 to eighty eight percent MapReduce and so forth so again uninterruptedly like to call continuous availability at when distances you are playing that what does continuous availability and wins because that's really important drill down on yeah I mean I think if you look at the difference between what people traditionally call high availability that means that generally speaking the system is there there is a very short time that the system will be unavailable and then it will then we come available again a continuously available system ensures that regardless of the failures that happen around it the system is always up and running something is able to take the request and in a leaderless system like ours where no one single node actually it actually creates a leadership role we're able to continue replication we're and we're also able to continue the coordinator that's two distinct is high availability which everyone kind of know was in loves expensive and then continues availability which is a little bit kind of a the Sun or cousin I guess you know saying can you put in context and cost implementation you know from a from a from a from a perspective of a when disco deployment it's kind of a continuously available system even though people look at us as somewhat traditional disaster recovery because we are replicating data to another data center but remember it's active active that means both data centers are able to write at the same time you have you get to maximize your cluster resources and again if we go back to one of the first questions you asked what are what a customer's doing this with this what a prospects want to do they want to maximize their resource investment if they have half a million dollars sitting in another data center that only is able to perform an emergency recovery situation that means they either have to a scale the primary data center or be what they want to do is utilize existing resource in an active active configuration which is why i say continuous availability they're able to do that in both data centers maximizing all their resource so you versus the consequences of not having that would be the consequences of not being able to do that is you have a one-way synchronization a disaster occurs you then have to bring that data center online you have to make sure that all the appropriate resources are there you have to you have an administrative burden that means a lot of people have to go into action very quickly with the win disco systems right what that would look like I mean with time effort cost and you have any kind of order of magnitude spec like a gay week called some guy upside dude get in the office login you have to look at individual customer service level agreements a number that i hear thrown out very very often is about 16 hours we can be back online within 16 hours really RTO 44 when disco deployment is essentially zero because both sites are active you're able to essentially continue without without any doubt some would say some would say that's contingent availability is high available because essentially zero 16 that's 16 hours I mean any any time down bad but 16 hours is huge yeah that's the service of level agreement then everyone says but we know we can do it in five hours the other of course the other part of that is of course ensuring that once a year somebody runs through the emergency configure / it you know procedure to know that they truly can be back up in line in the service level agreement timeframe so again there's a tremendous amount of effort that goes into the ongoing administrating some great comments here on our crowd chatter out chat dot net / hadoop summit joined the conversation i'll see ya we have one says nice he's talking about how the system has latency a demo is pretty cool the map was excellent excellent visual dave vellante just weighed in and said he did a survey with Jeff Kelly said large portion twenty-seven percent of respondents said lack of enterprises great availability was the biggest barriers to adoption is this what you're referring to yeah this is this is exactly what we're seeing you know people are not able to meet the uptime requirements and therefore applications stay in proof-of-concept mode or those that make it out of proof of concept are heavily burdened by administrators and a large team to ensure that same level of uptime that can be handled without error through software configuration like Linda scope so another comment from Burt thanks Burt for watching there's availability how about security yeah so security is a good one of course we are you know we run on standard dupe distributions and as such you know if you want to run your cluster with on wire encryption that's okay if you want to run your cluster with kerberos authentication that's fine we we fully support those environments got a new use case for crowd chapel in the questions got more more coming in so send them in we're watching the crowd chat slep net / hadoop summit great questions and a lot of people aren't i think people have a hard time partial eh eh versus continues availability because you can get confused between the two is it semantics or is it infrastructure concerns what is what is the how do you differentiate between those two definitions me not I think you know part of it is semantics but but but also from a win disco perspective we like to differentiate because there really isn't that that moment of downtime there is there really isn't that switch over moment where something has to fail over and then go somewhere else that's why I use that word continuous availability the system is able to simply continue operating by clients load balancing their requests to available nodes in a similar fashion when you have multiple data centers as I do here I'm able to continue operations simply by running the jobs in the alternate data center remember that it's active active so any data ingest on one side immediately transfers to the other so maybe let me do the the next part I showed you one failure scenario you've seen all the nodes have actually come back online and self healed the next part of this I want to do an separation I want to run it again so let me kick up kick that off when I would create another directory structure here only this time I'm going to actually chop the the network link between the two data centers and then after I do that I'm going to show you some some of our new products in the works give you a demonstration of that as well well that's far enough Britain what are some of the applications that that this enables people to use the do for that they were afraid to before well I think it allows you know when we look at our you know our customer base and our prospects who are evaluating our technologies it opens up all the all the regulated industries you know things like pharmaceutical companies financial services companies healthcare companies all these people who have strict regulations auditing requirements and now have a very clear concise way to not only prove that they're replicating data that data has actually made its way it can prove that it's in both locations that it's not just in both locations that it's the correct data sometimes we see in the cases of like dis CP copying files between data centers where the file isn't actually copied because it thinks it's the same but there is a slight difference between the two when the cluster diverges like that it's days of administration hour depending on the size of the cluster to actually to put the cluster you know to figure out what went wrong what went different and then of course you have to involve multiple users to figure out which one of the two files that you have is the correct one to keep so let me go ahead and stop the van link here of course with LuAnn disco technology there's nothing to keep track of you simply allow the system to do HDFS replication because it is essentially native HDFS so I've stopped the tunnel between the two datacenters while running this job one of the things that you're going to see on the left-hand size it looks like all the notes no longer respond of course that's just I have no visibility to those nodes there's no longer replicating any data because the the tunnel between the two has been shut down but if you look on the right hand side of the application the upper right-hand window of course you see that the MapReduce job is still running it's unaffected and what's interesting is once I start replicating the data again or once i should say once i start the tunnel up again between the two data centers i'll immediately start replicating data this is at the block level so again when we look at other copy technologies they are doing things of the file level so if you had a large file and it was 10 gigabytes in size and for some reason you know your your file crash but in that in that time you and you were seventy percent through your starting that whole transfer again because we're doing block replication if you had seventy percent of your box that had already gone through like perhaps what I've done here when i start the tunnel backup which i'm going to do now what's going to happen of course is we just continue from those blocks that simply haven't made their way across the net so i've started the tunnel back up the monitor you'll see springs back to life all the name nodes will have to resync that they've been out of sync for some period of time they'll learn any transactions that they missed they'll be they'll heal themselves into the cluster and we immediately start replicating blocks and then to kind of show you the bi-directional nature of this I'm going to run Tara validate in the opposite data center over in Oregon and I'll just do it on that first directory that we created and in what you'll see is that we now wind up with foreign blocks in both sides I'm running applications at the same time across datacenters fully active active configuration in a single Hadoop cluster okay so the question is on that one what is the net net summarized that demo reel quick bottom line in two sentences is that important bottom line is if name notes fail if the wind fails you are still continuously operational okay so we have questions from the commentary here from the crowd chat does this eliminate the need for backup and what is actually transferring certainly not petabytes of data ? I mean you somewhat have to transfer what what's important so if it's important for you to I suppose if it was important for you to transfer a petabyte of data then you would need the bandwidth that support I transfer of a petabyte of data but we are to a lot of Hollywood studios we were at OpenStack summit that was a big concern a lot of people are moving to the cloud for you know for workflow and for optimization Star Wars guys were telling us off the record that no the new film is in remote locations they set up data centers basically in the desert and they got actually provisioned infrastructure so huge issues yeah absolutely so what we're replicating of course is HDFS in this particular case I'm replicating all the data in this fairly small cluster between the two sites or in this case this demo is only between two sites I could add a third site and then a failure between any two would actually still allow complete you know complete availability of all the other sites that still participate in the algorithm Brent great to have you on I want to get the perspective from you in the trenches out in customers what's going on and win disco tell us what the culture there what's going on the company what's it like to work there what's the guys like I mean we we know some of the dudes there cause we always drink some vodka with him because you know likes to tip back a little bit once in a while but like great guy great geeks but like what's what's it like it when disco I think the first you know you touched on a little piece of it at first is there are a lot of smart people at windows go in fact I know when I first came on board I was like wow I'm probably the most unsmoked person at this company but culturally this is a great group of guys they like to work very hard but equally they like to play very hard and as you said you know I've been out with cause several times myself these are all great guys to be out with the culture is great it's a it's a great place to work and you know so you know people who are who are interested should certainly yeah great culture and it fits in we were talking last night very social crowd here you know something with a Hortonworks guide so javi medicate fortress ada just saw him walk up ibm's here people are really sociable this event is really has a camaraderie feel to it but yet it's serious business and you didn't the days they're all a bunch of geeks building in industry and now it's got everyone's attention Cisco's here in Intel's here IBM's here I mean what's your take on the big guys coming in I mean I think the big guys realize that that Hadoop is is is the elephant is as large as it appears elephant is in the room and exciting and it's and everybody wants a little piece of it as well they should want a piece of it Brett thanks for coming on the cube really appreciate when discs are you guys a great great company we love to have them your support thanks for supporting the cube we appreciate it we right back after this short break with our next guest thank you