>>from the Silicon Angle Media Office in Boston, Massachusetts. It's the cue. Here's your host Still, Minutemen >>Hi and welcome to the Boston area studio. Happy to welcome back two of our Cube alumni, both from Active e o Brian Regan, the C M O of the company. And it took Rommel. Who's the vice president and general manager of Cloud? Gentlemen, thanks so much for joining us. >>Happy New Year's too great to be here. >>Yeah, 2020 way we're talking about. We don't all have flying cars and some of these things, but there are a lot of exciting things and ever changing in the tech world. We're gonna talk a lot about N. C. Which, of course, is active use announcement. If I heard the sea, it's about clouds, about containers and about copy data management. With course, you know we know act as always quite well, Brian. Let's start with a company update first. Of course, you know, copy data management is where activity really created a category, but all of these new waves of technology that activity is fitting into Well, 2000 >>19 was an incredible year for us, you know, continued accelerating our growth in the market in the enterprise particularly, You know that the secular trends around hybrid and multi cloud really played well to our existing strengths. And 10 c really builds on those strengths will talk more about that. I know in a moment we also saw continued, you know, as digital transformation as as application modernization initiatives to cold. In just about every enterprise, our database capabilities really played again a cz a strength that we could capitalize on to land significant enterprise accounts, get started with them and then really start to expand overall data platform data management platform in those accounts >>s Oh, sure, before we get into the 10 see stuff specifically. But Brian, Brian teed up some of those cloud trends and how I think about data protection. Data management absolutely has changed. You know, I remember a couple years ago we said, Oh, well, you know, people are adopting all these clouds. All of these concerns still exist. You know. It doesn't go away. It's not magically Oh, I did office 3 65 I don't need to think about all the things that I thought about without. Look, when I do public cloud and build new applications. Oh, wait. You know, somebody needs to take care of that data. So bring us inside your customers. The team that's building these products and some of those big trends should >>happen. You're still so happy to be back in the Cube. So 2019 really defined. There were a lot of for enterprises really started moving. Production will look to the cloud multi cloud become a reality for active field way. We're running production workloads on seven o'clock platforms. So the key elements off being infrastructure agnostic wherein active you can do everything in all clark platforms. Basically, infrastructure neutral was a key element. On the other element was a single pane of glass. You could have an Oracle worker running on prime with the logic application running in azure and not know the difference. S o. The seamless mobility of data was the key element. That lot of our enterprises took advantage from elective standpoint on a lot of the 10 see capabilities adds onto those capabilities and you see more of these adoptions happening in 2020. So I think 10 seat eases up absolutely perfectly for that market. >>Yeah, let's talk a little bit about activities, place in the market, that differentiation there, that direct connection with the application and the partner's eyes. Real big piece of it. >>It's a huge piece and something we really not just double triple down on in 2019. Certainly for us our database capabilities, which we believe are really second to none in the industry, we continue to expand and enrich the capabilities, including ASAP Hana obviously already Oracle and sequel server D B two, as well as the linen space databases, the new and no sequel databases. We also understood, and as our customers were talking to us about their application modernization, they were moving Maur of their front and capabilities two containers, and they wanted that the data to come with it a t east temporarily on. So that was a big focus for us as well was making sure that we could bring the data whether it was into a V M, into a container into a physical server into any number of clouds in order to support that application. At that time, it was a critical part of our differentiation. For two dozen 1 19 >>I'd love just a little more on the database piece because you go to Amazon, reinvent and you know, the migrations of databases to the cloud, of course, is a major conversation. You look at Amazon, they have a whole number of their offerings as well, as if you want to use any database out there, they'll let you use it. Course Oracle might charge him or if you're doing it on the Amazon, the Amazon partner. The azure partnership with Oracle was big news in the back and 1/2 of 2019. So when you're working with their customers, you know, databases still central to you know how they run their business and one of the bigger expenses on the books, they're So you know what we look at 2020. You know, what is the landscape specifically from a database? Well, we continue >>to see and in most of our large enterprise accounts that Oracle and sequel servers continue to dominate the majority of the payload of databases. We don't see that changing, although we do see net new applications being built on new database platforms. Thio complement the oracle and sequel server back end. So we are seeing a rise of the bongos and the new and no Sequels out there. We're also seeing Maur consideration of building in the cloud, as opposed to starting on Prem and then potentially leveraging the cloud sort of post facto and in terms of the application architecture's. So our ability to support both the the legacy big iron database platforms as well as the new generation platforms, regardless of application architectural, regardless of the geometry of the application, is a big part of our differentiation >>going forward. >>All right, so let let's Wave hinted about it. But 10 c major announcement. Let's get into how that extends what we've been talking about. >>Absolutely so you know, we've made a lot of the new databases, particularly the no sequel databases, the Mongols and Hannah's first class citizens intensity, which means we understand not just the database. He also he also the ecosystem that the database lives. We all know Hannah's a fairly big database in terms of the number of machines that consumes number off, you know, applications that you use it and toe capture and actually provide value for Hannah. You need to understand where the Honda database lifts and so some of the capabilities we've added in 10 C's to kind of figure out this ecosystem, and when you migrate, you might need the ecosystem, not just the holiday. The peace because you know that is that is a key element. On the second aspect is the containers that that Brian touched on. Now we're seeing legacy data being presented into containers, and there's a bridge too quiet for that. Now. How do you present that bridge containers could be brought up, but they're lifeless unless you give them data. So the actors of bridge ready and you bring up the container using communities of whatever framework you have and be married the data into the container framework. So most organizations, you know, as they evolved from yesterday's architecture to today's architect. And they need this bridge, which helps them navigate that that my creation process and an active field being the data normalization platform is helping them live on both segments, Right? Nobody does us turn the switch off of the old one and move to the new That'll be co exist. That is the key element >>way spent a lot of time over the last couple of years hearing about cloud native architectures and that discussion of data, it is kind of something you need to kind of dig in to understand. I'm glad to hear you talking about, You know, when you talk about storage and container ization, you know where that fits today? Because originally it was only stateless. But now we know we could do state full environment here. But while container ization is, you know, growing at huge leaps and bounds, customers aren't taking their Oracle database and shoving Brian A lot of discussion about the partnerships. I think it was seven. You know, major cloud providers. That activity is there talk a little bit about the common native. The relationships with some >>of those partners? Absolutely. I mean, way made great strides from a go to market standpoint with our cloud partners this past year. Google Cloud is probably our most significant go to market partner. From a cloud standpoint, we've done a lot of joint engineering works in order to support both our existing, uh, software platform as well as our SAS control plane in the Google Cloud. We have landed many significant deals with with Google this past year on dhe. They have been as they continue to really increase their focus on enterprise accounts and both hybrid as well as public cloud sort of architectures. We are hand in glove with them as their backup in D R partner for those club >>workloads. >>Great eso We talked quite a bit about the database peace, but in general, back into the cloud archive in the cloud. What is 10 see specifically an active you, in general, enhance in those environments >>so tense he bring It brings in you know, the key elements of the recovery orchestration. So if I have to bring up, let's say, 500 machines in any club platform, how did I do it? Well, I can go and bring up one machine at a time and take two days to bring it up or with active fuels. Resiliency. Director. You can create a recovery plan and a push pardon Recovery happens, so we've seen a lot of customers adopt that, particularly customers that want to leverage the Google platform for its infrastructure capabilities. Wants an orchestration, that is, that is, that understands the applications that are coming up, so there is a significant benefit from a PR standpoint of the recovery orchestrations will be invested a lot of time and tuning the performance and understanding Google and Amazon and Azure to make sure this was built, right. The other big push we're seeing for the clock platforms ASAP, ASAP, as an enterprise has taken a mission to say, there's no more data centers. Everything is going to the cloud. So an escapee workloads are not the easiest were close to manage. And so they did the the intersection point of S A P and the cloud is very active. Field becomes really valuable because, though, did this data sets by definition or large, their complex and there were distributed. And the D artists of paramount importance because these air crown jewels So so those segments of the R orchestration forward with, you know ASAP and Hannah, which is to get our strength of databases. It's kind of their tense. He really hits, hits, hits a home run >>when we're talking to users in the discussion of multi Cloud in general, one of the challenges is Yoon hee. Different skill sets across. One of those powerful things I've heard from active use really is a normalization across any cloud or even in a cloud. Oh, wait. I was gonna stuck six up again in an archive. That means I'm never going to touch it again. Ingress and egress fees. You know, I have to figure these out or I need toe dedicated engineer to those kind of environments. So it seems that just fundamentally the architecture that you built it active eo is toe help customers really get their arms around those multi cloud >>environments? Absolutely. And I think there are two additional components that really one of which has lived with activity from the very beginning of the company, which is a p a p I. First, the cloud is very much an AP I centric type of operating model on with active fio We don't change the management system were operating model. But in fact we incorporate in eso all of this orchestration that it shook talked about can be actuated via a P I. The second piece, which we really started in 2017 with our eight Dato platform release, is the the consumption and the intelligent consumption of object with 10 see, we've continued to advance our object capabilities. In fact, we published a paper with the SG in late 2019 that talked about mounting 50 terabyte Oracle databases directly out of object with actually increased performance versus the production block >>storage behind it. >>So we have really with 10 C, actually added cashing to even further performance optimized object workloads, which speaks to both the flexibility but also the economic flexibility of being able. Thio contemplate running workloads in the cloud out of object at a lower cost platform without necessarily the compromise of performance that you would normally expect >>absolutely. And like you said, the skill set required. Do I need to put it in object to any reported in block? We can eliminate that right. Be neutralized that to say you want to leverage the cloud, give us your cost point and you can dial the cost up or down, depending on what you see for performance, and we will be the day that back and forth, so that flexibility is enormous for customers. >>That's greater if you talk to anybody that's been in the storage industry for a while, and you want to make them squirm, say the word migration s O. We know how painful it has been if you go talk to any of the triple vendors, they have so many tools and so many service is to help do that in a cloud era. It should be a little bit easier, but it sounds like that's another key piece. Intensity? >>Absolutely, absolutely. I mean, 10 See, you know, hits the home. I think with the A P. I integration. So the other element 2019 Saul, was the scale of deployment effective. You know, when you have to manage hundreds of thousands of machines across different geo's, that is a scale that comes to the data protection that you know, people. Really? You have a seat to actually build for it and and work with it and be sorry in 2019 and 10 See, incorporates a lot of that capabilities as well, making it ask Cloud needed as possible. So basically, around these applications globally. All >>right, uh, I was wondering if you might have a customer example toe really highlight the impact that NBC's having understand if you can't name them specifically, but, uh, yeah, >>well, actually, shook has already talked about 11 customer slash partner. Who is I think still the world's largest software company in the world based out of Germany. And they are powering their enterprise cloud on the data management data protection. Beneath that enterprise cloud across four different hyper scale er's using, active you on. I think they're on record in a weapon. Our earlier in December, talking about their evaluation of pretty much every technology out there on the one that could really deliver on performance at scale across clouds was activity >>on. The key element was they wanted a single platform with a single pane of glass across all platforms, and an active feel was the solution to each other. So >>and certainly I think we credit them and are the rest of our enterprise customers for pushing us to make 10 see more powerful and more a capable across any clout, you know, Ultimately, an inter enterprise is going to make a decision that they've probably already made the decision to incorporate cloud into their enterprise architecture. What we give them is the freedom and the flexibility to choose any cloud. And, by the way, any cloud today that might change tomorrow and having the ability to seamlessly migrate and or convert from cloud eight o'clock be. Is something that active powers as well? >>Yeah, just make sure we're clear as to what's happening there. It's great that you've got flexibility there when we're talking about data and data gravity. Of course, we're not talking about just lifting an entire database land, you know, ignoring the laws of physics there. But it's the flexibility of using a ll These various things, any way Talk about A S, A P, of course, needs to live across all these clouds. But when you talk about an enterprise, you know what is kind of that? That killer use case? Because we said we're not at a point where cloud is not a utility. I don't wake up in the morning and look at the sheet and say, Oh, I'm gonna, you know, use Cloud a versus cloud be s o. You know what is? You know the importance of that flexibility for us >>today. The majority of our business starts with company saying I need to deliver my data faster to my developers or my tester's, or even increasingly, my data scientists and analysts and my data sets have become so large that it's becoming increasingly difficult for me to do that with regularity. So the currency of the data is starting to suffer. That is the first use case for us and that that powering that enterprise transformational initiative around a new application or an updated application based on a historical app using those enterprise databases delivering that seamlessly quickly, regardless of how big the data is still remains our first use case. And then, increasingly, those customers air realizing that they can start to achieve the other benefits of active eo, including I can start to back that up to the cloud. Aiken actually orchestrate recoveries in the cloud. Not just bulk sort of transfer, but actually the entire application stack. And bring that up in the cloud. I can start Thio, take those those data sets and actually amount them into containers for my next generation application. So that starting point of give me my data as quickly as possible, regardless of how big it is, starts to become universal in terms of its applicability for all use cases. >>Yeah, I guess I shook. The last thing I wanna understand from you is in 2019. We saw a lot of large providers putting out their vision for how I manage in this multi cloud environment. You were at the Google Cloud event where Anthros was unveiled. I was at Microsoft ignite when as your ark was unveiled. VM wear has things like tans you out there. So this moldy cloud environment how do I manage across these disperse environments? What? What What are all those move mean to active you on how you look at things. >>And I think you know, the Tennessee release and with the core architecture that if you had in place, which was multiple already and a P I ready. So those are the two elements that are kind of building blocks that you can tie into any one of those construct you talked about. All right, so we've had we have customers, innovated us with Antos. If customers get up service now we have customers doing Vieira with us, right? So there are many, many integration platforms. The latest I saw was an Alexa app, but we were mounting an oracle database on a voice command. So So you know, there's endless possibilities as thes equal systems evolve because active feel stays behind the cowards powering the data delivering the data available if needed on the target. So that is the key element in the neighbor that we see that helps all these other platforms become super successful. >>So, Brian, it sounds very much a hell wind. The big trends that we're seeing here keep partnerships and, you know, meeting your customers where they need to >>pay. Absolutely. We continue Thio play in the enterprise market, where these thes are absolutely top of mind of every CEO and top of their agenda. Onda, we are working hand in glove with them to make sure that our platform not only anticipates their needs but delivers on their current state of needs as well. >>Brian, thank you so much. Congratulations on the 10 sea launch Cloud containers. Copy data management. Look forward to watching your customers and your continued Thanks. As always, Very much. All right, I'm still Minutemen. Lots more coverage here in 2020. Check out the cube dot net for all of it. And thank you for watching the Cube

>>from Las >>Vegas. It's the cues covering quality security Conference 2019 by quality. Hey, welcome back already, Jefe Rick here with the Cube were in Las Vegas at the Bellagio at the Kuala Security Conference. It's the 19th year they've been doing this. It's our first year here, and we're excited to be here. And it's great to have a veteran who's been in this space for so long to give a little bit more of historical perspective as to what happened in the past. Where we are now, what can we look forward to in the future? So coming right off its keynote is Felipe Quarto, the chairman and CEO of Qualities felt great. See, >>Thank you. Same. Same same for me. >>Absolutely. So you touched on so many great topics in your conversation about kind of the shifts of of modern computing, from the mainframe to the mini. We've heard it over and over and over. But the key message was really about architecture. If you don't have the right architecture, you can't have the right solution. How is the evolution of architects of architectures impacted your ability to deliver security solutions for your clients >>So no That's a very good question. And in fact, you know what happened is that we started in 1999 with the vision that we could use exactly like Salesforce. They'll come this nascent Internet technologies and apply that to security. And s and Marc Benioff applied that essentially changing the way serum was essentially used and deployed in enterprises and with a fantastic success as we know. So for us, the I can't say today that 19 years later the vision was right. It took a significant longer because the security people are not really, uh, warm at the idea of Senate Lee, uh, having the data interview which was in place that they could not control. And the i t people, they didn't really like a toll. The fact that certainly they were not in control anymore of the infrastructure. So whether a lot of resistance, I wever, we always I always believe, absolutely believe that the cloud will be the architecture to go back. A lot of people make the confusion That was part of the confusion that for people it was a cloud, that kind of magical things someplace would you don't know where and when I was trying to explain, and I've been saying that so many times that well, you need to look at the club like a computer that can architecture which distribute the computing power for more efficiently than the previous one, which was Clyde Server, which was distributing the computing power for better then, of course, the mainframes and minicomputers. And so if you look at their architecture's so the mainframe were essentially big data centers in in Fort Knox, like setting private lines of communication to damn terminal. And of course, security was not really an issue then, because it's a gritty was building by the IBM said company simply with the minicomputer, which then was, instead of just providing the computing power to the large, very large company could afford it. Now 70 the minicomputer through the advance and say, My conductor technology could reduce the food frank. And then I'll bring the company power to the labs and to the departments. And that was then the new era of the dish, your equipment, the primes, that General et cetera, Uh, and then conservative. So what client service did again? If you look at the architecture, different architectures now, incidently servers LAN or the Internet network and the PC, and that was now allowing to distribute the computing power to the people in the company. And so, but then you needed to so everybody. Nobody paid attention to security because then you were inside of the enterprise. So it starts inside the wars of the castle if you prefer. So nobody paid attention to that. It was more complex because now you have multiple actors instead of having one IBM or one desert equipped. But its center said, You have the people manufacturing the servers. The software that that obeys the PC is an unannounced excellently there was the complexity increased significantly, but nobody paid attention to security because it was not needed. Until suddenly we realized that viruses could come in through the front door being installed innocent. You were absolutely, absolutely compromised. And of course, that's the era of the anti VARS, which came in and then because of the need to communicate more more. Now, Senator, you could not stay only in your castle. You need to go and communicate your customers to your suppliers, et cetera, et cetera. And now you were starting to up and up your your castle to the word and a low now so that the bad guy could come in and start to steal your information. And that's what the new era of the far wall. Now you make sure that those who come in But of course, that was a bit naive because there were so many other doors and windows that people could come in, you know, create tunnels and these and over that transfer, insure your custard. Because the day I was becoming more, more rich and more more important, more value. So whatever this value, of course, the bad guys are coming in to try to sell it. And that was that new era off a win. Each of attention to security. The problem is being is because you have so many different actors. There was nothing really central there. Now. I just suddenly had Maura and more solutions, and now absolutely like 800 vendors. Boarding on security and boating on anything is shortly at the end of the day because you put more more weight, and then you also increasing complexity in all these different solutions. Didn't they need to talk together? So you have a better context, but they weren't designed to talk together. So now you need to put other system where they could communicate that information. So you complicated, complicated, complicated the solution. And that's the problem of today. So now cloud computing comes in and again. If you look at the architecture of cloud computing, it's again Data centers, which not today, have become, thanks to the technology, having infinite, almost company power and storage capabilities. And like the previous data center, there are much more fracture because you just once gave and they become essentially a bit easier to secure. And by the way, it's your fewer vendors now doing that. And then, of course, the access can be controlled better on then. Of course, the second component is that the land and the one it's now the Internet and the Internet, of course, eyes the Web communications extremely cheap, and it brings you in every place on the planet and soon in Morse. Why no so and so now. The issue today is that still the Internet needs to be secure, and today how are you going to secure the Internet? Which is very important thing today because you see today that you can spoof your image, you can spoof your website. You could attack the Deanna's who? Yes, there's a lot of things that the bad guy still do in fact, themselves that ever is the Internet, of course, to access everywhere, so they take advantage of it. So now this is obviously, you know, I created the trustworthy movement many years ago to try to really address that. Unfortunately, qualities was too small, and it was not really our place. Today there's all the Google, the Facebook, the big guys which contract their business, depend on the Internet. Now need to do that and I upload will be been criticised very much so. Google was the 1st 1 to essentially have a big initiative. I was trying to Bush SSL, which everybody understands secret encryption, if you prefer and to everybody. So they did a fantastic job, really push it. So now today's society is becoming like okay, it's a said. You want to have this a settle on your communication, but that's not enough. And now they're pushing and some people criticize them, and I absolutely applaud them to say we need to change the Internet protocols which were created at the time when security you were transferring information from universities. And so for these was a hay days, you know, if everything was fine, there's no bad guys. No, The heebie day is if you like arranging that everybody was free, Everybody was up in fantastic. Okay. And now, of course, today, these poor cold this to be a graded, which is a lot of work. But today I really believe that if you put Google Amazon Facebook altogether and they can fix these internet for records so we could forget about the spoofing and we forget about all these fishing and all this thing this is there responsibility. So and then you have now on the other side, you have now a very intelligent devices from in a very simple sensors and, you know, too sophisticated devices the phone, et cetera, and Maura and more Maur devices interconnected and for people to understand what is being so This is the new environment. And whether we always believe is that if you adopt an architecture which is exactly which fits which is similar, then we could instead of bolting security in, we can also have the build security in voting signal on. We could be in security in. And we have been very proud of the work that went down with my car itself, which we announce, in fact, reluctantly recently, very recently, that, in fact, our agent technologies now it's banned erred in Microsoft. So we have been security with Microsoft in So from a security perspective today, if you go to the Microsoft as your security center, you click on a link, and now you have the view. If you're in tar, is your environment courtesy of record? It's agent. You click on a second link, and now you have the view of your secret cameras. First year, crazy of the same qualities agent. And then you click on the third inning with us. Nothing to do with quite it's It's old Mike ourself you create your playbook and Yuri mediates The security in this environment has become quickly, quick, nothing to in store, nothing to update, and the only thing you bring. All your policies saying I don't want to have this kind of machine exposed on the Internet on what this is what I want and you can continuously owed it essentially in real time, right? So, as you can see, totally different than putting boxes and boxes and so many things. And then I think for you, so very big game changer. So the analogy that I want you that I give to people it's so people understand that paradigm shift. It's already happening in the way we secure our homes. You put sensors everywhere, your cameras of detection, approximately detection. Essentially, when somebody tried to enter your home all that day, that's continuously pumped up into an incident response system. And then from your phone again across the Internet, you can change the temperature of your rooms. You can do it. You can see the person who knocks on the door. You can see its face. You can open the door, close the door, the garage door. You can do all of that remotely and automatically. And then, if there's a burglar, then in your house, who's raking immediately that the incidence response system called the cops or the farmer shirt? If good far. And that's the new paradigm. So security has to follow that product, and then you have interesting of the problem today that we see with all the current security systems incidents Original system developed for a positive force. Positive and negative are the enemy reedy off security? Because if you have forced positive, you cannot automate the response because then you're going to try to respond to something that is that true? So you are. You could create a lot of damage. And the example. I give you that today in the if you leave your dog in your house and if you don't have the ability the dog would bark would move, and then the senses will say intruder alert. So that's become the force. Pretty. So how do you eliminate that? By having more context, you can eliminate automatically again this false positives, like now you, I think a fingerprint of fuel dog and of his voice. And now the camera and this and the sensors on the voice can pick up and say, Oh, this is my dog. So then, of course, you eliminate that forces right now, if if another dog managed to return your home through a window which was open or whatever for so what do we know? A window was open, but you know you can't necessarily fix it on the dog weapons, then you will know it. Sze, not yours. So that's what securities avoiding such a huge sea of change which is happening because of all that injured that end today Companies today after leverages nuclear technology which are coming, there's so much new to college. What people understand is where's that technology coming from? How come silently we have doctors cybernetics a ll these solutions today which are available at almost no cost because it's all open source So what happened is that which is unlike the enterprise software which were Maur the oracle, et cetera, the manufacturer of that software today is in fact the cloud bubbly club Sanders, the Amazon, the Google, the Facebook, the macro self which shouldn't be needed to have to develop new technology so they could scale at the size of the planet. And that very shrewdly realized that if I keep the technology for me, I'm essentially going to imprison. The technology is not going to evolve. And then I need other technologies that I'm not developing. So they realize that they totally changed that open source movement, which in the early days of happens offers more controlled by people who had more purity. If you prefer no commercial interests, it was all for the good, off the civilization and humankind. And they say they're licensing Modern was very complex or the simplified all of that. And then Nelson and you had all this technology coming at you extremely fast. And we have leverage that technology, which was not existing in the early days when when such was not come started with the eunuchs, the lamb, pork or what's called leaks. Apache mice Fewer than Petri limiting Announcer Tiel This technology, like elasticsearch, was coming. We index today now back and three trillion points or less excerpts, clusters, and we return information in 100 minutes seconds and then on the calf campus, which is again something that open source way Baker Now today, five million messages a day and on and on and on. So the word is changing. And of course, if that's what it's called now, the dish transformation now enterprises to be essentially a joy to reach out to the customers better and Maur, they need to embrace the cloud as well, >>right? I >>do retool their entire right infrastructure, and it's such A. It's a huge sea of change, and that's what we see even the market of security just to finish now, evolving in a totally different ways than the way it has Bean, which in the positive market of security was essentially the market for the enterprise. And I'm bringing you might my board, my board, towns, traditions that you have to go in installed and make work. And then you had the the anti virus, essentially for all the consumers and so forth. So today, when we see the marketplace, which is fragmenting in four different segments, which is one is the large enterprise which are going to essentially constantly data start moving to the transformation. Leveraging absolutely develops, which isn't becoming the new buyer. And, of course, so they could improve their I t. For to reach out to more customers and more effectively than the current providers. As I mentioned earlier, which are building security in the knife, you use them. You don't have to worry about infrastructure about how many servers you need, amenities. It's all done for you and something about security. The third market is going to be in an emergence of a new generation of managed Grannie service providers which are going to take all these companies. We don't have enough resources. Okay, Don't worry. I'm going to help you, you know, duel that digital transformation and help you build the security. And then there's a totally new market of all these devices, including the phone, et cetera, which connects and that you essentially I want to all these i, o t and I ot devices that are or now connected, which, of course, present security risk. So I need to also secure them. But you also need to be able to also not only check their health to make sure that okay, because you cannot send people read anymore. So you tournament simply on security. If you find that that phone is compromised, you need to make to be able to make immediate decisions about Should I kill that phone? Destroyed everything in it. Should I Now don't let that phone connect any more to my networks. What should I do? Should I, by the way, detected that they've done with the application which another loud Because what we see is more and more companies are giving tablets to their users and in doing so now, today's the company property so they could say, OK, you use these tablets and you're not allowed to do that so you could check all of that and then automatically. But that again requires full visibility in what you are. And that's why just to finish, we make a big decision about the few three months ago that were We build the ability for any company on the planet to automatically build their targetable itis it eventually, which nobody knows what they have. That old networking environment. You don't know what connects to have the view of the known and the unknown totally free of charge across on premise and pawned crowd continues Web obligations or to united devices to come. So now that's the cornerstone of securities with that totally free. So and then, of course, you have all these additional solutions, and we're being very scalable up in platform where we can take data, a passel data as well. So we really need to be and want to be good citizen here because security at the end of it, it's almost like we used to say, like the doctors, you have to have that kind of feeble court oath that you can do no arms. So if you keep if you try to take the data that you have, keep it with you, that's all.

>> from Austin, Texas. It's Theo Cube covering your storage accelerate 2019. Brought to you by pure storage. >> Welcome back to the Q. We are wrapping up day two of two days of coverage. We're getting some applause. I'm pretty sure that's for us. At pure accelerate. 2019. Lisa Martin flanked by two gents Day Volante and Justin Warren. You probably know Justin, who's been on the Cube many times and less. Chief analyst. A pivot. Nine. Justin. You have been covering this event and well as an independent, so we want to get your take on this two days. We've had our 1st 2 day for the Cube covering pier storage. We've spoken with lots of people, cause Charlie kicks. I'm sure there's more nicknames that I'm forgetting customers. Partners. Dave. Let's do a quick recap of some of the trends and the themes that we've heard the last couple days. And then we'll get some independent analysis. Justin on Not just what you've heard the last three days, starting with a tech field day, but also just your history of covering and working with here. >> Well, so for my sample, its story of growth they even started pure starts all the press releases with the only company that's growing on the growth storage company. The growth in the first. So so this growth is a financial story there. Um pure is going for growth, the markets rewarding growth right now. So it's smart, double down on growth. That might change at some point on. We talked about Charlie Jean Carlo about this, and they'll decide what what they do at that point time. But But from a financial standpoint, growing fast, uh, like their balance sheet, be interesting to see if they can leverage it. Maur. But maybe they're using it for Optionality. They'll do 1.7 this fiscal year. 1.7 billion. That's good. They got 70% gross margins. It a little bit of free cash flow. Not much because they pour it back into the business. So story a growth that's number 12 was differentiation. Um, I think it it's pretty clear that their products are differentiated from the sort of big portfolio companies. I mean, it's it shows up in the numbers and the income statement, and it shows up when you talk to customers simplicity, the whole A P I thing. I guess the third is products. I mean, they're embracing the cloud, which is kind of interesting. I don't think they're gonna do a ton of business with block storage for AWS, but it's an interesting hedge, and I think it's really cool from an engineering standpoint on, I think you know, two other things. Culture but orange. They're different, They're cool. They're hip and customers, which at the end of the day, that's where the rubber meets the road. Customers happy you talk to companies are customers of companies like pure service now Splunk Nutanix >> Uh uh, >> and some others. And they're happy. They love it. It's transforming their business. Snowflake is another one. Really? How come you AI path is another one? These are the hottest companies in the business right now, and you can tell when you talk to their customers is good story >> and their customers articulate their differentiation for them pretty darn while what? You know, we've spoken to a number. I think four or five customers the last couple of days, and they're not talking about Flash Ray flash blade X M flashback. They're talking about their business and how the I T is benefiting from that and how the business is benefiting from that. You also see piers very vibrant culture being embraced organically by their customers. There's plenty of customers walking around and the brightest orange I think I've even seen here. So there they're differentiation. Their culture, their customer experience and their ability to really differentiate three that are were loud and clear for what I heard through the voice of the customer and the partners, Frankly, as well. >> So I guess, Justin, I mean, the other pieces Tam expansion 1st 10 years, Cloud New Way I workloads partnerships with backup companies growing. The Tim I've said the 1st 10 years is probably gonna be easier, and I know that's a terrible thing to say, but don't hate me for saying it pure. But then the next 10 because they're up against the flat footed E. M. C. That was getting pounded by Elliott management with pressures to go private, trying to hang on to its legacy business and then got acquired and distracted by Del. So that was a really tailwind for Pierre. Now it's like Cloud guys got their act together, you know? Aye, aye. Everybody's doing A s. Oh, so they get some challenges. But what's your take? I think I've >> still got an advantage. Talking to some customers, 11 in particular was quite clear. That they saw pure is having at least a 2 to 3 lead through 2 to 3 year lead on the technology from some of their competitors. So they shopped around and they had a look at some of his competitors, and they thought that actually they were trying to sell me technology that's 234 years old and they quite from them, was that this is something that I could do myself, so they clearly see that pure provides them with something that they can't do themselves. So pure has an advantage there. I also think that the way that the market is changing advantage is pure, a little bit as well. So you mentioned Cloud there, Dave and I think that we've all seen that people have realized that multi cloud is a thing and that not every workload is going to go to the cloud. A lot of it is going to stay on Prem, so now that that's kind of allowed, people are allowed to talk about that, That there are CEOs who would have been being pressured by boards and so on to say we have to go all in on the cloud. Now they can come back to them and say, Well, actually, weaken, stay on side. That means that we should be looking at some of these onside products, like pure so that we can go on put in storage. A race in a data center may not be our Dana Senate might be in Coehlo, but we have this on site method of doing things. Not everything has to go to the cloud. So I think that will help them with some of the growth. >> So I'm left thinking, What would Andy say? Okay to >> be >> It's the number one hottest company, you know, notwithstanding some smaller companies right now, cos moving the market is a W s obviously Microsoft with the trillion dollar valuation. But Amazon, to me, is the benchmark it. So I feel like Jassy would say, Well, so Hey, Andy, you've acknowledged hybrid, you know? Actually, yeah, I guess he uses that word. Um, and you're doing some stuff one prim, but I think he would say we still believe that the vast majority of workloads are gonna land in the public cloud. And what you just said is what everybody else believes. And to me, they're in conflict and I don't necessarily have the answer. But you got the big gorilla. Now the big claw gorilla is moving. The markets say with one philosophy and they've made some good calls and the entire i t industry. Yeah, the other the inspector. >> Except that AWS has outpost have a product that actually sits on site. And they did. And Jesse last year said that he did say that the boat inward, multi cloud, >> you know, So, uh, sorry. Used the word multi cloud used hybrid hybrid cloud. They don't say that. That's for Boden, but no. But my point is they've acknowledged hybrid, which they never used to talk about hybrid. So they capitulated there The end where capitulated on their claws on its cloud strategy. But he has not capitulated on the belief the firm belief that most workloads are gonna be in the club. I'm not sure he's wrong. >> That may be true, but on what Time horizon? So that's not going to happen next year. But I >> think for sure, >> I pointed out that the agile manifesto came out in 2001. That's 18 years ago. Not every shop is doing software in agile, so enterprises take a long time to change, so there's plenty of room for pure to grow. While that changes going on, even if it if it does go all their own cloud, it's gonna take a long time to get there. And people can make plenty of money in the meantime. >> But I believe you're sorry. I believe pure is growing in what is a crappy market. Yeah, I think the storage market is a crap market right now. It's one that's very difficult. The leader Deli emcees growing at 0%. And that's a goodness because they're gaining share. Ned ABS down last quarter, not minus 16% IBM, minus 21% hp thrilled with whatever 3% or whatever. They're at a minus three. I can't remember now. Here is the only one that showing any substantive growth on my premises there, doing that by having a superior product and business model, and they're stealing share. So and then I ask you this. I I believe in hybrid, by the way. But I'm just playing kind of devil's advocate here. Cloud is growing and it's consistently growing and everybody talks about repatriation. You don't see it in the numbers. Every talks about the large of the law of large numbers like in other words, they hit a wall. You don't see that in the numbers. What you see is the traditional IittIe spaces flattish. The new stuff that they're all developing is not growing fast enough to offset the old stuff. You see that? Certainly. See that IBM. You see that now? Adele, even though they had good bounce back last year. But now you're seeing that Adele Oracle ekes out 1% growth. So the big, uh, legacy companies are growing there, hanging on there, throwing off tons of cash. They got good, strong balance sheets, maybe taking on some cheap debt. But the cloud continues to grow at a pace that I think it's stealing share from traditional I t. >> That's that's a reasonable sort of announcing something. Yeah, whether or not we'll see an increase in growth of onsite, particularly things like EJ computing way, maybe you need Thio redefine what we think of as a data center, and maybe we're not thinking about a broad enough market. I actually think that a lot of those workloads that we would traditionally have said would go on site and cola. I don't think Cola Data Center is actually growing all that much, but I think we are going to see growth in things like EJ. >> So that's a really great point I want. I want to come back to that. But the big question is, then okay. Can cloud be before we get ahead, you can cloud be a tail wind for pure. They've embraced it. 20 years ago, the leaders of a company would say, Oh, no, it's cloud his crap about a peace Caesar of toys You remember that pure embracing cloud, I think, is impressive only from an engineering perspective but business model. So can they make in your opinion cloud a tail wind and an opportunity? Maybe that's where Multi Cloud comes in. >> Yeah, it's tricky. I think it will become more of an advantage once good things like kubernetes and containers matures a bit further and people are used to being able to deploy things in that way, both in Cloud and on site. I think that that's the portability play, and it's more about making onsite more cloudy rather than making the cloud more enterprising, which I think was one of the messages that we had here. Because enterprises a lot of what yours messaging so far. And it's product development, particularly around cloud block stories, to make the cloud look more like an enterprise. Where's what we actually needed it to go the other way. Pure is doing things in that in that regard with pure storage optimizer, which which takes a lot of the decision making a way that from the way you would normally do things on side the way we've gotten used to it, manually configuring things, it's actually turning it into software on just letting computers handle it. That integration with things like the M, where is making things operate a lot more like cloud? So once enterprises become used to operating on a lot more like clouds, I think that's going to be an advantage for pure. To be ableto have that operations be in cloud and then they'll bring in products into in time for that to happen. >> You have the opportunity just in a couple days ago to tend the technical field day, the TFT that pure dead. So you got that double click the day before all the press releases broke about. Some of you know, we talked about the expansion into cloud with aws Maur, their portfolio delivered as a service. The aye aye data hub. But if we look at one of the things that stuck out today was differentiation. We've talked about that a number of levels in the last minutes. But talk to us about the technical differentiation that you've not only heard this week from pure, but that you've been engaging with them for years. You have an interesting story of Of John Cosgrove caused their CEO and founder really describing something very unique. That seems to be quite a technical level of differentiation that you even said We don't see this from a lot of their competitors. Give us a little snapshot of that. >> Yeah, you don't sort of get that level of detail in some of the briefings as well. So it was another tech Field day event some years ago on was talking about flash array and we sat in a room, and they had a flash array in front of us, and I think they were talking about the newest kind of flash they were putting into this. But they described some of the technical decisions they made about the architecture inside the blade. So at that time, and I hope I'm getting all these details correct, they had designed and asic, so to go in front, off the flash so that they could essentially create a layer above above the flash that they could speak to within their software. That meant that it didn't matter which flash foundry they bought it from, because it's slut. There are certain differences around the way that flash works, and they do address the flash directly, unlike buying SS D's and putting them inside the box. So that gives them a performance advantage because you don't have a whole bunch of software translation going on to get into the flash. But that decision meant that they could then change flash foundry without changing the experience off the awful. The software developers up the stack inside their array, so that meant that there cadence of being able to bring out new products and gradually dropped down the cost of the supply of flash, which makes up a large amount of the calls on these particular devices. It provided them with better options so they could maintain, maintain optionality essentially and be very, very flexible and react to the things that they can't predict. So Charlie mentioned in the briefing yesterday that you know, in this industry, you might get a 20% drop in the cost of flash in one month, which will then affect them their revenues in coming months after that, because clearly they want to pass on some of those cost drops to customers. But it needs to be done a certain, more manage way. When you have that kind of dynamic behavior happening in the market, being able to react to that well in something where the hardware design time can be 18 months to two years, building that into your product so that it then provides you with business options as a technology, that's a really impressive way of thinking about how all the different pieces of your company have to interact with each other. So it's not just about the technology, it's about the business and the technology working hand in hand, >> and those lower flash prices should open up new markets for them. Flash a racy I think they call it, is still not at the price of hybrid, I wouldn't think, although they saying it will be. Hybrid arrays are priced around 70 60 70 cents a gigabyte today is according Thio Gardner analysis. Big >> Challenge with hybrid of rays Which flat, which flash around flash or a C wouldn't actually wouldn't have? This problem is the reliability of the Leighton see and predictability. So with an old flash array, you don't get Layton. See sparks if you suddenly exhaust the amount of flash that you have in a hybrid of rain that has to go back to the disk. So if you need that predictable performance, that's why people have gone with flesh arrayed very beginning, absolutely getting that as a capacity tear. I think that provides a lot of reliability, for particularly when you've got large amounts of data need to write flesh >> and the price is coming down and it's maybe it's double now on a per gigabyte basis, that'll come down further. But I welcome back to EJ because I think you bring up a good point And we didn't Thankfully, here a ton about EJ. I think we heard anything about EJ at this show. We didn't get inundated with edge, which we always do with these big shows. And I'm happy about that because I think that that a lot of the companies that we re attend I think they got it wrong. They're taking a box and they're throwing over the fence to trying to do a top down model to the edge. Hey, here's a server or here's a storage device and we're gonna put it at the edge. It's like, OK, well, I think the edge is going to evolve as a software development. You know, play not isn't over. The top is gonna be bottoms up innovation. Now, I don't know question about you know, whether Amazon at the edge vm wear at the edge. Um, but I don't see any traditional i t companies crushing it at the edge there talking about it. They're trying to build out ecosystems, and but nobody's has meaningful revenue today at the edge. But it's a new way to think about this. Distributed massive compute engine >> on. I think we'll start to see that mature as people start to bring out products that actually do operated the way heard from Nvidia about some of their ideas that they have about doing a I processing at the edge for things like image recognition systems, where you train your model on leg large data sets in a cloud or in a data center. And then you shoot those models out two devices that operate on a smaller data set. But for a lot of these things, you need to do data collection at the edge. So Formula One is a classic example based given for the F one racing team is an I. O. T. Company that is connected to a nail and analytics company. Really? >> Yeah, that's right. We did hear about EJ and that an actual use case is in college edge, so there's going to be >> a lot more of that. We have things like sensors are just all over the place, so you know, in anything in retail, if you have fridges in retail and you need to monitor the sensors in those to find out whether or not is the temperature going out out of control or outside of your control limits because that will affect the food that's in that. There's a whole bunch of kind of boring examples that are actually all I OT. So I think some of those will start to push more data into into devices at the edge. And as people's understanding of how to use machine learning and I matures away from the hype, I think we're pretty peak hype at the moment. Once we do actually drop that back a notch and we see that people they're doing really use riel riel world use cases with real world business value that will start to drive a lot more of the growth of practical. And that will drive growth in data, which will need to get close throughout the weather's device. >> I think you're right. I think that date is gonna be at the edge of a lot of that data. I would say most of that date is going to stay at the edge. It's probably it's not gonna says it. Probably it's definitely not going to sit in a million dollar storage array, and it's gonna comprise a lot of alternative processing arm, Uh, GP use versus conventional microprocessors. So >> and that's where I think he was thinking about, like the white pure One works, for example, pure. One works the same no matter what products you have from pure, and they have been very clear in stating that they want to make sure that when they bring out a new array or a new product, it works with pure one. So it's that consistency of experience for their customers, which I think is fairly unique in the industry, is a lot of other products that will come out. And they only partly supported, not full support for their entire race tagging. AMC struggle with that for a long time simply because it has so many products and needed to kill a whole bunch of them first. So when when you have that kind of engineering discipline built built into your company, when you go out and you have customers who have edge devices or you have stuff in the cloud and they have devices on their phones which they used to showing off a conference and say, Hey, come and have a look at my array, it runs on software on my phone that's pure one that software ability that pure has of being able to address this data wherever it is. I think >> there's >> a real opportunity for pure that put that kind of intelligence on to age things. Even if they don't actually sell any flash a raise to those people, they could start to sell them software. >> All right, guys. So 15 seconds each since arose at a time. Computers competitive. Positioning your thoughts in a quick summary about what you've heard the last few days and what Justin has >> to me if I would expect continued growth, forgetting about the macro for a moment, even in gonna grow faster than the market place. Um and yeah, they said they don't throw off as much cash as the big guys. So it's gonna be a game of the big guys do in stock buybacks, free cash flow and pure storage. Investing in growth. >> Excellent. Justin. >> Yes, I agree. I think they're going to double down on the R and D spend to make sure that they maintain a technological advantage over their competitors. The biggest risk of pure is if the other players, you know, the deal emcee other plays in that big online storage market. If they actually get their act together and start bringing out competitive products, that's the biggest threat to fuel. But pure has a big lead on them. I would say, >> Yeah, I think the last thing cloud, you know, kind of a question Mark. And I think the m where to me, Del. Of course I care about storage is huge business for them. They're all above the M where and to the extent that they can leverage VM where, you know, as a competitive weapon, they'll use it against anybody you know. Damn the ecosystem. >> Excellent. Well, thanks, guys, for a great wrap up to our two days here for Justin Warren and Day Volante. I'm Lisa Martin. Thank you for watching the cubes. Coverage of pure accelerate 2019.

>> Hey, welcome back, everybody. Jefe Rick here with the Cube. Where? It Oracle Park in San Francisco, on the stork with cubby code. We're excited to be here. They're moving a lot of dirt, I think downstairs. But we're at a very cool event. It's called Sports Tech Tokyo World Demo Day. And we're excited. Have our next guest. He's Todd Simms s VP of corporate development from access taught. Great to see you. Great >> to be here. Thank you. Absolutely. So, for people are familiar with access. Give us kind of the company over here. >> We're a global ticketing company. We were launched out of ah global sports and entertainment company called E E G in 2011. And we serve live the live entertainment market and ticketing. Excellent. >> All over the world, >> different types of events. >> E e g. Is a global company with a run venues worldwide. And we serve them as well as third party clients. >> Okay, great. So we're here. It's sports tech, Tokyo. It's a little bit different. Type of an organization. Kind of an incubator. Not really an incubator kind of association, early association, but certainly a community. Why are you guys here. What is this organization mean to you? Why is that important? >> Yeah, it's really important. We We launched our ticketing service in Tokyo last year, and you know, that's a market that we love. It's a vibrant large market with super passionate fans, both on the sports side and on the music side. What it really needs is more of an ecosystem. It can't just be a new, innovative ticketing platform needs all the bells and whistles around it to really innovate the fan experience. And that's what these startups are doing. I >> just I just love this job because, you know, you think of many industries if you're not familiar with them, and they seem really simple on the outside and like everything, once you get under the covers, >> a lot more going on. So >> from the outside, looking in a ticket is a ticket. Yeah, what's the innovation and tickets? What's different about somebody in Japan buying a ticket to watch a baseball game than >> somebody find a ticket to come here to talk >> a little bit about what we're bringing to Tokyo and what we brought to our platform of clients here in the States as well as in Europe, and that's really a digital I. D based ticketing system. So when you walk into the Staples Center at L. A live in Los Angeles, that thing that's getting scanned is not a ticket. It's an identity, it's you. And what's being reviewed is whether you have access to that building on that night or not. So what that allows for is full data around the customer base. Every president of every team wants to know two things. They want to know who's in there building, and they wanna have some control, whether it's economic control or otherwise on the secondary market. Our digital I D ticketing system enables both of that, and that's kind of the innovation that we're bringing to the Tokyo market. >> But I would imagine when you say, you know it's me, you know the opportunities way beyond that because now you know what in my preference is, how often do I come? What kind of beer do I like to drink? It just opens up a whole kind of CR m ah, world of opportunity for this relationship between the team now in that person with that barker, >> absolutely, and that happens today, but what you're missing is every time someone comes in with a paper ticket, you're really not sure who's entering the building. So that eliminates that piece of that. And it gets all these teams with analytic departments to really have a full picture of their fan base. So, you know, they may have been investing in some of this and capturing 60 70% of their who's in the building. Now they have 100% right, >> and I would imagine they've been doing this for a long time, with kind of their season ticket base and knowing they're in the building. But it got a lot of data on their season ticket holders. How is that? You know, changed. What can they apply there to? The casual fan that maybe bought a ticket on the secondary market and his, you know, common is sitting in the bleachers? >> Well, it's huge >> for up sales and establishing that relationship. A lot of teams, if you've you know, just buying a single ticket off a secondary market, you're nowhere in that database now because of our I D based system. Those people are now prospects for either mini pack or a season ticket back. It's right. Just >> curious how the rise of the secondary market really impacted the teams and how they think about their own ticket based. I think the 1st 1 is probably StubHub back in the day for some, and it all happened kind of outside the purveyor of leagues and outside the purveyor of the teams. Likely, they're pretty smart and figured out we need to be a piece of this. So how did that kind of evolution change the way the teams think about their fans? Well, look, I mean, teams >> like music promoters, they Sometimes they like the brokers getting involved because it takes risk off the table. I think teams air realizing, though, that a riel yield management perspective on their ticket inventory to really revenue manage this appropriately. They have to take a holistic approach on their >> tickets, and any time you >> have a segment of your >> ticket base where you really don't have control of pricing distribution, >> all of that, it really hurts and it has an impact on your unsold primaries. So what teams are looking to do is gain more control and manages inventory more holistically to do that you really need to know all the data. And again, the I. D based ticketing system enables secondary sales. But at least you are tracking those sales and, you know, from one person to the next who who sold it, who bought it >> right? I'm curious to get your perspective on on the difference between if you arm or >> entertainment focused. So you know, the Rolling Stones were in town a couple nights ago, and it's really a one shot deal for the Rolling Stones in the Bay Area that night versus the Giants game, right where you're hoping that your people come back over and over. Did they think of it differently? Or is it Maur? You know, Jeff, you like music? You went to the Rolling Stones last night. Maybe you'll come and see somebody else tonight. Is that is that well, can't were they? No doubt, sports teams are >> a lot smarter about their fan base. They have loyalty built in. They have got history, you know there's variability. There's night of game. And then there's weather in who's on the mound and all of those factors. But promoters are, ah, lot more in the dark about, you know, Is this an artist that you know? How much credence can they put in the last two? Or they did. It's too been two years. Is that artist still going to sell appropriately or similarly than they did last time again? The secondary market on the music side is made a bigger issue because of that variability, and those promoters are willing to take risk off the table. But the same thing applies in order for them to really manage and revenue manage that tour. They really need to know who's buying and grab some of that secondary economics out of the system. Right? And that's again, what our platform enables, and that's what we're really bringing to the Tokyo market. It's really exciting. That's a great market for >> us. I was gonna say just to close. >> You know what's special about the Tokyo market either? From an opportunity side, we're kind of a unique way which they do things or unique way in which the kind of the fan experiences as you look at that market. >> Well, it's interesting. I mean, in a culture that is so reliant on such interesting technology, these ticketing technology is actually quite old, and so we're excited to bring that. We've got great partners past Revo is our partner there, and they're really selling that through the Yahoo ticketing channel. Uh, they we have we just signed the B league, which is the professional basketball league will be rolling them out in their fall season coming up soon here. But basically, they are looking for the same things. We're looking for more data and Maura capturing of the secondary market, and we can bring that to them. >> All right. Well, Todd, thanks for taking a few minutes. Pull the covers back off ticketing A lot more going on than people think. Thank you very much. All right, He's >> taught. I'm Jeff. You're watching The Cube. Were Rhetorical Park on the shores of >> McCovey Cove in San Francisco. Thanks for watching. We'll see you next time.

>> live from Barcelona, Spain. It's the key covering Cook Con Cloud, Native Con Europe twenty nineteen by Red Hat, The Cloud, Native Computing Foundation and Ecosystem Partners. >> Welcome back to the Cubes Live coverage of Cloud Native Con Cube Khan, twenty nineteen I'm student of my co host is Corey Quinn and happy to welcome back to the program. Doug Davis, who's a senior technical staff member and PM of a native and happens to be employed by IBM. Thanks so much for joining. Thanks for inviting me. Alright. So, Corey, I got really excited when he saw this Because server lists, uh, is something that, you know he's been doing for a while. I've been poking in, trying to understand all the pieces have done marvelous conflict couple of times and, you know, I guess, I guess layout for our audience a little bit, you know, Kay native. You know, I look at it kind of a bridging the solution, but, you know, we're talking. It's not the, you know, you know, containers or server. Listen, you know, we understand that world, they're spectrums, and there's overlap. So maybe is that is a set up. You know what is the service. Working groups, you know, Charter, Right. So >> the service Working Group is a Sand CF working group. It was originally started back in mid two thousand seventeen by the technical recite committee in Cincy. They basically wanted know what is service all about his new technology is that some of these get involved with stuff like that. So they started up the service working group and our main mission was just doing some investigation. And so the output of this working group was a white paper. Basically describing serval is how it compares with the other as is out there. What is the good use cases for when to use? It went out through it. Common architectures, basically just explaining what the heck is going on in that space. And then we also produced a landscape document basically laying out what's out there from a proprietors perspective as well is open source perspective. And then the third piece was at the tail end of the white paper set of recommendations for the TOC or seen staff in general. What should they do? Do next and basic came down to three different things. One was education. We want to be educate the community on what services, when it's appropriate >> stuff like that >> to what should wait. I'm sorry I'm getting somebody thinks my head recommendations. What other projects we pull into the CNC f others other service projects, you know, getting encouraged in the joint to grow the community. And, third, >> what should we >> do around improbability? Because obviously, when it comes to open source standards of stuff like that, we want in our ability portability, stuff like that. And one of the low hang your food so they identified was, Well, service seems to be all about events. So there's something inventing space we can do and we recognize well, if we could help the processing of events as it moves from Point A to point B, that might help people in terms of middleware in terms of routing, of events, filtering events, stuff like that. And so that's how these convents project that started. Right? And so that's where most of service working group members are nowadays. Is cloud events working or project, and they're basically divine, Eva said. Specification around cloud events, and you kind of think of it as defining metadata to add to your current events because we're not going to tell you. Oh, here's yet another one size fits all cloud of in format, right? It's Take your current events. Sprinkle a little extra metadata in there just to help routing. And that's really what it's all about. >> One of the first things people say about server list is quoted directly from the cover of Missing the Point magazine Server list Runs on servers. Wonderful. Thank you for your valuable contribution. Go away slightly less naive is, I think, an approach, and I've seen a couple of times so far at this conference. When talking to people that they think of it in terms of functions as a service of being able to take arbitrary code and run it. I have a wristwatch I can run arbitrary code on. That's not really the point. It's, I think you're right. It's talking more about the event model and what that unlocks As your application. Mohr less starts to become more self aware. Are you finding that acceptance of that point is taking time to take root? >> Yeah, I think what's interesting is when we first are looking. A serval is, I think, very a lot of people did think of service equals function of the service, and that's all it was. I think what we're finding now is this this mode or people are more open to the idea of sort of as you. I think you're alluding to merging of these worlds because we look at the functionality of service offers things like event base, which really only means is the messages coming in? It just happens to look like an event. Okay, fine. Mrs comes in you auto scale based upon, you know, loaded stuff like that scale down to zero is a one of the key. Thought it was really like all these other things are all these features. Why should you limit those two service? Why not a past platform? Why not? Container is a service. Why would you want those just for one little as column? And so my goal with things like a native though I'm glad you mentioned it is because I think Canada does try to span those, and I'm hoping it kind of merges them altogether and says, Look, I don't care what you call it. Use this piece of technology because it does what you need to do If you want to think of it as a pass. Go for I don't care. This guy over here he wants think that is a FAZ Great. It's the same piece of technology. Does the feature do what you need? Yes or no? Ignore that, nor the terminology around it more than anything else. >> So I agree. Ueda Good, Great discussion with the user earlier and he said from a developer standpoint, I actually don't want to think too much about which one of these pass I go down. I want to reduce the friction for them and make it easy. So you know, how does K native help us move towards that? You know, ideal >> world, right? And I think so fine. With what I said earlier, One of the things I think a native does, aside from trying to bridge all the various as columns is I also look a K native as a simplification of communities because as much as everybody here loves communities, it is kind of complicated, right? It is not the easiest thing in the world to use, and it kind of forced you to be a nightie expert which almost goes against the direction we were headed. When you think of Cloud Foundry stuff like that where it's like, Hey, you don't worry about this something, we're just give us your code, right? Cos well says, No, you gotta know about networks, Congress on values, that everything else it's like, I'm sorry, isn't this going the wrong way? Well, Kania tries to back up a little, say, give you all the features of Cooper Netease, but in a simplified platform or a P I experience that you can get similar Tokat. Foundry is Simo, doctor and stuff, but gives you all the benefits of communities. But the important thing is if for some reason you need to go around K native because it's a little too simplified or opinionated, you could still go around it to get to the complicated stuff. And it's not like you're leaving that a different world or you're entering a different world because it's the same infrastructure they could. This stuff that you deploy on K native can integrate very nicely with the stuff you deploy through vanilla communities if you have to. So it is really nice emerging these two worlds, and I'm I'm really excited by that. >> One thing that I found always strange about server list is a first. It was defined by what it's not and then quickly came to be defined almost by its constraints. If you take a look at public cloud offerings around this, most notably a ws land other there, many others it comes down well. You can only run it for experience, time or on Lee runs in certain run times, or it's something the cold starts become a problem. I think that taking a viewpoint from that perspective artificially hobbles what this might wind up on locking down the road just because these constraints move. And right now it might be a bit of a toy. I don't think it will be as it because it needs to become more capable. The big value proposition that I keep hearing around server listen I've mostly bought into has been that it's about business logic and solving the things that Air corps to your business and not even having to think about infrastructure. Where do you stand on that >> viewpoint? I completely agree. I think a lot of the limitations you see today are completely artificial I kind of understand why they're there, because the way things have progressed, But again, it's one reason I excited like a native is because a lot of those limitations aren't there. Now. Kay native doesn't have its own set of limitations. And personally, I do want to try to remove those. Like I said, I would love it if K native, aside from the service features it offers up, became these simplified incriminate his experience. So if you think about what you could do with Coronet is right, you can deploy a pod and they can run forever until the system decides to crash. For some reason, right, why not do that with a native and you can't stay with a native? Technically, I have demos that I've been running here where I set the men scale the one it lives forever, and teenager doesn't care right? And so deploying an application through K native communities. I don't care that it's the same thing to me. And so, yes, I do want to merge in those two worlds. I wantto lower those constraints as long as you keep it a simplified model and support the eighty to ninety percent of those use cases that it's actually meant to address. Leave the hard stuff for going around it a little. >> Alright, So, Doug, you know, it's often times, you know, we get caught in this bubble of arguing over, you know? You know what we call it, how the different pieces are. Yesterday you had a practitioner Summit four server list. So what? I want to hear his You know, whats the practitioners of you put What are they excited about? What are they using today and what are the things that they're asking for? Help it become, you know, Maur were usable and useful for them in the future. >> So in full disclosure, we actually kind of a quiet audience, so they weren't very vocal. But what little I did here is they seemed very excited by K native and I think a lot of it was because we were just talking about sort of the merging of the worlds because I do think there is still some confusion around, as you said, when to use one versus the other. And I think a native is helping to bring those together. And I did hear some excitement around that in terms of what people actually expect from us going the future. I don't know the honest They didn't actually say a whole lot there. I had my own personal opinion, and lot of is what already stayed in terms of emerging. Stop having me pick a technology or pick a terminology, right? Let me just pick technology gets my job done and hopefully that one will solve a lot of my needs. But for the most part, I think it was really more about Kenya than anything else yesterday. >> I think like Lennox before it. Any technology? At some point you saw this with virtual ization with cloud, with containers with Cooper Netease. And now we're starting to seriously with server lists where some of its most vocal proponents are also so the most obnoxious in that they're looking at this from a perspective of what's your problem? I'm not even going to listen to the answer. The solution is filling favorite technology here. So to that end today, what workloads air not appropriate for surveillance in your >> mind? Um, so this is hardly the answer because I have the IBM Army running through my head because what's interesting is. I do hear people talk about service is good for this and not this or you can date. It was good for this and not this. And I hear those things, and I'm not sure I actually buy it right. I actually think that the only limitations that I've seen in terms of what you should not run on time like he needed or any of the platform is whatever that platform actually finds you, too. So, for example, on eight of us, they may have time limited in terms of how long you can run. If that's a problem for you, don't use it to me. That's not an artifact of service. That's artifact of that particular choice of how the implement service with K native they don't have that problem. You could let it run forever if you want. So in terms of what workloads or good or bad, I honestly I don't have a good answer for that because I don't necessary by some of the the stories I'm hearing, I personally think, try to run everything you can through something like Cain native, and then when it fails, go someplace else is the same story had when containers first came around, they would say, You know when to use viens roses containers. My go to answer was, always try containers first. Your life would be a whole lot easier when it doesn't work, then look at the other things because I don't want to. I don't want to try to pigeonhole something like surly or K native and say, Oh, don't even think about it for these things because it may actually worked just fine for you, right? I don't want people to believe negative hype in a way that makes sense, >> and that's very fair. I tend to see most of the constraints around. This is being implementation details of specific providers and that that will dictate answers to that question. I don't want to sound like I'm coming after you, and that's very thoughtful of measured >> thank you Usual response back. Teo >> I'LL give you the tough one. The critical guy had in Seattle when I looked at K Native is there's a lot of civilised options out there yet, but when I talked to users, the number one out there is a ws lambda, and number two is probably as your functions and as of Seattle, neither of those was fully integrated since then. I talked a little startup called I Believe his Trigger Mash that that has made some connections between Lambda on K Native. And there was an announcement a couple of weeks ago, Kedia or Keita? That's azure and some kind of future to get Teo K native. So it feels like it's a maturity thing. And, you know, what can you tell us about, you know, the big cloud guys on Felicia? Google's involved IBM Red Hat on and you know Oracle are involved in K Native. So where do those big cloud players? Right? >> So from my perspective, what I think Kenya has going for it over the others is one A lot of other guys do run on Cooper Netease. I feel like they're sort of like communities as well as everything else, like some of them can run. Incriminate is Dr anything else, and so they're not necessary. Tightly integrated and leveraging the carbonates features the way Kay native is doing, and I think that's a little bit unique right there. But the other thing that I think K native has going for it is the community around it. I think people were doing were noticing. Is that what you said? There's a lot of other players out there and his heart feel the choose and what? I think Google did a great job of this sort of bringing the community together and said, Look, can we stop bickering and develop a sort of common infrastructure like communities is that we can all then base our surveillance platforms on, and I think that rallying cry to bring the community together across a common base is something a little bit unique for K native. When you compare it with the others, I think that's a big draw for people. Least from my perspective. I know it from IBM Zzzz Well, because community is a big thing for us, obviously. >> Okay, so will there be a bridge to those other cloud players soon as their road map? For that, >> we think a native itself. Yeah, I am not sure I can answer that one, because I'm not sure I heard a lot of of talk about bridging per se. I know that when you talk about things like getting events from other platforms and stuff, obviously, through the eventing side of a native. We do. But from a serving perspective, I'm not sure I hold her old water. From that perspective, you have to be >> honest. All right, Well, Doug Davis, we're done for This one really appreciate all the updates there. And I definitely look forward, Teo, seeing the progress that the servant working group continues to do, so thank you so much. Thank you for having me. Alright for Corey Quinn. I'm stupid and will be back with more coverage here on the Cube. Thanks for watching.

>> about >> fifteen live from basically about a room that is a common club native con Europe twenty nineteen by Red Hat, The >> Cloud, Native Computing Foundation and Ecosystem Partners. >> Welcome back to the Cubes. Live coverage of Cloud Native Con Cube Khan, twenty nineteen I'm stupid in my co host is Corey Quinn and having a welcome back to the program, Doug Davis, who's a senior technical staff member and PM of a native. And he happens to be employed by IBM. Thanks so much for joining. Thanks for inviting me. Alright, So Corey got really excited when he saw this because server Lis is something that you know he's been doing for a while. I've been poking in, trying to understand all the pieces have done marvelous conflict couple of times and, you know, I guess, I guess layout for our audience a little bit, you know, k native. You know, I look at it kind of a bridging a solution, but, you know, we're talking. It's not the, you know, you know, containers or server lists. And, you know, we understand that world. They're spectrums and there's overlap. So maybe as that is a set up, you know, What is the surveillance working groups? You know, Charter. Right. So >> the service Working Group is a Sand CF working group. It was originally started back in mid two thousand seventeen by the technical recite committee in Cincy. They basically wanted know what is service all about his new technology is that some of these get involved with stuff like that. So they started up the service working group and our main mission was just doing some investigation. And so the output of this working group was a white paper. Basically describing serval is how it compares with the other as is out there. What is the good use cases for when to use that went out through it? Common architectures, basically just explaining what the heck is going on in that space. And then we also produced a landscape document basically laying out what's out there from a proprietors perspective as well is open source perspective. And then the third piece was at the tail end of the white paper set of recommendations for the TOC or seen stuff in general. What do they do next? And basic came down to three different things. One was education. We want to be educate the community on what services when it's appropriate stuff like that. Two. What should wait? I'm sorry I'm getting somebody Thinks my head recommendations. What other projects we pull into the CNC f others other service projects, you know, getting encouraged in the joint to grow the community. And third, what should we do around improbability? Because obviously, when it comes to open source standards of stuff like that, we want in our ability, portability stuff like that and one of the low hang your food should be identified was, well, service seems to be all about events. So there's something inventing space we could do, and we recognize well, if we could help the processing of events as it moves from Point A to point B, that might help people in terms of middleware in terms of routing, of events, filtering events, stuff like that. And so that's how these convents project that started. Right? And so that's where most of service working group members are nowadays. Is cod events working or project, and they're basically divine, Eva said specification around cloud events, and you kind of think of it as defining metadata to add to your current events because we're not going to tell you. Oh, here's yet another one size fits all cloud of in format, right? It's Take your current events. Sprinkle a little extra metadata in there just to help routing. And that's really what it's all about. >> One of the first things people say about server list is quoted directly from the cover of Missing the Point magazine Server list Runs on servers. Wonderful. Thank you for your valuable contribution. Go away slightly less naive is, I think, an approach, and I've seen a couple of times so far at this conference. When talking to people that they think of it in terms of functions as a service of being able to take arbitrary code and running, I have a wristwatch I can run arbitrary code on. That's not really the point. It's, I think you're right. It's talking more about the event model and what that unlocks As your application. Mohr less starts to become more self aware. Are you finding that acceptance of that viewpoint is taking time to take root? >> Yeah, I think what's interesting is when we first are looking. A serval is, I think, very a lot of people did think of service equals function of the service, and that's all it was. I think what we're finding now is this this mode or people are more open to the idea of sort of as you. I think you're alluding to merging of these worlds because we look at the functionality of service offers, things like event based, which really only means is the messages coming in? It just happens to look like an event. Okay, fine. Mrs comes in you auto scale based upon, you know, loaded stuff like that scale down to zero is a the monkey thought it was really like all these other things are all these features. Why should you limit those two service? Why not a past platform? Why not? Container is a service. Why would you want those just for one little as column? And so my goal with things like a native though I'm glad you mentioned it is because I think he does try to span those, and I'm hoping it kind of merges them altogether and says, Look, I don't care what you call it. Use this piece of technology because it does what you need to do. If you want to think of it as a pass, go for I don't care. This guy over here he wants think that is a FAZ Great. It's the same piece of technology. Does the feature do what you need? Yes or no? Ignore that, nor the terminology around it more than anything >> else. So I agree. Ueda Good, Great discussion with the user earlier and he said from a developer standpoint, I actually don't want to think too much about which one of these pass I go down. I want to reduce the friction for them and make it easy. So you know, how does K native help us move towards that? You know, ideal >> world, right? And I think so fine. With what I said earlier, One of the things I think a native does, aside from trying to bridge all the various as columns is I also look a K native as a simplification of communities because as much as everybody here loves communities, it is kind of complicated, right? It is not the easiest thing in the world to use, and it kind of forced you to be a nightie expert which almost goes against the direction we were headed. When you think of Cloud Foundry stuff like that where it's like, Hey, you don't worry about this something, we're just give us your code, right? Cos well says No, you gotta know about Network Sing Gris on values that everything else it's like, I'm sorry, isn't this going the wrong way? Well, Kania tries to back up a little, say, give you all the features of Cooper Netease, but in a simplified platform or a P I experience that you can get similar Tokat. Foundry is Simo, doctor and stuff, but gives you all the benefits of communities. But the important thing is if for some reason you need to go around K native because it's a little too simplified or opinionated, you could still go around it to get to the complicated stuff. And it's not like you're leaving that a different world or you're entering a different world because it's the same infrastructure they could stuff that you deploy on. K Native can integrate very nicely with the stuff you deploy through vanilla communities if you have to. So it is really nice emerging these two worlds, and I'm I'm really excited by that. >> One thing that I found always strange about server list is at first it was defined by what it's not and then quickly came to be defined almost by its constraints. If you take a look at public cloud offerings around this, most notably a ws land other there, many others it comes down well. You can only run it for experience time or it only runs in certain run times. Or it's something the cold starts become a problem. I think that taking a viewpoint from that perspective artificially hobbles what this might wind up on locking down the road just because these constraints move. And right now it might be a bit of a toy. I don't think it will be as it because it needs to become more capable. The big value proposition that I keep hearing around server listen I've mostly bought into has been that it's about business logic and solving the things that Air Corps to your business and not even having to think about infrastructure. Where do you stand on that >> viewpoint? I completely agree. I think a lot of the limitations you see today are completely artificial. I kind of understand why they're there, because the way things have progressed. But again, that's one reason I excited like a native is because a lot of those limitations aren't there. Now, Kay native doesn't have its own set of limitations. And personally, I do want to try to remove those. Like I said, I would love it if K native, aside from the serval ISS features it offers up, became these simplified, incriminate his experience. So if you think about what you could do with Coronet is right, you could deploy a pod and they can run forever until the system decides to crash. For some reason, right, why not do that with a native and you can't stay with a native? Technically, I have demos that I've been running here where I set the men scale the one it lives forever, and teenager doesn't care right? And so deploying an application through K native communities. I don't care that it's the same thing to me. And so, yes, I do want to merge in those two worlds. I wantto lower those constraints as long as you keep it a simplified model and support the eighty to ninety percent of those use cases that it's actually meant to address. Leave the hard stuff for going around it a little. >> Alright, So, Doug, you know, it's often times, you know, we get caught in this bubble of arguing over, you know? You know what we call it, how the different pieces are. Yesterday you had a practitioner Summit four server list. So what? I want to hear his You know, whats the practitioners of you put What are they excited about? What are they using today and what are the things that they're asking for? Help it become, you know, Maur were usable and useful for them in the future. >> So in full disclosure, we actually kind of a quiet audience, so they weren't very vocal. But what little I did here is they seem very excited by K native and I think a lot of it was because we were just talking about that sort of merging of the worlds because I do think there is still some confusion around, as you said when you use one verse of the other and I think a native is helping to bring those together. And I did hear some excitement around that in terms of what people actually expect from us going in the future. I don't know. Be honest. They didn't actually say a whole lot there. I had my own personal opinion, and lot of years would already stayed in terms of emerging. Stop having me pick a technology or pick a terminology, right? Let me just pick the technology. It gets my job done and hopefully that one will solve a lot of my needs. But for the most parts, I think it was really more about Kaneda than anything else. Yesterday, >> I think like Lennox before it. Any technology? At some point you saw this with virtual ization with cloud, with containers with Cooper Netease. And now we're starting to Syria to see with server lists where some of its most vocal proponents are also the most obnoxious in that they're looking at this from a perspective of what's your problem? I'm not even going to listen to the answer. The absolution is filling favorite technology here. So to that end today, what workloads air not appropriate for surveillance in your mind? >> Um, >> so this is hardly an answer because I have the IBM Army running through my head because what's interesting is I do hear people talk about service is good for this and not this or you can date. It is good for this and not this. And I hear those things, and I'm not sure I actually buy it right. I actually think that the only limitations that I've seen in terms of what you should not run on time like he needed or any of the platform is whatever that platform actually finds you, too. So, for example, on eight of us, they may have time limited in terms of how long you can run. If that's a problem for you, don't use it to me. That's not an artifact of service. That's artifact of that particular choice of how the implement service with K native they don't have that problem. You could let it run forever if you want. So in terms of what workloads or good or bad, I honestly I don't have a good answer for that because I don't necessary by some of the the stories I'm hearing, I personally think, try to run everything you can through something like Cain native, and then when it fails, go someplace else is the same story had when containers first came around. They would say, You know when to use BMS vs Containers. My go to answer was, always try containers first. Your life will be a whole lot easier when it doesn't work, then look at the other things because I don't want to. I don't want to try to pigeonhole something like surly or K native and say, Oh, don't even think about it for these things because it may actually worked just fine for you, right? I don't want people to believe negative hype in a way that makes sense, >> and that's very fair. I tend to see most of the constraints around. This is being implementation details of specific providers and that that will dictate answers to that question. I don't want to sound like I'm coming after you, and that's very thoughtful of measured with >> thank you. That's the usual response back. So don't >> go. I'Ll give you the tough one critical guy had in Seattle. Okay, when I looked at K Native is there's a lot of civilised options out there yet, but when I talked to users, the number one out there is a ws Lambda, and number two is probably as your functions. And as of Seattle, neither of those was fully integrated. Since then, I talk to a little startup called Believers Trigger Mash, that that has made some connections between Lambda Ah, and a native. And there was an announcement a couple of weeks ago, Kedia or Keita? That's azure and some kind of future to get Teo K native. So it feels like it's a maturity thing. And, you know, what can you tell us about, you know, the big cloud guys on Felicia? Google's involved IBM Red Hat on and you know Oracle are involved in K Native. So where do those big cloud players? Right? >> So from my perspective, what I think Kenya has going for it over the others is one A lot of other guys do run on Cooper Netease. I feel like they're sort of like communities as well as everything else, like some of them can run. Incriminate is Dr anything else, and so they're not necessary, tightly integrated and leveraging the community's features the way Kay Native is doing. And I think that's a little bit unique right there. But the other thing that I think K native has going for it is the community around it? I think people were doing were noticing. Is that what you said? There's a lot of other players out there, and it's hard for people to choose. And what? I think Google did a great job of this sort of bringing the community together and said, Look, can we stop bickering and develop a sort of common infrastructure? Like Who Burnett is is that we can all then base our surveillance platforms on, and I think that rallying cry to bring the community together across a common base is something a little bit unique for K native. When you compare it with the others, I think that's a big draw for people. Least from my perspective. I know it from IBM Zzzz Well, because community is a big thing for us, >> obviously. Okay, so will there be a bridge to those other cloud players soon as their road map? For that, >> we think a native itself. Yeah, I am not sure I can answer that one, because I'm not sure I heard a lot of talk about bridging per se. I know that when you talk about things like getting events from other platforms and stuff. Obviously, through the eventing side of a native we do went from a serving perspective. I'm not sure I hold her old water. From that perspective, you have >> to be honest. All right, Well, Doug Davis, we're done for This one. Really appreciate all the updates there. And I definitely look forward, Teo, seeing the progress that the servant working group continues to do, so thank you so much. Thank you for having me. Alright for Corey Quinn. I'm stupid and will be back with more coverage here on the Cube. Thanks for watching.

>> Las Vegas. Extensive signal from the noise. It's the Q covering interconnect 2016. Brought to you by IBM. Now your host, John Hurry and Dave Ilan. >> Okay, Welcome back, everyone. We are here live in Las Vegas for exclusive coverage of IBM interconnect 2016. This is Silicon Angles. The Q. That's our flagship program. We go out to the events and extract the signal from the noise. I'm John Ferrier with my Coast Day Volante. Our next guest, Steve Robinson News. The GM of client technical engagement before that, in the cloud doing all the blue mix now has the army of technical soldiers out there doing all the action because it's so much robust. So much demand for horizontally scale. The sluices with vertically targeted, prepackaged application development. That's horrible. First you name it big data. Welcome back. Good to see you, John. Thanks. Good to be with you again. Always, like great to have you on because you got a great perspective. You understand the executive viewpoint. A 20 mile stare in the industry. But also you got the in the nuts and bolts in under the hood. >> That's right. A >> lot of action happening under the hood. So let's get that right away. Blue, Mrs Hot Night. Now it's about the developers. What's going on under the hood right now that customers are caring about? >> I always love the Cube. You guys were like one of the first guys talking to us two years ago when we just launched a blue makes on stage. We walked off, got in front of cameras here, and it was great. Over the past year, it's been it's been outstanding. We we're writing about 20,000 folks toe blue mix right now on public, we came out with dedicated and then what people had really been warning was local blue mix as well. So we finally have full hybrid chain that goes from behind the firewall to a single client dedicated cloud all the way up to the public as well. So we've been building that out with service is as well, so have over 106 service is on top of it. You'll see things like Watson, which is unique, our Dash CB analytics, which is unique Internet of things coming in as well. So it's been a great year old building it out and getting more clients on top of it, >> it's like really trying to change the airplane engine in 30,000 feet. Or, in your case, you guys were taken off and from the runway. How has that been? It's been growing pains, of course. Unlearning What? What's going on? What have you learned? Give us the update on >> changing the engine while the plane is flying, and we've used that analogy quite a bit in the labs and way have to show relevance in this market. You know, this market is probably the fastest face technical market I think I've ever been in, and it's moving at such a rapid pace. We had to ship a lot of technology out last year is well, we have every new middleware group in IBM. Putting service is on top of blue mix, so let's get it out there. Let's get it out fast. Now, of course, this year we're gonna harden it up a little bit as well. So more architectures, more points of view. Better look on how this stuff works together hardening up our container strategy, pulling it all the way back to the virtual machine. So both continue to expand it out but let's make it enterprise grade at the same time. >> And also, some differentiation with Watts has been a big play around Catnip. Yeah, really is different because right now with the quote, um, market the way it is court monetization is on number one's mind. Start from startups to enterprises. If you're in business, you want you're top line if you're starting to get monetization. So there's a little bit of IBM in here for people to take in. Well, >> you know, if you look at Watson, you know, when we first started with it, you know, it was this very large big chunk of software that she had to buy. And and we work with Mike Rodents Team toe. Can we chop it up into a set of service is Let's really make this a set of AP eyes, and we started noticing, you know, you saw in Main stage the other day out from Otis. You know, this was a pure startup. He's started picking up the social semantics. Let's pick up the you know, some of the works to text etcetera, conversions, and all of a sudden they're starting to add it in. They said they would have never had access to this technology before way Have that a P I said. Not growing up to 28 we announced a couple cool things this morning. We even showed how would improve your dating life. Probably need some of that with my wife is well to translate between the sexes there, but what people are doing with it now, it's kind of like blowing people. His mind is far beyond what the initial exception waas. >> So your team of your niche is when they get right. It's a large team. It's, but it's a new initiative. New Justice unit, New role for you Talk about that >> way. Kinda had >> a couple pockets of this, but way clearly found that getting clients to the cloud is both a technology challenge as well as a cultural challenge as well. So he brought together some technical experts to kind of help through that entire life chain help up front. You know, many clients are trying to figure out what their overall cloud strategy is, where they truly today and where do they want to get to be? And how can we help him with a road map? That kind of helps them through the transition. Many accounts are very comfortable with the only wanting to be private and only glimpsing forward Thio Public Cloud Helping us bridge across that as well. Then we have the lab service's teams and these air the rial ninjas, the Navy seals. They go as low as you can go and what they're helping. A good way. Yeah, that's good. That's good. That's why they're helping with this very specific technical issue. Technical deployments. A lot of our dedicated local environment. These guys, they're they're really helping it wire in a cz Well, and then we have the garages, you know, we're up Thio. Five of those were going. We announced four new Blockchain garages as well. And this is where firms air coming in to kind of explore do the innovative type project as well. So I think all the way from the initial inception through rolling it out into production, having that team to be able to support him across the >> board. And so this capability existed in IBM previously, But it existed in a sort of bespoke fashion that coordinated >> couple pockets here and there. We always have supports. We had various pockets a lap service's. But we won't really wanna have the capability of seeing that client all the way through their journey, bringing it all under me. We now can easily pass the baton, Handoff says. We need to have that consistent skill there with the clients all the way through their >> journey and is the What's the life cycle of these service is? Is it Is it both pre sales in and post there? Just posted >> many times we'll get involved like our cloud advisers would get involved. Presale. They'll say a specific workload wants to go to the cloud. What are the steps we need to take to make that happen? A CZ well, with our Laps Service's teams, you know, we kind of have, you know, anywhere from a 4 to 6 week engagement. Thio do a specific technology. Let's get it in place. Let's get it wired in et cetera, and then in the garage is you know, we could just take a very novel idea and get it up to, ah, minimal viable product in about a six week period. So again, we're not doing dance lessons for life but strategically placing key skills in with accounts toe. Help him get over that next hump of their journey. >> Steve, when you look at the spectrum from from public all the way down to private and everything in between are you, I wonder if you could describe the level of capability that you are able to achieve with the best practice on Prem with regard to cloud ability. It's service is all the wonderful attributes of child that we've come to know and love. Are you able to, you know, somewhat replicate that roughly replicate that largely replicate, exactly. Replicate that. Where are we today? >> Yeah, I think >> it's a great question. I think. You know, I think most of the clients that we're dealing with have been dealing with some virtualized infrastructure, probably more VMC as they as they've been kind of progressing. That story. One of the things we did it IBM is Could we bring a true cloud infrastructure back behind the firewall? Could we bring an open stack? We bring a cloud foundry base past all the way back through because the goal, of course, is if we could have the same infrastructure private, dedicated and public as they continue to grow and got more comfortable with the public cloud that could start taking work clothes that they had built in one location and start to migrate it out with you. That that local cloud the Maur used for EJ cases. So taking that system of record and building a p i's and allowing to do extensions to that allowing you access into data records that you have today dealing with a lot of extension type cases, you know the core application still needs to be federally regulated. It needs to be under compliance domain. It's gotta be under audit. But maybe I wantto connect it in with a Fitbit or connected in with with a lot Soon are connected in with the Internet of things sensor. I gotta go public cloud for that as well. So locally we can bring that same infrastructure in and then they could doom or service. Is that extended out in the hybrid scenario >> code basis? Because this has come up. Oracle claims this is their big claim to fame. That code base is the same on premise hybrid public. Is that an issue with that? Is that just their marketing, or does it matter what's IBM take on this? >> But we've done ah lot of work with the open standard communities to let's get to a true reference implementation. So on open Stack, we've been doing a lot of work with them, and this is one of the reasons we picked up the Blue box acquisition. Could we really provide a standard open stack locally and also replicate that dedicated and, of course, have it match a reference architecture in public as well? We've also done the same thing with clout. Foundry worked with Sam Ram G to be one of the first vendors, have a certified cloud. Foundry instance is the same local dedicated in public. I think that's kind of the Holy Grail. If you could get the same infrastructural base across all, three, magic can happen. >> But management's important and integration piece becomes the new complexity. I mean, I would say it sounds easy, but it's really hard. Okay, developing in the clouds. Easy, easier ways always used to be right, right well, but not for large enterprises. The integration becomes that new kind of like criteria, right? That separates kind of the junior from the senior type players. I mean do you see the same thing and what we believe >> we do? I think there's usually two issues. We start to see that this model looks great. Let's have the same code base across all three environments. What things? We noticed that a lot of folks, when you get into Private Cloud, had tried to roll their own. You know, open Stack is an open source Project clout. Foundry is an open source project. Let's pull it down and let's see units roll it out and manage it ourselves. These air a little bit you they're very dynamic environments, and they're also a bit punishing if you don't stay current with them, both of them update on a very regular basis. And we found a lot of firms once they applied tenor well, folks to it, they just could not keep up with the right pace of change. So when the technologies we invented was a notion called relay on, this allowed us to actually to use the public cloud is our master copy and then we could provide updates to get down to the dedicated environment and down to the local. This takes the headache completely away from the firm's on trying to keep that local version current. It's not manage service, but it's kind of a new way that we can provide manage patches down to that environment. >> So one of the problems we hear in our community is and presume IBM has some visibility on this. I'm thinking about last year, John, we're at the IBM Z announcement in January, rose 1,000,000 company talked a lot about bringing transaction analytic capabilities together. But one of the problems that our community has practitioners in our community course the data for analytics. A lot of it's in the cloud and a lot of transaction data sitting, you know, on the mainframe, something. How do they bring those two together? Do I remove the data into the data center? Do I do I move pieces in how you see >> we're seeing a lot of that. A lot of it was. Bring the technology down to where the data is, and and now you know the three amount of integration you can do with public data sources, private data sources, et cetera. We're seeing a lot more of the compute want to go out to the cloud as well. You know, we've done some things like around the dash, CB Service's et cetera, where I can start to extract some of that transactional data, but maybe only need a few pieces to really make the data set. That is important to me as I move it out, so I can actually, you know, extract that record. I can actually mask it into being something brand new, and then I could minute we mix it with public data tohave. It do brand new things as well, so I think you're gonna see a lot of dynamic capability across that with or cloud computing technologies coming back behind the firewall and then more ability to release that data be intermixed with public data as well. >> What's the number one thing that you're seeing from customers that you guys were executing on? There's always the low hanging fruit for the easy winds from bringing a team of street team, if you will out. Technical service is out to clients where they really putting that gather, not their five year plans, but their one year. Of course, there's a lot of that agile going on right now. New technologies. You can't isolate one thing and break everything. Za new model. What a customer is caring about, right? What's that? What's the common thing? I think >> over there in 2015 I think the discussion changed and went from Are we going to go to the cloud or we're going to the cloud now? How are we going to do it? And the nice thing about I think a lot of enterprise architecture groups kind of took a step back to say, What do we truly have to do? What is a common platform? What is an integration layer? How do we take some of our old applications and decomposed those into a set of AP eyes? How can we then mix that with public AP eyes? So probably taking one or two projects to be proof points so they could say, this thing really has the magic associated with it. We can really build stuff fast. If we do it the right way, it's gonna be in a catalyst to have the I t. Organization now take the tough steps in what's gonna be the commonality? What common service is are we going to use and how do we start breaking up >> around things you know, we have our own data science and our backcourt operation and one of the things that we always looked at with bloom. It's way start our Amazon. But now, with blue mix, you have a couple things kind of coming together in real time. You said it's getting hard, but those hardened areas are important identity. For instance, where's the data is an instruction and structure. I want a little mongo year or something over there, but with blue mix and compose, I oh, really has a nice fit. I want to explain to the folks we talked before he came on about this new dynamic of composed Io and some of the things that are gluing around blue mix. Could you share this >> William Davis King right? And I think people look to the Cloud Data Service is air. Probably it's the most critical, the most visible, and the one we have to harden up the most is well, even though IBM has been well known for D. B two and we've been a >> wire composed right >> that we did Cognos first, and then we followed up with composed by you because recent waded about, we did compose. I know about eight months ago what we liked about it was all of your favorite flavors, you know? So your your progress, your mongo, you're you're ready. But really having it behave like Like what you would want an enterprise database to do. You can back it up. You can have multiple versions of it. We can replicate itself >> is a perfect cloud need of civic >> class. It has all the cloud properties to it and all the enterprise. Great capabilities with it. Yeah, we've got that now in public, and then you're gonna start seeing dedicated, and you want >> to go bare metal, Just go to soft layer. It's not required right on these things where this will work in the cloud, and then you get the bare metal object you want pushed up the bare metal. No problem. Well, I think >> you know it. Almost hybrid is not gonna get a new definition around it. So it's all gonna be around control and automation, more automation. You need to go all the way up to a cloud foundry where it's managing all the health, checking and keeping your apple. I've etcetera. If you want to go all the way down to bare metal so you can tune it audited et cetera. You can do that as well. I think I've got one of the broader spectrum, is there? >> I'm impressed with the composer. I got to say, Go ahead, get hotel Excited by what? I get excited by just about every way. Just love the whole Dev Ops has been just a game changer in extras. Code has been around for a while, but it's actually going totally mainstream. That's right. The benefits are just off the charts. With Mobile, we have the mobile first guys on. Earlier in the Swift, we had 10 made 12 year old kid. I mean, it's just really amazing. Now that the APS themselves aren't the discussion, it's the under the hood. That's right, so you can have an app look and feel like it's targeted for a vertical, say, retail or whatever. But the actions under the hood yeah, yeah, more than ever. Now >> it's, you know it's funny this year, you know, Dick Tino to the Devil Obsession yesterday and you're the amount of proof points we had around it last year. We were scrambling a little bit and this year it's just we always had to thin out. That's how many guys were having great success with this stuff is coming into its own. >> It totally is. And you guys are give you guys Props were running as fast as you can and you're working hard. And it's not just talk. Yeah, it's It's it's legit. I'm gonna ask you a question. What's the big learnings from last year? This year? What's happened? What do you look back and say? Wow, we really learned a lot or something that might have been Magda ified for you in this journey this past year. >> A lot of it goes back to, you know, this changing culture at IBM, you know, the amount of code we put out in two years was just just unbelievable. But I think also the IBM becoming a true cloud company. Some of that we did with our own shop some, but we did through injecting it with acquisitions. You know, like to compose Io the cloud and team, the blue box guys, et cetera. I think we got the chops now to play it play pro ball way worked very hard, Teoh. How many folks, Can we attract the blue mix? We're getting up to 20,000 week. Right now. We're starting. Get some great recognition and the successes are rolling in as well. So a lot of hard work and a lot of busted knuckles. A lot of guys are tired. Definitely, definitely straight in the game now. >> Ready for the crow bait? Taking the pro GameCube madness starts on cute madness. There were, you know, keep matched all the brackets of the Cube alumni and vote on it turns into a hack a phone because everyone stuffed the ballots. Let's talk about pro ball for next year, a CZ. You guys continue? Sure. The theme here obviously is developer. I mean, the show could be dedicated 100%. The blooming LeBlanc up there kind of going fast at the end of this booth on the clock anymore. Time >> right. Like the Star Wars trailer we had >> going up, he needed more time. So it's good props you got for this year. What's going on the road map this year? What if some of the critical goals that you guys see on your group and then just in general for the thing a >> lot of the activities were gonna be doing again is hardening the stack. I've got a brand new team now called a Solution Architecture, where we're looking at it from top to bottom, taking customer scenarios and really testing it out. How do you do? Back up. How do you do? Disaster recovery? How do you do? Multi geography, You know, things like PC I compliance. The rial enterprise problems are now coming to the class global and their global. And with security and compliance, they're changing in a very dynamic fashion. We have to show how you can do those in the cloud. You'd be amazed on how many conversations we have with Si SOS every single week. Is the cloud secure? How do we do enterprise? Great workloads. IBM is bringing that story to the cloud as well. That's the story of >> a potato that content >> Curation is unbelievable, right? That's the hardest part. And it's not that we have it fixed either. But you were doing more of aggregating it together so that we can really pull it all together. I call it the diamond Mine versus the jewelry store. You know, we always have really did you got yet? The great answers out there somewhere. But if you don't start to pull it together into a single place So one of things we did this year was launched the blue mixed garage methodology where we took all of our best practices. We took text test cases, even sample code, and brought it into a single methodology site where people start to go out, pull it down, use it, etcetera. Previously, we had it scattered all over the place, and we're gonna be doing more things like that. Bring in the assets to the programmers, things that we've tried, things we've tested being more open about it, putting in a single location. >> Well, we certainly would like to help promote that. Any kind of those kind of customer reference architectures. Happy to pump on silicon angle with the bond outlook for the vibe. I'm sorry. Five for the show things year. What's the vibe this year? You know, I think I've >> been very impressed with it, and I think, you know, I've been stepping up its game If you go down to the blue. Mixed garages are motives. A motorcycle on stage, you know, kind of getting a little more hip and happening as well. But I think the clients here and this is always about the customer stories and some of the things that we're hearing from the three guys start ups that are doing GPS logistical management 22 to the big accounts, and the big banks that you really see have embraced the cloud and doing great stories on it as well. I think people come to this show so they see what their peers were doing. And they definitely walk away with a sense that the cloud Israel it's happening and 2016. It is really going to driving it home. That has to be part of everybody. Strategy motorcycles I had put on the Harley Man. We'll take it for a spin guarantee. Come on down >> and give my wife. When I got married, it was terms of conditions. That's right. That's right. Last, Watson that Yeah, Thanks, Steve. Thanks. Taking the time and great to see you again. Congratulations. What? They get technical engagement team that you have all the work that you did that blue mix noted certainly by the cube. Congratulations and continued success with Loomis congratulating >> you guys. Well, always a pleasure. >> Okay. Cube Madness, March 15th Cube Gems go to Twitter. And speaking of jewelry, we have Cube gems hashtag Cube gems. That's the highlights of the videos up there. Real time. And, of course, we're gonna get that TV for all. All the action videos are up there right now. I'll be right back with more coverage after this short break here in Las Vegas.