>>Live from San Diego, California at the cue covering to clock in cloud native con brought to you by red hat, the cloud native computing foundation and its ecosystem Marsh. >>Welcome back to the cube here in San Diego for cube con cloud native con 2019. It's our fourth year of doing the cube here. I'm Stu Miniman. It's my fourth time I've done this show. Joining me is Justin Warren. He's actually been to more of the coupons than the cube has, I think at least in North America. And welcome into the program to two veterans of these events from pure storage. Uh, sitting to my right is she'll be uh, Shrivastava who's a director of product marketing and sitting to her right is Anthony lay Ferrario who's a senior product manager, uh, both of you with pure storage. Thank you so much for joining us. Thanks for having us. All right, so, so we, we were kind of joking about veterans here because we know that things are moving faster and faster. You both work for storage companies. Storage is not known to be the fastest moving industry. Um, it's been fascinating for me to watch kind of things picking up the pace of change, especially when you talk about, uh, you know, how developers and you know, software and a multicloud environment, a fit-out. So she'll be maybe, you know, give us a frame for, you know, you, you know, you're in a Cooper ladies tee shirt here pures at the show. How should we be thinking about pure in this ecosystem? >>Sure. Yeah. So, uh, you're, as, you know, we, we side off as all flash on brand storage company, uh, 10 years ago and, uh, we've kept pace with constantly innovating and making sure we're meeting our customer's needs. One of the areas of course that we see a lot of enterprises moving today is two words, microservices, two words, containerized applications. And our goal that you're really is to help customers modernize, modernize their applications while still keeping that store it's seamless and keeping that, uh, invisible to the application developers. >> I think it actually lines up really well if you're do just a pure sort of steam across time has been performance with simplicity. Right? And I think the simplicity argument starts to mean something different over time, but it's a place that we still want to really focus as our customers started to use, uh, try to containerize our applications. >>There are couple of challenges. We saw continued environments, of course, they're known for their, uh, agility, uh, how portable they are. They're lightweight and they're fast. And when they're fast, storage can sometimes be a bottleneck because your storage might not necessarily scale as fast. It might not be able to provision storage volumes as fast, your container environment. And that's the challenge that we at pure why to solve with our Cuban eighties integrations. Anthony, you mentioned simplicity there. So I'm going to challenge you a bit on that because Kubernetes is generally not perceived as being particularly simple and the storage interfaces as well, like stateful sets is kind of only really stabilized over the last 18 months. So how >>is pure actually helping to make the Cuban Eddie's experience simpler for developers? Yeah, and you know, you're totally right. I don't think I was necessarily saying that someone looking for the simplest thing that could ever find would adopt Kubernetes and expect to find that. But what I really meant was, you know, on one hand you have, you know, your more traditional enterprise infrastructure type folks who are trying to build out the underlying private cloud that you're going to deploy, you know, your infrastructure on. And on the other hand, you have your developers, you have your Kubernetes, you have your cloud native applications, right? And really the interface between those is where I'm looking at that simplicity argument because traditionally pure has focused on that simple interface to the end user. But the end user, as we were talking about before, the show has shifted from a person to being a machine, right? >>And the objective for pure and what we're building on the cognitive side is how do we take that simple sort of as a service consumption experience and present that on top of what looks like a traditional infrastructure platform. So I can get more into the, the details of that if you'd like, but really that that layer is where we're focused on the simplicity and really just asking the, the, uh, the end user as few questions as we can. Right. I just want to ask you, what do you need? I don't want to ask you, well, tell me about the, you know, IQN and blah, blah. They don't want that, right? That's the simplicity I'm talking about. Yeah. Well, you run developers generally, I mean, the idea of dev ops and I challenge people whenever they mentioned dev ops, and I'm hearing a pretty consistent message that developers really don't care about infrastructure and don't want to have anything to do with it at all. >>So if you can just bake it into the system and somehow make it easier to operate it, that kind of SRE level, that infrastructure level that, that Kubernetes as a platform. So once that's solved, then as a developer, I can just get on with, with writing some code. We definitely want stories to be invisible. Yeah. So if you want, but if they want stories to be invisible, that's not so great for your brand because you actually want them to know and care about having a particular storage platform. So how do you, how do you balance that idea that we want to show you that we can have to have innovative products that you care about the storage, but you also don't need to care about the storage at all because we'll make it invisible. How does that work? >>So Coupa storage for container environments has been a challenge. And what we are trying to educate the platform level users is that with the right kind of storage, it can actually be easy stores. For QA, these can be easy. And, uh, the way we make it simple or invisible is through the automation that we provide. So pure service orchestrator is our, uh, automation for storage delivery into the containerized environments. And so it's delivered to a CSI plugin, but we tried to do a little more than just develop a plugin into your Cubanetis environments. We tried to make your scalability seamless, so it's super easy to add new storage. And, um, so yeah, I think because a container environments were initially developed for States, less applications when became to staple applications, they still think about, Oh, why should I care about storage? But people are slowly realizing that we need care about it because we don't want to ultimately be bothered by it. Right. >>And if I can make, if I can make a point to just tag on to that I, the conversations I've had at the show this week, I've even helped me sort of crystallize the way I like to explain this to people, which is at first, you know, a lot of people will say, Oh, I don't, I don't do stateful application. I'm doing stateless applications and competitors. And my response is, okay, I understand that you've decided to externalize the state of your system from your Kubernetes deployment. But at some point you have to deal with state. Now, whether that's an Oracle database, you happen to be calling out to outside of your community's cluster, whether that's a service from a public cloud like S3 or whether that's deciding to internalize that state into Coobernetti's and manage it through the same management plane you have to have state. >>Now when we talk about, you know, what we're doing in PSO and why that's valuable and why, you know, to your point about the brand, I don't necessarily worry is because when we can give a seamless experience at the developer layer and we can give the SRE or the cluster manager layer a way where they can have a trusted high performance, high availability storage platform that their developers consume without knowing or worrying about it. And then as we look into the future, how do we handle cross cluster and multi-cloud stateful workloads, we can really add value there. >>Well, yeah, and I'm glad you brought up the multi-cloud piece of it because one of the more interesting things I saw from pure this year is how pure is putting in software cloud native. Um, so when I saw that one of the questions like, okay, when I come to a show like this, how does Kubernetes and containers fit into that old discussion? So how help us connect the dots as to what was announced and everything else that's happening. >>You've heard about cloud block store, which is our software running on the AWS cloud today. And uh, that's basically what we've done is we've people have loved flash array all these years for the simplicity it provides for the automation and performance. You want to give you something similar and something enterprise grade in the public cloud. The cloud, Luxor is basically, you can think of it as a virtual flash array and on the AWS cloud. So with that, you now have D duplication, 10 provisioning capabilities in the cloud. You can, um, be brought an active cluster, which is active, active, synchronous replication between availability zones. So really making your AWS environments ready for mission critical applications. Plus with our, you know, PSO just works the same way on prem as in the cloud. So it's just great for hybrid application mobility. You have the same APIs. >>Yeah, it's actually very cool. Right? One of the, one of the, you know, fun things for me as a software developer at pure, at a software side guy at pure, um, is that the API's that our arrays have are the same API. It's actually the same underlying software version even though it's a totally different hardware, hardware back end implementation. When we run in a cloud native form factor versus when we run in a physical appliance form factor, the replication engines work between the two snapshots, clones. Um, our ability to do instant, um, restores like everything that we do and that has brought value from our, our storage software stack, we still get access to in a cloud native environment and the transports as well. I guess trying to understand, is there Kubernetes involved here or is this just natively in AWS? And then then on premises itself is a, >> is a compute orchestration layer component. So when I look at Kubernetes, I'd say Kubernetes sits above both sides, right? Or potentially above and across both sides, um, depending on how you decide to structure your environment. But the nice part is if you've developed a cloud native application, right, and that's running on Kubernetes, the ability to support that with the same storage interfaces, the same SLS, move it efficiently, copy it efficiently and do that on whatever cloud you care to do. That's where it gets really cool. >>So we developed this really cool demo where you have a container application running on PSO, on flash array, on prem. We migrated that to cloud block store and on AWS and it just runs, you use the same yanno scripts in both places. There is no need to, you know, do a massive rearchitecture anything. Your application just runs when you move it. And we take care of all the data mobility with our asynchronous replications, you can take a snapshot on prem, you can snap it out into AWS, restore it back into cloud block store. So it really opens up a lot of new use cases and make them simple for customers >>that that idea of write once run anywhere. I said I'm, I'm old enough to remember when Java was a brand new thing and that was the promise. And it never quite got there because it turns out it's really, really hard to do that. Um, but we are seeing for from pure and from a lot of vendors here at the show that there's a lot of work and effort being put in into that difficult problem so that other people don't have to care about it. So you're building that abstraction in and, and working on how this particular, how the details of this work. And, uh, I was fortunate enough to get a deep dive into the end of the architecture of cloud Brock's door, just a recent accelerate conference and the way you've actually used cloud resources as if they were kind of infrastructure components and then built the abstraction on top of it, but in the same way that it runs on site, it, that's what gives you that ability to, to keep everything the same and make it simple, is doing a lot of hard work and hard engineering underneath so that no one has to care anymore. >>Yeah. And the way we've architected CloudLock store is that, you know, be as use the highest performance performing, uh, AWS infrastructure. And the highest durability it this infrastructure. So you're actually now able to buy performance and, and durability in one through one single virtual appliance as you would. >>Yeah. How's the adoption of the products going? I know it was, it was very early when it was announced just a few months ago. So what's the feedback from customers been so far about? >>It's been really positive and actually, you know, the one use case that I want to highlight really most is actually dev ops use cases, right? This, the value add of being able to have the same deployment for that application for a test or dev infrastructure in one cloud versus a production to point them in another cloud has been very exciting for folks. So, you know, when you think about that use case in particular, right? The ability to say, okay, I'm coming up to a major quarterly release or whatever I have for my product, I need to establish a bunch more test environments. I don't necessarily want to have bought that and we're not necessarily talking about, you know, bursting over the wire anymore. Right. We're talking about local, uh, local storage under the same interfaces in the cloud that you choose to spin up all of those test environments. So cases like that are pretty interesting for folks. >>Yeah. I think that's how people have started to realize that it's that operation side of things. It's not even day to day 90 and day 147 where I want to be operating this in the same place in the same way no matter where it is because it just saves me so much heartache and time of not having to re implement differently and I don't have to retrain my resources because it all looks the same. So, uh, yeah, Def does definitely have a big use case migration through verbose. That's another use case that we are seeing a lot of customers interested in and uh, disaster recovery, using it as a disaster recovery. How do you, so you can efficiently store backups on Amazon S three, but how do you do an easy fast restore to actually run your applications there? So with CloudLock store, it is now possible to do that, to do a fast, easy restore. Also a couple of weeks ago actually, we started taking registrations for a beta program for cloud Glocks or for Azure as well. Uh, yup. Customers are going multi-cloud. We are going multi-cloud with them. >>Great. I want to give you both a final word, uh, takeaways for a pure storage participation here at the show. >>I think the biggest thing that I, that I want people to understand, and I actually gave this talk at the cloud native storage day on day zero is that cloud native storage is an approach to storage. There's not a location for storage. And I think pure storage that really defines to me the way we're going about this, we're trying to be cloud native storage wherever you need it. So that's, that's really the takeaway I'd like people to have about pure >>and cute and storage for Cuban. It is, doesn't have to be hard. We are here all day today as well. So, um, I mean this is a challenge the industry seeing today and uh, we have a solution to solve that for you. >>All right, well that's a, that's a bold statement, uh, to help end us as Shilpi. Anthony, thank you so much for joining us for Justin Warren. I'm Stu Miniman back with more coverage here from cube con cloud native con 2019 stay classy, San Diego. And thanks for watching the queue.

from the cube studios in palo alto in boston bringing you data-driven insights from the cube and etr this is breaking analysis with dave vellante by our estimates aws will generate around nine billion dollars in storage revenue this year and is now the second largest supplier of enterprise storage behind dell we believe aws storage revenue will hit 11 billion in 2022 and continue to outpace on-prem storage growth by more than a thousand basis points for the next three to four years at its third annual storage day event aws signaled a continued drive to think differently about data storage and transform the way customers migrate manage and add value to their data over the next decade hello and welcome to this week's wikibon cube insights powered by etr in this breaking analysis we'll give you a brief overview of what we learned at aws's storage day share our assessment of the big announcement of the day a deal with netapp to run ontap natively in the cloud as a managed service and we'll share some new data on how we see the market evolving with aws executive perspectives on its strategy how it thinks about hybrid and where it fits into the emerging data mesh conversation let's start with a snapshot of the announcements made at storage day now as with most aws events this one had a number of announcements and introduced them at a pace that was predictably fast and oftentimes hard to follow here's a quick list of most of them with some comments on each the big big news is the announcement with netapp netapp and aws have engineered a solution which ports the rich netapp stack onto aws and will be delivered as a fully managed service this is a big deal because previously customers either had they had to make a trade-off they had a settle for cloud-based file service with less functionality than you could get with netapp on-prem or it had to lose the agility and elasticity of the cloud and the whole pay-by-the-drink model now customers can get access to a fully functional netapp stack with services like data reduction snaps clones the full multi-protocol support replication all the services ontap delivers in the cloud as a managed service through the aws console our estimate is that 80 of the data on-prem is stored in file format and that's not the revenue but that's the data and we all know about s3 object storage but the biggest market from a capacity standpoint is file storage you know this announcement reminds us quite a bit of the vmware cloud on aws deal but applied to storage netapp's aunt anthony lai told me dave this is bigger and we're going to come back to that in a moment aws announced s3 multi-region access points it's a service that optimizes storage performance it takes into account latency network congestion and the location of data copies to deliver data via the best route to ensure our best performance this is something we've talked about for quite some time using metadata to optimize that that access aws also announced improvements to s3 tiering where it will no longer charge for small objects of less than 128k so for example customers won't be charged for most metadata and other smaller objects remember aws years ago hired a bunch of emc engineers and those guys built a lot of tiering functionality into their boxes and we'll come back to that later in this episode aws also announced backup and monitoring tools to ensure backups are in compliance with regulations and corporate edicts this frankly is table stakes and was was overdue in my view aws also made a number of other announcements that have been well covered in the press around block storage and simplified data migration tools so we'll leave that to your perusal through other outlets i want to come back to the big picture on the market dynamics now as we've reported in previous breaking analysis segments aws storage revenue is on a path to 10 billion dollars we reported this last year this chart puts the market in context it shows our estimates for worldwide enterprise storage revenue in the calendar year 2021. this data is meant to include all storage revenue including primary secondary and archival storage and related maintenance services dell is the leader in the 60 billion market with aws now hot on its tail with 15 of the market in terms of the way we've cut it now in the pre-cloud days customers would tell us our storage strategy is the following we buy emc for block and netapp for file keeping it simple while remnants of this past habit continue the market is definitely changing as you can see here the companies highlighted in red represent the growing hyperscaler presence and you can see in the pi on the right they now account for around 25 percent of the market and they're growing much much faster than the on-prem vendors well over that thousand basis points when you combine them all a couple of other things to note in the data we're excluding kindrel from ibm's figures that's ibm spinout but including our estimates of storage software for example spectrums protect that is sold as part of the ibm cloud but not reported in ibm's income statement by the way pre-kindred spin ibm storage business we believe would approach the size of netapp's business now in the yellow we've highlighted the portion of hyper-converged that comprises storage this includes vmware nutanix cisco and others vmware and nutanix are the largest hci players but in total the storage piece of that market is less than two billion okay so the way to look at this market is changing traditional on-prem is vying for budgets with cloud storage services which are rapidly gaining presence in the market and we're seeing the on-prem piece evolve of course into as a service models with hpe's green lake dell's apex and other on-prem cloud-like models now let's come back to the netapp aws deal netapp as we know is the gold standard for file services they've been the market leader for a long long time and other than pure which is considerably smaller netapp is the one company that consistently was able to beat emc in the market emc developed its its nas business and developed on its own nasdaq and it bought isilon to compete with netapp with isilon's excellent global file system but generally netapp remains the best file storage company today now emerging disruptors like cumulo vast weka they would take issue with this statement and rightly so as they have really promising technology but netapp remains the king of the file hill you can't debate that now netapp however has had some serious headwinds as the largest independent storage player as seen in this etr chart the data shows a nine-year view of netapp's presence in the etr survey presence is referred to by etr as market share it's not traditional market share it measures the pervasiveness of responses in the etr survey over a thousand customers each quarter so the percentage of mentions essentially that netapp is getting and you can see well netapp remains a leader it has had a difficult time expanding its tam and it's become frankly less relevant in the eye in the grand scheme and the grand eyes of it buyers the company hit headwinds when it began migrating its base to ontap 8 and was late riding a number of new waves including flash but generally it is recovered from those headwinds and it's really now focused on the cloud opportunity opportunity as evidenced by this deal with aws now as i said earlier netapp evp anthony lai told me that this deal is bigger than vmware cloud on aws like me you may be wondering how can that be vmware is the leader in the data center it has half a million customers its deal with aws has been a tremendous success as seen in this etr chart the data here shows spending momentum or net score from when vmware cloud on aws was picked up in the etr surveys with a meaningful n which today is approaching 100 responses in the survey the yellow line is there for context it's vmware's overall business so repeat it buyers who responded vmware versus specifically vmware cloud on aws so you see vmware overall has a huge presence in the survey more than 600 n the red line is vmware cloud on aws and that red dotted line you see that that's that's my magic 40 mark anything above that line we consider elevated net score or spending velocity and while we saw some deceleration earlier this year in that line that top line for vmware cloud vmware cloud and aws has been consistently showing well in the survey well above that 40 percent line so could this netapp deal be bigger than vmware cloud on aws well probably not in our view but we like the strategy of netapp going cloud native on aws and aws's commitment to deliver this as a managed service now where could get interesting is across clouds in other words if netapp can take a page out of snowflake and build an abstraction layer that hides the underlying complexity of not only the aws cloud but also gcp and azure where you log into the netapp cloud netapp data cloud if you will just go ahead and steal steal it from snowflake and then netapp optimizes your on-prem your aws your azure and or your gcp file storage we see that as a winning strategy that could dramatically expand netapp's tam politically it may not sit well with aws but so what netapp has to go multi-cloud to expand that tam when the vmware deal was announced many people felt it was a one-way street where all the benefit would eventually accrue to aws in reality this has certainly been a near-term winner for aws and vmware and of course importantly vmware and aws join customers now longer term it's going to clearly be a win for aws because it gets access to vmware's customer base but we also think it will serve vmware well because it gives the company a clear and concise cloud strategy especially if it can go across clouds and eventually get to the edge so with this netapp aws deal will it be as big probably not in our view but it is big netapp in our view just leapfrogged the competition because of the deep engineering commitment aws has made this isn't a marketplace deal it's a native managed service and we think that's pretty huge okay we're going to close with a few thoughts on aws storage strategy and some other thoughts on hybrid talk about capturing mission critical workloads and where aws fits in the overall data mesh conversation which is one of our favorite topics first let's talk about aws's storage strategy overall as with other services aws approach is to give builders access to tools at a very granular level that means it does mean a lot of apis and access to primitives that are essentially building blocks while this may require greater developer skills it also allows aws to get to market quickly and add functionality faster than the competition enterprises however where they will pay up for solutions so this leaves some nice white space for partners and also competitors and especially the on-prem folks but let's hear from an aws executive i spoke to milan thompson bucheveck an aws vp on the cube and asked her to describe aws's storage strategy here's what she said play the clip we are dynamically and constantly evolving our aws storage services based on what the application and the customer want that is fundamentally what we do every day we talked a little bit about those deployments that are happening right now dave that is something that idea of constant dynamic evolution just can't be replicated by on-premises where you buy a box and it sits in your data center for three or more years and what's unique about us among the cloud services is again that perspective of the 15 years where we are building applications in ways that are unique because we have more customers and we have more customers doing more things so you know i i've said this before uh it's all about speed of innovation dave time and change wait for no one and if you're a business and you're trying to transform your business and base it on a set of technologies that change rapidly you have to use aws services i mean if you look at some of the launches that we talk about today and you think about s3's multi-region access points that's a fundamental change for customers that want to store copies of their data in any number of different regions and get a 60 performance improvement by leveraging the technology that we've built up over over time the the ability for us to route to intelligently router requests across our network that and fsx for netapp ontap nobody else has these capabilities today and it's because we are at the forefront of talking to different customers and that dynamic evolution of storage that's the core of our strategy so as you hear and can see by milan's statements how these guys think outside the box mentality at the end of the day customers want rock solid storage that's dirt cheap and lightning fast they always have and they always will but what i'm hearing from aws is they think about delivering these capabilities in the broader context of an application or a business think deeper business integration not the traditional suppliers don't think about that as well but the services mentality the cloud services mentality is different than dropping off a box at a loading dock turning it over to a professional services organization and then moving on to the next deal now i also had a chance to speak with wayne dusso he's another aws vp in the storage group wayne do so is a long time tech athlete for years he was responsible for building storage arrays at emc aws as i said hired a bunch of emcs years ago and those guys did a lot of tiered storage so i asked wayne what's the difference in mentality when you're building boxes versus cloud services here's what he said you have physical constraints you have to worry about the physical resources on that device for the life of that device which is years think about what changes in three or five years think about the last two years alone and what's changed can you imagine having being constrained by only uh having boxes available to you during this last two years versus having the cloud and being able to expand or contract based on your business needs that would be really tough right and it has been tough and that's why we've seen customers from every industry accelerate uh their use of the cloud during these last two years so i get that so what's your mindset when you're building storage services and data services so so each of the surfaces that we have in object block file movement services data services each of them provides very specific customer value in each are deeply integrated with the rest of aws so that when you need object services you start using them the integrations come along with you when if you're using traditional block we talked about ebs io2 block express when using file just the example alone today with ontap you know you get to use what you need when you need it and the way that you're used to using it without any concern so so the big difference is no constraints in the box but lots of opportunities to blend in with other services now all that said there are cases where the box is gonna win because of locality and and physics and latency issues you know particularly where latency is king that's where a box is gonna be advantageous and we'll come back to that in a bit okay but what about hybrid how does aws think about hybrid and on-prem here's my take and then let's hear from milan again the cloud is expanding it's moving out to the edge and aws looks at the data center as just another edge node and it's bringing its infrastructure as code mentality to that edge and of course to data centers so if aws is truly customer centric which we believe it is it will naturally have to accommodate on-prem use cases and it is doing just that here's how milan thompson-bucheveck explained how aws is thinking about hybrid roll the clip for us dave it always comes back to what the customer is asking for and we were talking to customers and they were talking about their edge and what they wanted to do with it we said how are we going to help and so if i just take s3 for outposts as an example or ebs and outposts you know we have customers like morningstar and morningstar wants outposts because they are using it as a step in their journey to being on the cloud if you take a customer like first adudabi bank they're using outposts because they need data residency for their compliance requirements and then we have other customers that are using outposts to help like dish networks as an example to place the storage as close as account to the applications for low latency all of those are customer driven requirements for their architecture for us dave we think in the fullness of time every customer and all applications are going to be on the cloud because it makes sense and those businesses need that speed of innovation but when we build things like our announcement today of fxs for netapp ontap we build them because customers asked us to help them with their journey to the cloud just like we built s3 and evs for outposts for the same reason so look this is a case where the box or the appliance wins latency matters as we said and aws gets that this is where matt baker of dell is right it's not a zero-sum game this is especially accurate as it pertains to the cloud versus on-prem discussion but a budget dollar is a budget dollar and the dollar can't go to two places so the battle will come down to who has the best solution the best relationships and who can deliver the most rock solid storage at the lowest cost and highest performance let's take a look at mission critical workloads for a second we're seeing aws go after these it's doing a database it's doing it with block storage we're talking about oracle sap microsoft sql server db2 that kind of stuff high volume oltp transactions mission critical work now there's no doubt that aws is picking up a lot of low hanging fruit with business critical workloads but the really hard to move work isn't going without a fight frankly it's not going that fast aws and mace has made some improvements to block storage to remove some of the challenges related but generally we see this is a very long road ahead for aws and other cloud suppliers oracle is the king of mission critical work along with ibm mainframes and those infrastructures generally it's not easy to move to the cloud it's too risky it's too expensive and the business case oftentimes isn't there because very frequently you have to freeze applications to do so what generally what people are doing is they're building an abstraction layer over that putting that abstraction layer maybe in the cloud building new apps that can connect to the back end and the into the cloud but that back end is largely cemented and fossilized look it's all in the definition no doubt there's plenty of mission critical work that is going to move but just really depends on how you define it even aws struggles to move its most critical transaction systems off of oracle but we'll continue to keep an open mind there it's just that today we define the most mission-critical workloads as we define them we don't see a lot of movement to the hyperscale clouds and we're going to close with some thoughts on data mesh so one of our favorite topics we've written extensively about this and interviewed and are collaborating with jamaa dagani who has coined the term and we've announced a media collaboration with the data mesh community and believe it's a strong direction for the industry so we wanted to understand how aws thinks about data mesh and where it fits in the conversation here's what milan had to say about that play the clip we have customers today that are taking the data mesh architectures and implementing them with aws services and dave i want to go back to the start of amazon when amazon first began we grew because the amazon technologies were built in microservices fundamentally a data match is about separation or abstraction of what individual components do and so if i look at data mesh really you're talking about two things you're talking about separating the data storage and the characteristics of data from the data services that interact and operate on that storage and with data mesh it's all about making sure that the businesses the decentralized business model can work with that data now our aws customers are putting their storage in a centralized place because it's easier to track it's easier to view compliance and it's easier to predict growth and control costs but we started with building blocks and we deliberately built our storage services separate from our data services so we have data services like lake formation and glue we have a number of these data services that our customers are using to build that customized data mesh on top of that centralized storage so really it's about at the end of the day speed it's about innovation it's about making sure that you can decentralize and separate your data services from your storage so businesses can go faster so it's very true that aws has customers that are implementing data mess data mesh data mess data mesh can be a data mess if you don't do it right jpmorgan chase is a firm that is doing that we've we've covered that they've got a great video out there check out the breaking analysis archive you'll see that hellofresh has also initiated a data mesh architecture in the cloud and several others are starting to pop up i think the point is the issues and challenges around data mesh are more organizational and process related and less focused on the technology platform look data by its very nature is decentralized so when mylan talks about customers building on centralized storage that's a logical view of the storage but not necessarily physically centralized it may be in a in a hybrid device it may be a copy that lives outside of that same physical location this is an important point as jpmorgan chase pointed out the data mesh must accommodate data products and services that are in the cloud and also on-prem it's got to be inclusive the data mesh looks at the data store as a node on the data mesh it shouldn't be confined by the technology whether it's a data warehouse a data hub a data mart or an s3 bucket so i would say this while people think of the cloud as a centralized walled garden and in many respects it is that very same cloud is expanding into a massively distributed architecture and that fits with the data mesh architectural model as i say the big challenges of data mesh are less technical and more cultural and we're super excited to see how data mesh plays out over time and we're really excited to be part of part of the the community and a media partner of the data mesh community okay that's it for now remember i publish each week on wikibon.com and siliconangle.com and these episodes they're all available as podcasts all you do is search for breaking analysis podcasts you can always connect on twitter i'm at d vellante or email me at david.velante at siliconangle.com i appreciate the comments you guys make on linkedin and don't forget to check out etr.plus for all the survey action this is dave vellante for the cube insights powered by etr be well and we'll see you next time [Music] you

>>Lai from Orlando, Florida. It's the cube covering Microsoft ignite brought to you by Cohesity. >>Good afternoon, cube viewers. We are here at Microsoft ignite at the orange County convention center. I'm your host, Rebecca Knight. Along with my cohost Stu Miniman. We're joined by Edward Thompson. He is the product manager at get hub. Thank you so much for coming on the queue. So the get hub acquisition closed this time last year, uh, for our viewers who are maybe unfamiliar with get hub, explain what get hub is and then also tell us a little bit how it's going since the, >>yeah, I'd be happy to. So yeah, get hub is like the home for software development. If you're a, if you're a software developer, uh, you know, get hub rehost, you know, most of the open source repositories in the world. Um, you know, just to give you some stats. So at this time, last year, about the time the acquisition happened, um, we announced ad get hub universe, which is our annual developer conference, uh, that we had 30 million developers on GitHub and a hundred million repositories. So that's, that's a huge number of developers. I haven't seen the latest numbers. We'll announce the newest, uh, at get hub university this year, which is coming up next week. Uh, but the last number I saw was 40 million developers. So that's a growth of, you know, 10 million developers in just a year. Unbelievable. And that, that also means the 25% of our developers on get hub have joined within the last year. So that's just absolutely incredible. Um, and so yeah, I get hope. Is, is, is that, is that place for development? >>Yeah, it's really interesting when I look at some acquisitions that Microsoft has made back in 2016, they spent $26 billion for LinkedIn, which is most people's resume. And if you look last year it was seven and a half billion dollars for my friends in the software world. Get hub is their resume. That's right. Oh, when you talk about how you do things online, so you've got an interesting perspective on this because you've worked for Microsoft and get hub a couple of times. So give us a little bit about, you know, the relationship when you joined Microsoft 10 years ago, you know, open source developers, developers, developers weren't exactly on everyone's lips. So it gives a little bit of viewpoint through the various incarnations. >>So as you said, I joined Microsoft about 10 years ago. I came in through a little acquisition. Uh, we were just a very small software company, but we were building enterprise cross platform developer tools and we were about five engineers. And when you're building for, you know, Mac OS, Linux, Sonos, all these different platforms you use with so many people with so few rather, so few developers, you really need to take as much off the shelf as possible. You can't build all that yourself, you know. So if, if you needed a logging library, we would just go and use some open source products. We're not going to spend our time working on that when we could be building customer value in step. So when Microsoft acquired that company, they looked at, you know, they did their due diligence, they looked at the source code and they saw all this open source and they, I mean it was almost a deal breaker. >>They really lost their mind. Um, they were not geared up to deal with open source, to use open source, certainly not to contribute to open source. Uh, and so that's the Microsoft that I first saw. And, and to get from there to here is, is incredible. You know, over time. Um, we worked closely with some open source tools. We worked closely with get hub at Microsoft and that was really one of the early sort of unions between Microsoft and get hub was starting to work together on, on some open source software. And so we kind of started to know each other. We started to understand each other's companies and each other's cultures. And we started to, I don't know, I dare say like each other. Like I still count some of those early get hub employees that I met, uh, as some of my closest friends. Uh, and so at some point, uh, they became such close friends that I went to go work with them and get hub and then of course the Microsoft acquisition and so on. But I really think that that, you know, the, the transformation in Microsoft between, uh, the 10 years ago, Microsoft that really didn't get open source and today is, is just incredible. >>Well, let me just sit in that, in that culture and maybe culture clash a little bit the first time around because Microsoft developers have their own culture and their own uniform and their own way of interacting with each other. The, the, the hours that they work, which is very different from Microsoft, which is a pretty middle-aged Volvo driving kind of organization. So how, how does that work and, and what is, what has it been like the second time around the Microsoft as a middle aged Volvo driver? I think you can, you can >>wear a hoodie in and drive a Volvo. Um, no, I think it's been, I think it's been really great. The interesting thing about Microsoft is that it's not, you know, with so many people, it's not just like a homogenous big company. Um, we do have, you know, the developer tools division is a little bit different than offices, a little bit different than windows. And so they all have their own sort of unique cultures and, and now get hub slots in as its own unique culture. And we can, you know, we can talk to each other and we can understand each other, but we don't necessarily have to be all the same, you know, we can get hub team does kind of work some, some of us do work kind of weird hours. And, and I think that somehow that that works, especially with, you know, new tools coming to, um, coming to the marketplace, uh, you know, chat applications, we can be a lot less synchronous. We can be a lot more online and leave a message for each other. You know, we get out, we use get hub issues and pull requests to collaborate on almost everything, whether it's legal, uh, or, you know, our, our PR department. And it's not just developers. So we're trying to take these, these tools and, and sort of apply them to allow us to have the culture that we want at get hub. And I think Microsoft's doing the same thing as well. >>So speaking of new tools and you're, you're speaking here at ignite, you're about to announce the new repository with lots of new capabilities, enabling users to deploy at to any cloud. So tell us a little bit about, about the, this new tool. >>Yeah, so, uh, we announced, we call it get hub actions. We announced it last year at, at get hub universe. Our, uh, again, our, our annual developer conference. And our goal with GitHub actions was to allow people to take, you know, we've got 100 million repositories on get hub. We wanted our users to, to take those repositories and automate common tasks. Let me, let me give you a concrete example. Um, a lot of times somebody will open an issue on a, on a good hub repository, you know, uh, Hey, this doesn't work. I've got a bug report, you know, and they'll fill out an issue. And often either they didn't understand things or, um, the issue resolved itself, you know, who knows. We call that, uh, an issue that goes stale. And so you can build a workflow around that repository that will look for these stale issues and it will, uh, you know, just close them automatically. >>That gets rid of the mental tacks for somebody who, for a, for a developer who owns this repository to allow this, you know, this workload to just do it automatically. And so that's an example of a, a get hub actions workflow. Um, some people, uh, don't like swearing in their repository and you know, so if somebody were to open a bug report, you know, they might be angry. And so you could actually have a get hub workflow that looks for certain words and then replies and says, Hey, that's, here's our code of conduct. That's not the way we roll here. And actually a lot of people find that that feedback coming from a robot, uh, is a lot easier to take than a feedback coming from a human cause. They might want to meet with a person, can't argue with a robot. Well, not successfully. >>I think I have argued with the chat bot in my day. But anyway, >>yeah. So that's what we did a year ago and we opened it up into the beta program and we really quickly got feedback that, that people liked it and people were doing some really innovative things. But the one thing that people really wanted to automate was their bills. They wanted it to be able to build their code and deploy it. And we were just not set up for that. We, we, we didn't build, get hub actions as that platform in 2018 so we kind of had to pause our beta program. You know, I, they, they, they say that no, uh, no good plan survives first contact with the customer. So we had to, we had to hit pause on that. Uh, and we retooled. Um, we, we just sort of, I don't know, iterated on it, I guess. Uh, and we basically built a new platform that supported all of that repository automation capability that we had planned for in the first place. But also allowed for continuous integration build and deployments. So, um, we brought Macko S we brought Linux and windows runners, uh, that we host, uh, in our cloud, um, that people can use to build their software and then deploy it. And again, yeah, we want to be absolutely a tool agnostic. So any, any operating system, any, uh, language and cloud agnostic, we want to let anybody deploy anywhere, whether it's to a public cloud or on premises. >>Yeah. Uh, so, and with this, the second year we've done our program at this show and we really feel it's gone through a transformation. You know, this is a multi decade in a windows office. Uh, the business applications, uh, you know, cloud seeped in, developers are all over the place here. The day two keynote was all about app dev. Um, I'd love to get a little compare and contrast as to, you know, what you see here at Microsoft ignite versus, and I guess what I would call a pure dev show next week. Get hub universe happening in San Francisco. >>It's true. Get up universe is pretty much a pure dev show. Um, we, we have fewer booths, we have smaller booths. Uh, but, uh, and, and honestly, we have fewer sort of, um, I don't know, enterprise sorta. It, it pro crowd is what we used to call them. Um, but we do of course have a lot of dev ops. So, you know, we get up university has a lot of developers, but, uh, we're seeing a lot of dev ops, so there's a lot of meeting in the middle because, you know, I started out my career as assistant man actually. So I remember just, you know, doing everything manually. Um, but that's not the way we do things anymore. We automate all of our, uh, automate, uh, deployments. We automate all of our builds. You know, I don't want to sit there and type something into a console cause I'm going to get it wrong. Um, you know, I've accidentally deleted config files on production servers and that's, that's no good. So I think that they're, uh, get up universe is very different. A to ignite, it's much smaller, it's more intimate, but at the same time, there's a lot of, uh, overlap, especially around dev ops. >>Yeah. Uh, Satya Nadella yesterday in the keynote talked about the citizen developer as a big push for Microsoft. He said 61% of job openings for developers are outside the tech sector. Um, w what do you see in that space? Uh, the different developer roles these days? >>Uh, I think it's, it's absolutely fascinating. When I, uh, when I started my career, you know, you were, you were a developer and you, and you wrote code probably at a development company. Um, but now like everybody is automating tools, everybody's adopting machine learning. Um, when I look around at some of my friends in finance, uh, it's not about, it's not about anything but tech anymore. That's th they're, they're putting technology into absolutely everything that they do to succeed. Uh, and I think that, I think that it's amazing. Um, uh, like I said earlier, uh, 25% of developers on get hub have joined within the last year. So it's clear that it's just exploding. Um, everybody is doing, uh, software now. Yeah. >>There's something for the citizen developer on get hub though. Or is it too high level? I think >>I don't think it's too high level. I think that, uh, I think that that's a great challenge that we need to really step up to. Yeah. So Edward, >>the other big themes we heard here is talking about trust. So, you know, we talked about how Microsoft is different today than it wasn't in past, but I'm curious what good hub seen because you know, in social media when the acquisition first happened, it was, wait, I love GoodHub hub, I love all those people, but Hey, get lab. Hey, some of these other things I'm, you know, I'm fleeing for the woods. And every time I've seen an open source company get bought by a public company, there's always that online backlash. What are you seeing? How has the community reacted over the last year? >>I understand that skepticism. Uh, you know, I would be skeptical of any, uh, sort of change really. I, you know, the, the whole notion of who moved my cheese. But I think that the only way that we can, we can counter that is just to prove ourselves. And I think that we have, I think that Microsoft has allowed get hub to operate independently. And I think that, you know, I think a lot of people expect it to all of a sudden everything to change. And I don't think everything did change. I think that, uh, get hub now has more resources than it used to to be able to tackle bigger and more challenging problems. I think that get hub, uh, now can hire more and, and, and deploy to more places. And so I really just think that we're just going to keep doing exactly what we've been doing just better. So I think it's great. >>So universe happening next week teed up a little bit for us. What are some of the most exciting things that you're looking forward to? What kinds of conversations that will you be having? Presentations? >>So the big one for me is, is actions. I've, I, I've been just completely heads down working on, on get hub actions. So I'm really excited to be able to put that out there and, and you know, finally give it to everybody. Cause you know, we've been in beta now. Uh, like I said, we've been in beta for a year, which sounds like a ridiculous amount of time. Uh, but you know, it, it did involve a lot of retooling and rethinking and, and iteration with our, our beta testers. Um, and so the biggest thing for me is, is talking to people about actions and showing what they can do with actions. I'm super excited about that, but we've got a lot of other interesting stuff. You know, we've done a lot in the last year since our last universe. We've done a lot in the security space. Um, we've done, uh, we've both built tools and we've acquired some. Um, and so we'll be talking about those, uh, get hood package registry, which goes along really well with get hub actions. Uh, I'm super excited about that too. But yeah, I mean my, my calendar is, is, is just booked. Um, it's great. So many people like want to want to sit down and talk that I'm, I'm super excited about it. >>Excellent. Well great note to end on Edgar Thompson. Thank you so much for coming on the queue. We appreciate it. Thank you. I'm Rebecca Knight. First two minutes, stay tuned for more of the cubes live coverage from Microsoft ignite.