(upbeat music) Developers have become the new king makers in the world of digital and cloud. The rise of containers and microservices has accelerated the transition to cloud native applications. A lot of people will talk about application architecture and the related paradigms and the benefits they bring for the process of writing and delivering new apps. But a major challenge continues to be, the how and the what when it comes to accessing, processing and getting insights from the massive amounts of data that we have to deal with in today's world. And with me are two experts from the data management world who will share with us how they think about the best techniques and practices based on what they see at large organizations who are working with data and developing so-called data-driven apps. Please welcome Maria Colgan and Gerald Venzl, two distinguish product managers from Oracle. Folks, welcome, thanks so much for coming on. >> Thanks for having us Dave. >> Thank you very much for having us. >> Okay, Maria let's start with you. So, we throw around this term data-driven, data-driven applications. What are we really talking about there? >> So data-driven applications are applications that work on a diverse set of data. So anything from spatial to sensor data, document data as well as your usual transaction processing data. And what they're going to do is they'll generate value from that data in very different ways to a traditional application. So for example, they may use machine learning, they are able to do product recommendations in the middle of a transaction. Or we could use graph to be able to identify an influencer within the community so we can target them with a specific promotion. It could also use spatial data to be able to help find the nearest stores to a particular customer. And because these apps are deployed on multiple platforms, everything from mobile devices as well as standard browsers, they need a data platform that's going to be both secure, reliable and scalable. >> Well, so when you think about how the workloads are shifting I mean, we're not talking about, you know it's not anymore a world of just your ERP or your HCM or your CRM, you know kind of the traditional operational systems. You really are seeing an explosion of these new data oriented apps. You're seeing, you know, modeling in the cloud, you are going to see more and more inferencing, inferencing at the edge. But Maria maybe you could talk a little bit about sort of the benefits that customers are seeing from developing these types of applications. I mean, why should people care about data-driven apps? >> Oh, for sure, there's massive benefits to them. I mean, probably the most obvious one for any business regardless of the industry, is that they not only allow you to understand what your customers are up to, but they allow you to be able to anticipate those customer's needs. So that helps businesses maintain that competitive edge and retain their customers. But it also helps them make data-driven decisions in real time based on actual data rather than on somebody's gut feeling or basing those decisions on historical data. So for example, you can do real-time price adjustments on products based on demand and so forth, that kind of thing. So it really changes the way people do business today. >> So Gerald, you think about the narrative in the industry everybody wants to be a platform player all your customers they are becoming software companies, they are becoming platform players. Everybody wants to be like, you know name a company that is huge trillion dollar market cap or whatever, and those are data-driven companies. And so it would seem to me that data-driven applications, there's nobody, no company really shouldn't be data-driven. Do you buy that? >> Yeah, absolutely. I mean, data-driven, and that naturally the whole industry is data-driven, right? It's like we all have information technologies about processing data and deriving information out of it. But when it comes to app development I think there is a big push to kind of like we have to do machine learning in our applications, we have to get insights from data. And when you actually look back a bit and take a step back, you see that there's of course many different kinds of applications out there as well that's not to be forgotten, right? So there is a usual front end user interfaces where really the application all it does is just entering some piece of information that's stored somewhere or perhaps a microservice that's not attached to a data to you at all but just receives or asks calls (indistinct). So I think it's not necessarily so important for every developer to kind of go on a bandwagon that they have to be data-driven. But I think it's equally important for those applications and those developers that build applications, that drive the business, that make business critical decisions as Maria mentioned before. Those guys should take really a close look into what data-driven apps means and what the data to you can actually give to them. Because what we see also happening a lot is that a lot of the things that are well known and out there just ready to use are being reimplemented in the applications. And for those applications, they essentially just ended up spending more time writing codes that will be already there and then have to maintain and debug the code as well rather than just going to market faster. >> Gerald can you talk to the prevailing approaches that developers take to build data-driven applications? What are the ones that you see? Let's dig into that a little bit more and maybe differentiate the different approaches and talk about that? >> Yeah, absolutely. I think right now the industry is like in two camps, it's like sort of a religious war going on that you'll see often happening with different architectures and so forth going on. So we have single purpose databases or data management technologies. Which are technologies that are as the name suggests build around a single purpose. So it's like, you know a typical example would be your ordinary key-value store. And a key-value store all it does is it allows you to store and retrieve a piece of data whatever that may be really, really fast but it doesn't really go beyond that. And then the other side of the house or the other camp would be multimodal databases, multimodal data management technologies. Those are technologies that allow you to store different types of data, different formats of data in the same technology in the same system alongside. And, you know, when you look at the geographics out there of what we have from technology, is pretty much any relational database or any database really has evolved into such a multimodal database. Whether that's MySQL that allows you to store or chase them alongside relational or even a MongoDB that allows you to do or gives you native graph support since (mumbles) and as well alongside the adjacent support. >> Well, it's clearly a trend in the industry. We've talked about this a lot in The Cube. We know where Oracle stands on this. I mean, you just mentioned MySQL but I mean, Oracle Databases you've been extending, you've mentioned JSON, we've got blockchain now in there you're infusing, you know ML and AI into the database, graph database capabilities, you know on and on and on. We talked a lot about we compared that to Amazon which is kind of the right tool, the right job approach. So maybe you could talk about, you know, your point of view, the benefits for developers of using that converged database if I can use that word approach being able to store multiple data formats? Why do you feel like that's a better approach? >> Yeah, I think on a high level it comes down to complexity. You are actually avoiding additional complexity, right? So not every use case that you have necessarily warrants to have yet another data management technology or yet the special build technology for managing that data, right? It's like many use cases that we see out there happily want to just store a piece of a chase and document, a piece of chase in a database and then perhaps retrieve it again afterwards so write some simple queries over it. And you really don't have to get a new database technology or a NoSQL database into the mix if you already have some to just fulfill that exact use case. You could just happily store that information as well in the database you already have. And what it really comes down to is the learning curve for developers, right? So it's like, as you use the same technology to store other types of data, you don't have to learn a new technology, you don't have to associate yourself with new and learn new drivers. You don't have to find new frameworks and you don't have to know how to necessarily operate or best model your data for that database. You can essentially just reuse your knowledge of the technology as well as the libraries and code you have already built in house perhaps in another application, perhaps, you know framework that you used against the same technology because it is still the same technology. So, kind of all comes down again to avoiding complexity rather than not fragmenting you know, the many different technologies we have. If you were to look at the different data formats that are out there today it's like, you know, you would end up with many different databases just to store them if you were to fully religiously follow the single purpose best built technology for every use case paradigm, right? And then you would just end up having to manage many different databases more than actually focusing on your app and getting value to your business or to your user. >> Okay, so I get that and I buy that by the way. I mean, especially if you're a larger organization and you've got all these projects going on but before we go back to Maria, Gerald, I want to just, I want to push on that a little bit. Because the counter to that argument would be in the analogy. And I wonder if you, I'd love for you to, you know knock this analogy off the blocks. The counter would be okay, Oracle is the Swiss Army knife and it's got, you know, all in one. But sometimes I need that specialized long screwdriver and I go into my toolbox and I grab that. It's better than the screwdriver in my Swiss Army knife. Why, are you the Swiss Army knife of databases? Or are you the all-in-one have that best of breed screwdriver for me? How do you think about that? >> Yeah, that's a fantastic question, right? And I think it's first of all, you have to separate between Oracle the company that has actually multiple data management technologies and databases out there as you said before, right? And Oracle Database. And I think Oracle Database is definitely a Swiss Army knife has many capabilities of since the last 40 years, you know that we've seen object support coming that's still in the Oracle Database today. We have seen XML coming, it's still in the Oracle Database, graph, spatial, et cetera. And so you have many different ways of managing your data and then on top of that going into the converge, not only do we allow you to store the different data model in there but we actually allow you also to, you apply all the security policies and so forth on top of it something Maria can talk more about the mission around converged database. I would also argue though that for some aspects, we do actually have to or add a screwdriver that you talked about as well. So especially in the relational world people get very quickly hung up on this idea that, oh, if you only do rows and columns, well, that's kind of what you put down on disk. And that was never true, it's the relational model is actually a logical model. What's probably being put down on disk is blocks that align themselves nice with block storage and always has been. So that allows you to actually model and process the data sort of differently. And one common example or one good example that we have that we introduced a couple of years ago was when, column and databases were very strong and you know, the competition came it's like, yeah, we have In-Memory column that stores now they're so much better. And we were like, well, orienting the data role-based or column-based really doesn't matter in the sense that we store them as blocks on disks. And so we introduced the in memory technology which gives you an In-Memory column, a representation of your data as well alongside your relational. So there is an example where you go like, well, actually you know, if you have this use case of the column or analytics all In-Memory, I would argue Oracle Database is also that screwdriver you want to go down to and gives you that capability. Because not only gives you representation in columnar, but also which many people then forget all the analytic power on top of SQL. It's one thing to store your data columnar, it's a completely different story to actually be able to run analytics on top of that and having all the built-in functionalities and stuff that you want to do with the data on top of it as you analyze it. >> You know, that's a great example, the kilometer 'cause I remember there was like a lot of hype around it. Oh, it's the Oracle killer, you know, at Vertica. Vertica is still around but, you know it never really hit escape velocity. But you know, good product, good company, whatever. Natezza, it kind of got buried inside of IBM. ParXL kind of became, you know, red shift with that deal so that kind of went away. Teradata bought a company, I forget which company it bought but. So that hype kind of disapated and now it's like, oh yeah, columnar. It's kind of like In-Memory, we've had a In-Memory databases ever since we've had databases you know, it's a kind of a feature not a sector. But anyway, Maria, let's come back to you. You've got a lot of customer experience. And you speak with a lot of companies, you know during your time at Oracle. What else are you seeing in terms of the benefits to this approach that might not be so intuitive and obvious right away? >> I think one of the biggest benefits to having a multimodel multiworkload or as we call it a converged database, is the fact that you can get greater data synergy from it. In other words, you can utilize all these different techniques and data models to get better value out of that data. So things like being able to do real-time machine learning, fraud detection inside a transaction or being able to do a product recommendation by accessing three different data models. So for example, if I'm trying to recommend a product for you Dave, I might use graph analytics to be able to figure out your community. Not just your friends, but other people on our system who look and behave just like you. Once I know that community then I can go over and see what products they bought by looking up our product catalog which may be stored as JSON. And then on top of that I can then see using the key-value what products inside that catalog those community members gave a five star rating to. So that way I can really pinpoint the right product for you. And I can do all of that in one transaction inside the database without having to transform that data into different models or God forbid, access different systems to be able to get all of that information. So it really simplifies how we can generate that value from the data. And of course, the other thing our customers love is when it comes to deploying data-driven apps, when you do it on a converged database it's much simpler because it is that standard data platform. So you're not having to manage multiple independent single purpose databases. You're not having to implement the security and the high availability policies, you know across a bunch of different diverse platforms. All of that can be done much simpler with a converged database 'cause the DBA team of course, is going to just use that standard set of tools to manage, monitor and secure those systems. >> Thank you for that. And you know, it's interesting, you talk about simplification and you are in Juan's organization so you've big focus on mission critical. And so one of the things that I think is often overlooked well, we talk about all the time is recovery. And if things are simpler, recovery is faster and easier. And so it's kind of the hallmark of Oracle is like the gold standard of the toughest apps, the most mission critical apps. But I wanted to get to the cloud Maria. So because everything is going to the cloud, right? Not all workloads are going to the cloud but everybody is talking about the cloud. Everybody has cloud first mentality and so yes, it's a hybrid world. But the natural next question is how do you think the cloud fits into this world of data-driven apps? >> I think just like any app that you're developing, the cloud helps to accelerate that development. And of course the deployment of these data-driven applications. 'Cause if you think about it, the developer is instantly able to provision a converged database that Oracle will automatically manage and look after for them. But what's great about doing something like that if you use like our autonomous database service is that it comes in different flavors. So you can get autonomous transaction processing, data warehousing or autonomous JSON so that the developer is going to get a database that's been optimized for their specific use case, whatever they are trying to solve. And it's also going to contain all of that great functionality and capabilities that we've been talking about. So what that really means to the developer though is as the project evolves and inevitably the business needs change a little, there's no need to panic when one of those changes comes in because your converged database or your autonomous database has all of those additional capabilities. So you can simply utilize those to able to address those evolving changes in the project. 'Cause let's face it, none of us normally know exactly what we need to build right at the very beginning. And on top of that they also kind of get a built-in buddy in the cloud, especially in the autonomous database. And that buddy comes in the form of built-in workload optimizations. So with the autonomous database we do things like automatic indexing where we're using machine learning to be that buddy for the developer. So what it'll do is it'll monitor the workload and see what kind of queries are being run on that system. And then it will actually determine if there are indexes that should be built to help improve the performance of that application. And not only does it bill those indexes but it verifies that they help improve the performance before publishing it to the application. So by the time the developer is finished with that app and it's ready to be deployed, it's actually also been optimized by the developers buddy, the Oracle autonomous database. So, you know, it's a really nice helping hand for developers when they're building any app especially data-driven apps. >> I like how you sort of gave us, you know the truth here is you don't always know where you're going when you're building an app. It's like it goes from you are trying to build it and they will come to start building it and we'll figure out where it's going to go. With Agile that's kind of how it works. But so I wonder, can you give some examples of maybe customers or maybe genericize them if you need to. Data-driven apps in the cloud where customers were able to drive more efficiency, where the cloud buddy allowed the customers to do more with less? >> No, we have tons of these but I'll try and keep it to just a couple. One that comes to mind straight away is retrace. These folks built a blockchain app in the Oracle Cloud that allows manufacturers to actually share the supply chain with the consumer. So the consumer can see exactly, who made their product? Using what raw materials? Where they were sourced from? How it was done? All of that is visible to the consumer. And in order to be able to share that they had to work on a very diverse set of data. So they had everything from JSON documents to images as well as your traditional transactions in there. And they store all of that information inside the Oracle autonomous database, they were able to build their app and deploy it on the cloud. And they were able to do all of that very, very quickly. So, you know, that ability to work on multiple different data types in a single database really helped them build that product and get it to market in a very short amount of time. Another customer that's doing something really, really interesting is MindSense. So these guys operate the largest mines in Canada, Chile, and Peru. But what they do is they put these x-ray devices on the massive mechanical shovels that are at the cove or at the mine face. And what that does is it senses the contents of the buckets inside these mining machines. And it's looking to see at that content, to see how it can optimize the processing of the ore inside in that bucket. So they're looking to minimize the amount of power and water that it's going to take to process that. And also of course, minimize the amount of waste that's going to come out of that project. So all of that sensor data is sent into an autonomous database where it's going to be processed by a whole host of different users. So everything from the mine engineers to the geo scientists, to even their own data scientists utilize that data to drive their business forward. And what I love about these guys is they're not happy with building just one app. MindSense actually use our built-in low core development environment, APEX that comes as part of the autonomous database and they actually produce applications constantly for different aspects of their business using that technology. And it's actually able to accelerate those new apps to the business. It takes them now just a couple of days or weeks to produce an app instead of months or years to build those new apps. >> Great, thank you for that Maria. Gerald, I'm going to push you again. So, I said upfront and talked about microservices and the cloud and containers and you know, anybody in the developer space follows that very closely. But some of the things that we've been talking about here people might look at that and say, well, they're kind of antithetical to microservices. This is our Oracles monolithic approach. But when you think about the benefits of microservices, people want freedom of choice, technology choice, seen as a big advantage of microservices and containers. How do you address such an argument? >> Yeah, that's an excellent question and I get that quite often. The microservices architecture in general as I said before had architectures, Linux distributions, et cetera. It's kind of always a bit of like there's an academic approach and there's a pragmatic approach. And when you look at the microservices the original definitions that came out at the early 2010s. They actually never said that each microservice has to have a database. And they also never said that if a microservice has a database, you have to use a different technology for each microservice. Just like they never said, you have to write a microservice in a different programming language, right? So where I'm going with this is like, yes you know, sometimes when you look at some vendors out there, some niche players, they push this message or they jump on this academic approach of like each microservice has the best tool at hand or I'd use a different database for your purpose, et cetera. Which almost often comes across like us. You know, we want to stay part of the conversation. Nothing stops a developer from, you know using a multimodal database for the microservice and just using that as a document store, right? Or just using that as a relational database. And, you know, sometimes I mean, it was actually something that happened that was really interesting yesterday I don't know whether you follow Dave or not. But Facebook had an outage yesterday, right? And Facebook is one of those companies that are seen as the Silicon Valley, you know know how to do microservices companies. And when you add through the outage, well, what happened, right? Some unfortunate logical error with configuration as a force that took a database cluster down. So, you know, there you have it where you go like, well, maybe not every microservice is actually in fact talking to its own database or its own special purpose database. I think there, you know, well, what we should, the industry should be focusing much more on this argument of which technology to use? What's the right tool for a job? Is more to ask themselves, what business problem actually are we trying to solve? And therefore what's the right approach and the right technology for this. And so therefore, just as I said before, you know multimodal databases they do have strong benefits. They have many built-in functionalities that are already there and they allow you to reduce this complexity of having to know many different technologies, right? And so it's not only to store different data models either you know, treat a multimodal database as a chasing documents store or a relational database but most databases are multimodal since 20 plus years. But it's also actually being able to perhaps if you store that data together, you can perhaps actually derive additional value for somebody else but perhaps not for your application. But like for example, if you were to use Oracle Database you can actually write queries on top of all of that data. It doesn't really matter for our query engine whether it's the data is format that then chase or the data is formatted in rows and columns you can just rather than query over it. And that's actually very powerful for those guys that have to, you know get the reporting done the end of the day, the end of the week. And for those guys that are the data scientists that they want to figure out, you know which product performed really well or can we tweak something here and there. When you look into that space you still see a huge divergence between the guys to put data in kind of the altarpiece style and guys that try to derive new insights. And there's still a lot of ETL going around and, you know we have big data technologies that some of them come and went and some of them came in that are still around like Apache Spark which is still like a SQL engine on top of any of your data kind of going back to the same concept. And so I will say that, you know, for developers when we look at microservices it's like, first of all, is the argument you were making because the vendor or the technology you want to use tells you this argument or, you know, you kind of want to have an argument to use a specific technology? Or is it really more because it is the best technology, to best use for this given use case for this given application that you have? And if so there's of course, also nothing wrong to use a single purpose technology either, right? >> Yeah, I mean, whenever I talk about Oracle I always come back to the most important applications, the mission critical. It's very difficult to architect databases with microservices and containers. You have to be really, really careful. And so and again, it comes back to what we were talking before about with Maria that the complexity and the recovery. But Gerald I want to stay with you for a minute. So there's other data management technologies popping out there. I mean, I've seen some people saying, okay just leave the data in an S3 bucket. We can query that, then we've got some magic sauce to do that. And so why are you optimistic about you know, traditional database technology going forward? >> I would say because of the history of databases. So one thing that once struck me when I came to Oracle and then got to meet great people like Juan Luis and Andy Mendelsohn who had been here for a long, long time. I come to realization that relational databases are around for about 45 years now. And, you know, I was like, I'm too young to have been around then, right? So I was like, what else was around 45 years? It's like just the tech stack that we have today. It's like, how does this look like? Well, Linux only came out in 93. Well, databases pre-date Linux a lot rather than as I started digging I saw a lot of technologies come and go, right? And you mentioned before like the technologies that data management systems that we had that came and went like the columnar databases or XML databases, object databases. And even before relational databases before Cot gave us the relational model there were apparently these networks stores network databases which to some extent look very similar to adjacent documents. There wasn't a harder storing data and a hierarchy to format. And, you know when you then start actually reading the Cot paper and diving a little bit more into the relation model, that's I think one important crux in there that most of the industry keeps forgetting or it hasn't been around to even know. And that is that when Cot created the relational model, he actually focused not so much on the application putting the data in, but on future users and applications still being able to making sense out of the data, right? And that's kind of like I said before we had those network models, we had XML databases you have adjacent documents stores. And the one thing that they all have along with it is like the application that puts the data in decides the structure of the data. And that's all well and good if you had an application of the developer writing an application. It can become really tricky when 10 years later you still want to look at that data and the application that the developer is no longer around then you go like, what does this all mean? Where is the structure defined? What is this attribute? What does it mean? How does it correlate to others? And the one thing that people tend to forget is that it's actually the data that's here to stay not someone who does the applications where it is. Ideally, every company wants to store every single byte of data that they have because there might be future value in it. Economically may not make sense that's now much more feasible than just years ago. But if you could, why wouldn't you want to store all your data, right? And sometimes you actually have to store the data for seven years or whatever because the laws require you to. And so coming back then and you know, like 10 years from now and looking at the data and going like making sense of that data can actually become a lot more difficult and a lot more challenging than having to first figure out and how we store this data for general use. And that kind of was what the relational model was all about. We decompose the data structures into tables and columns with relationships amongst each other so therefore between each other. So that therefore if somebody wants to, you know typical example would be well you store some purchases from your web store, right? There's a customer attribute in it. There's some credit card payment information in it, just some product information on what the customer bought. Well, in the relational model if you just want to figure out which products were sold on a given day or week, you just would query the payment and products table to get the sense out of it. You don't need to touch the customer and so forth. And with the hierarchical model you have to first sit down and understand how is the structure, what is the customer? Where is the payment? You know, does the document start with the payment or does it start with the customer? Where do I find this information? And then in the very early days those databases even struggled to then not having to scan all the documents to get the data out. So coming back to your question a bit, I apologize for going on here. But you know, it's like relational databases have been around for 45 years. I actually argue it's one of the most successful software technologies that we have out there when you look in the overall industry, right? 45 years is like, in IT terms it's like from a star being the ones who are going supernova. You have said it before that many technologies coming and went, right? And just want to add a more really interesting example by the way is Hadoop and HDFS, right? They kind of gave us this additional promise of like, you know, the 2010s like 2012, 2013 the hype of Hadoop and so forth and (mumbles) and HDFS. And people are just like, just put everything into HDFS and worry about the data later, right? And we can query it and map reduce it and whatever. And we had customers actually coming to us they were like, great we have half a petabyte of data on an HDFS cluster and we have no clue what's stored in there. How do we figure this out? What are we going to do now? Now you had a big data cleansing problem. And so I think that is why databases and also data modeling is something that will not go away anytime soon. And I think databases and database technologies are here for quite a while to stay. Because many of those are people they don't think about what's happening to the data five years from now. And many of the niche players also and also frankly even Amazon you know, following with this single purpose thing is like, just use the right tool for the job for your application, right? Just pull in the data there the way you wanted. And it's like, okay, so you use technologies all over the place and then five years from now you have your data fragmented everywhere in different formats and, you know inconsistencies, and, and, and. And those are usually when you come back to this data-driven business critical business decision applications the worst case scenario you can have, right? Because now you need an army of people to actually do data cleansing. And there's not a coincidence that data science has become very, very popular the last recent years as we kind of went on with this proliferation of different database or data management technologies some of those are not even database. But I think I leave it at that. >> It's an interesting talk track because you're right. I mean, no schema on right was alluring, but it definitely created some problems. It also created an entire, you know you referenced the hyper specialized roles and did the data cleansing component. I mean, maybe technology will eventually solve that problem but it hasn't up at least up tonight. Okay, last question, Maria maybe you could start off and Gerald if you want to chime in as well it'd be great. I mean, it's interesting to watch this industry when Oracle sort of won the top database mantle. I mean, I watched it, I saw it. It was, remember it was Informix and it was (indistinct) too and of course, Microsoft you got to give them credit with SQL server, but Oracle won the database wars. And then everything got kind of quiet for awhile database was sort of boring. And then it exploded, you know, all the, you know not only SQL and the key-value stores and the cloud databases and this is really a hot area now. And when we looked at Oracle we said, okay, Oracle it's all about Oracle Database, but we've seen the kind of resurgence in MySQL which everybody thought, you know once Oracle bought Sun they were going to kill MySQL. But now we see you investing in HeatWave, TimesTen, we talked about In-Memory databases before. So where do those fit in Maria in the grand scheme? How should we think about Oracle's database portfolio? >> So there's lots of places where you'd use those different things. 'Cause just like any other industry there are going to be new and boutique use cases that are going to benefit from a more specialized product or single purpose product. So good examples off the top of my head of the kind of systems that would benefit from that would be things like a stock exchange system or a telephone exchange system. Both of those are latency critical transaction processing applications where they need microsecond response times. And that's going to exceed perhaps what you might normally get or deploy with a converged database. And so Oracle's TimesTen database our In-Memory database is perfect for those kinds of applications. But there's also a host of MySQL applications out there today and you said it yourself there Dave, HeatWave is a great place to provision and deploy those kinds of applications because it's going to run 100 times faster than AWS (mumbles). So, you know, there really is a place in the market and in our customer's systems and the needs they have for all of these different members of our database family here at Oracle. >> Yeah, well, the internet is basically running in the lamp stack so I see MySQL going away. All right Gerald, will give you the final word, bring us home. >> Oh, thank you very much. Yeah, I mean, as Maria said, I think it comes back to what we discussed before. There is obviously still needs for special technologies or different technologies than a relational database or multimodal database. Oracle has actually many more databases that people may first think of. Not only the three that we have already mentioned but there's even SP so the Oracle's NoSQL database. And, you know, on a high level Oracle is a data management company, right? And we want to give our customers the best tools and the best technology to manage all of their data. Rather than therefore there has to be a need or there should be a part of the business that also focuses on this highly specialized systems and this highly specialized technologies that address those use cases. And I think it makes perfect sense. It's like, you know, when the customer comes to Oracle they're not only getting this, take this one product you know, and if you don't like it your problem but actually you have choice, right? And choice allows you to make a decision based on what's best for you and not necessarily best for the vendor you're talking to. >> Well guys, really appreciate your time today and your insights. Maria, Gerald, thanks so much for coming on The Cube. >> Thank you very much for having us. >> And thanks for watching this Cube conversation this is Dave Vellante and we'll see you next time. (upbeat music)

(upbeat music) >> It'll be five, four, three and then silent two, one, and then you guys just follow my lead. We're just making some last minute adjustments. Like I said, we're down two hands today. So, you good Alex? Okay, are you guys ready? >> I'm ready. >> Ready. >> I got to get get one note here. >> So I noticed Maria you stopped anyway, so I have time. >> Just so they know Dave and the Boston Studio, are they both kind of concurrently be on film even when they're not speaking or will only the speaker be on film for like if Gerald's drawing while Maria is talking about-- >> Sorry but then I missed one part of my onboarding spiel. There should be, if you go into gallery there should be a label. There should be something labeled Boston live switch feed. If you pin that gallery view you'll see what our program currently being recorded is. So any time you don't see yourself on that feed is an excellent time to take a drink of water, scratch your nose, check your notes. Do whatever you got to do off screen. >> Can you give us a three shot, Alex? >> Yes, there it is. >> And then go to me, just give me a one-shot to Dave. So when I'm here you guys can take a drink or whatever >> That makes sense? >> Yeah. >> Excellent, I will get my recordings restarted and we'll open up when Dave's ready. >> All right, you guys ready? >> Ready. >> All right Steve, you go on mute. >> Okay, on me in 5, 4, 3. Developers have become the new king makers in the world of digital and cloud. The rise of containers and microservices has accelerated the transition to cloud native applications. A lot of people will talk about application architecture and the related paradigms and the benefits they bring for the process of writing and delivering new apps. But a major challenge continues to be, the how and the what when it comes to accessing, processing and getting insights from the massive amounts of data that we have to deal with in today's world. And with me are two experts from the data management world who will share with us how they think about the best techniques and practices based on what they see at large organizations who are working with data and developing so-called data-driven apps. Please welcome Maria Colgan and Gerald Venzl, two distinguish product managers from Oracle. Folks, welcome, thanks so much for coming on. >> Thanks for having us Dave. >> Thank you very much for having us. >> Okay, Maria let's start with you. So, we throw around this term data-driven, data-driven applications. What are we really talking about there? >> So data-driven applications are applications that work on a diverse set of data. So anything from spatial to sensor data, document data as well as your usual transaction processing data. And what they're going to do is they'll generate value from that data in very different ways to a traditional application. So for example, they may use machine learning, they are able to do product recommendations in the middle of a transaction. Or we could use graph to be able to identify an influencer within the community so we can target them with a specific promotion. It could also use spatial data to be able to help find the nearest stores to a particular customer. And because these apps are deployed on multiple platforms, everything from mobile devices as well as standard browsers, they need a data platform that's going to be both secure, reliable and scalable. >> Well, so when you think about how the workloads are shifting I mean, we're not talking about, you know it's not anymore a world of just your ERP or your HCM or your CRM, you know kind of the traditional operational systems. You really are seeing an explosion of these new data oriented apps. You're seeing, you know, modeling in the cloud, you are going to see more and more inferencing, inferencing at the edge. But Maria maybe you could talk a little bit about sort of the benefits that customers are seeing from developing these types of applications. I mean, why should people care about data-driven apps? >> Oh, for sure, there's massive benefits to them. I mean, probably the most obvious one for any business regardless of the industry, is that they not only allow you to understand what your customers are up to, but they allow you to be able to anticipate those customer's needs. So that helps businesses maintain that competitive edge and retain their customers. But it also helps them make data-driven decisions in real time based on actual data rather than on somebody's gut feeling or basing those decisions on historical data. So for example, you can do real-time price adjustments on products based on demand and so forth, that kind of thing. So it really changes the way people do business today. >> So Gerald, you think about the narrative in the industry everybody wants to be a platform player all your customers they are becoming software companies, they are becoming platform players. Everybody wants to be like, you know name a company that is huge trillion dollar market cap or whatever, and those are data-driven companies. And so it would seem to me that data-driven applications, there's nobody, no company really shouldn't be data-driven. Do you buy that? >> Yeah, absolutely. I mean, data-driven, and that naturally the whole industry is data-driven, right? It's like we all have information technologies about processing data and deriving information out of it. But when it comes to app development I think there is a big push to kind of like we have to do machine learning in our applications, we have to get insights from data. And when you actually look back a bit and take a step back, you see that there's of course many different kinds of applications out there as well that's not to be forgotten, right? So there is a usual front end user interfaces where really the application all it does is just entering some piece of information that's stored somewhere or perhaps a microservice that's not attached to a data to you at all but just receives or asks calls (indistinct). So I think it's not necessarily so important for every developer to kind of go on a bandwagon that they have to be data-driven. But I think it's equally important for those applications and those developers that build applications, that drive the business, that make business critical decisions as Maria mentioned before. Those guys should take really a close look into what data-driven apps means and what the data to you can actually give to them. Because what we see also happening a lot is that a lot of the things that are well known and out there just ready to use are being reimplemented in the applications. And for those applications, they essentially just ended up spending more time writing codes that will be already there and then have to maintain and debug the code as well rather than just going to market faster. >> Gerald can you talk to the prevailing approaches that developers take to build data-driven applications? What are the ones that you see? Let's dig into that a little bit more and maybe differentiate the different approaches and talk about that? >> Yeah, absolutely. I think right now the industry is like in two camps, it's like sort of a religious war going on that you'll see often happening with different architectures and so forth going on. So we have single purpose databases or data management technologies. Which are technologies that are as the name suggests build around a single purpose. So it's like, you know a typical example would be your ordinary key-value store. And a key-value store all it does is it allows you to store and retrieve a piece of data whatever that may be really, really fast but it doesn't really go beyond that. And then the other side of the house or the other camp would be multimodal databases, multimodal data management technologies. Those are technologies that allow you to store different types of data, different formats of data in the same technology in the same system alongside. And, you know, when you look at the geographics out there of what we have from technology, is pretty much any relational database or any database really has evolved into such a multimodal database. Whether that's MySQL that allows you to store or chase them alongside relational or even a MongoDB that allows you to do or gives you native graph support since (mumbles) and as well alongside the adjacent support. >> Well, it's clearly a trend in the industry. We've talked about this a lot in The Cube. We know where Oracle stands on this. I mean, you just mentioned MySQL but I mean, Oracle Databases you've been extending, you've mentioned JSON, we've got blockchain now in there you're infusing, you know ML and AI into the database, graph database capabilities, you know on and on and on. We talked a lot about we compared that to Amazon which is kind of the right tool, the right job approach. So maybe you could talk about, you know, your point of view, the benefits for developers of using that converged database if I can use that word approach being able to store multiple data formats? Why do you feel like that's a better approach? >> Yeah, I think on a high level it comes down to complexity. You are actually avoiding additional complexity, right? So not every use case that you have necessarily warrants to have yet another data management technology or yet the special build technology for managing that data, right? It's like many use cases that we see out there happily want to just store a piece of a chase and document, a piece of chase in a database and then perhaps retrieve it again afterwards so write some simple queries over it. And you really don't have to get a new database technology or a NoSQL database into the mix if you already have some to just fulfill that exact use case. You could just happily store that information as well in the database you already have. And what it really comes down to is the learning curve for developers, right? So it's like, as you use the same technology to store other types of data, you don't have to learn a new technology, you don't have to associate yourself with new and learn new drivers. You don't have to find new frameworks and you don't have to know how to necessarily operate or best model your data for that database. You can essentially just reuse your knowledge of the technology as well as the libraries and code you have already built in house perhaps in another application, perhaps, you know framework that you used against the same technology because it is still the same technology. So, kind of all comes down again to avoiding complexity rather than not fragmenting you know, the many different technologies we have. If you were to look at the different data formats that are out there today it's like, you know, you would end up with many different databases just to store them if you were to fully religiously follow the single purpose best built technology for every use case paradigm, right? And then you would just end up having to manage many different databases more than actually focusing on your app and getting value to your business or to your user. >> Okay, so I get that and I buy that by the way. I mean, especially if you're a larger organization and you've got all these projects going on but before we go back to Maria, Gerald, I want to just, I want to push on that a little bit. Because the counter to that argument would be in the analogy. And I wonder if you, I'd love for you to, you know knock this analogy off the blocks. The counter would be okay, Oracle is the Swiss Army knife and it's got, you know, all in one. But sometimes I need that specialized long screwdriver and I go into my toolbox and I grab that. It's better than the screwdriver in my Swiss Army knife. Why, are you the Swiss Army knife of databases? Or are you the all-in-one have that best of breed screwdriver for me? How do you think about that? >> Yeah, that's a fantastic question, right? And I think it's first of all, you have to separate between Oracle the company that has actually multiple data management technologies and databases out there as you said before, right? And Oracle Database. And I think Oracle Database is definitely a Swiss Army knife has many capabilities of since the last 40 years, you know that we've seen object support coming that's still in the Oracle Database today. We have seen XML coming, it's still in the Oracle Database, graph, spatial, et cetera. And so you have many different ways of managing your data and then on top of that going into the converge, not only do we allow you to store the different data model in there but we actually allow you also to, you apply all the security policies and so forth on top of it something Maria can talk more about the mission around converged database. I would also argue though that for some aspects, we do actually have to or add a screwdriver that you talked about as well. So especially in the relational world people get very quickly hung up on this idea that, oh, if you only do rows and columns, well, that's kind of what you put down on disk. And that was never true, it's the relational model is actually a logical model. What's probably being put down on disk is blocks that align themselves nice with block storage and always has been. So that allows you to actually model and process the data sort of differently. And one common example or one good example that we have that we introduced a couple of years ago was when, column and databases were very strong and you know, the competition came it's like, yeah, we have In-Memory column that stores now they're so much better. And we were like, well, orienting the data role-based or column-based really doesn't matter in the sense that we store them as blocks on disks. And so we introduced the in memory technology which gives you an In-Memory column, a representation of your data as well alongside your relational. So there is an example where you go like, well, actually you know, if you have this use case of the column or analytics all In-Memory, I would argue Oracle Database is also that screwdriver you want to go down to and gives you that capability. Because not only gives you representation in columnar, but also which many people then forget all the analytic power on top of SQL. It's one thing to store your data columnar, it's a completely different story to actually be able to run analytics on top of that and having all the built-in functionalities and stuff that you want to do with the data on top of it as you analyze it. >> You know, that's a great example, the kilometer 'cause I remember there was like a lot of hype around it. Oh, it's the Oracle killer, you know, at Vertica. Vertica is still around but, you know it never really hit escape velocity. But you know, good product, good company, whatever. Natezza, it kind of got buried inside of IBM. ParXL kind of became, you know, red shift with that deal so that kind of went away. Teradata bought a company, I forget which company it bought but. So that hype kind of disapated and now it's like, oh yeah, columnar. It's kind of like In-Memory, we've had a In-Memory databases ever since we've had databases you know, it's a kind of a feature not a sector. But anyway, Maria, let's come back to you. You've got a lot of customer experience. And you speak with a lot of companies, you know during your time at Oracle. What else are you seeing in terms of the benefits to this approach that might not be so intuitive and obvious right away? >> I think one of the biggest benefits to having a multimodel multiworkload or as we call it a converged database, is the fact that you can get greater data synergy from it. In other words, you can utilize all these different techniques and data models to get better value out of that data. So things like being able to do real-time machine learning, fraud detection inside a transaction or being able to do a product recommendation by accessing three different data models. So for example, if I'm trying to recommend a product for you Dave, I might use graph analytics to be able to figure out your community. Not just your friends, but other people on our system who look and behave just like you. Once I know that community then I can go over and see what products they bought by looking up our product catalog which may be stored as JSON. And then on top of that I can then see using the key-value what products inside that catalog those community members gave a five star rating to. So that way I can really pinpoint the right product for you. And I can do all of that in one transaction inside the database without having to transform that data into different models or God forbid, access different systems to be able to get all of that information. So it really simplifies how we can generate that value from the data. And of course, the other thing our customers love is when it comes to deploying data-driven apps, when you do it on a converged database it's much simpler because it is that standard data platform. So you're not having to manage multiple independent single purpose databases. You're not having to implement the security and the high availability policies, you know across a bunch of different diverse platforms. All of that can be done much simpler with a converged database 'cause the DBA team of course, is going to just use that standard set of tools to manage, monitor and secure those systems. >> Thank you for that. And you know, it's interesting, you talk about simplification and you are in Juan's organization so you've big focus on mission critical. And so one of the things that I think is often overlooked well, we talk about all the time is recovery. And if things are simpler, recovery is faster and easier. And so it's kind of the hallmark of Oracle is like the gold standard of the toughest apps, the most mission critical apps. But I wanted to get to the cloud Maria. So because everything is going to the cloud, right? Not all workloads are going to the cloud but everybody is talking about the cloud. Everybody has cloud first mentality and so yes, it's a hybrid world. But the natural next question is how do you think the cloud fits into this world of data-driven apps? >> I think just like any app that you're developing, the cloud helps to accelerate that development. And of course the deployment of these data-driven applications. 'Cause if you think about it, the developer is instantly able to provision a converged database that Oracle will automatically manage and look after for them. But what's great about doing something like that if you use like our autonomous database service is that it comes in different flavors. So you can get autonomous transaction processing, data warehousing or autonomous JSON so that the developer is going to get a database that's been optimized for their specific use case, whatever they are trying to solve. And it's also going to contain all of that great functionality and capabilities that we've been talking about. So what that really means to the developer though is as the project evolves and inevitably the business needs change a little, there's no need to panic when one of those changes comes in because your converged database or your autonomous database has all of those additional capabilities. So you can simply utilize those to able to address those evolving changes in the project. 'Cause let's face it, none of us normally know exactly what we need to build right at the very beginning. And on top of that they also kind of get a built-in buddy in the cloud, especially in the autonomous database. And that buddy comes in the form of built-in workload optimizations. So with the autonomous database we do things like automatic indexing where we're using machine learning to be that buddy for the developer. So what it'll do is it'll monitor the workload and see what kind of queries are being run on that system. And then it will actually determine if there are indexes that should be built to help improve the performance of that application. And not only does it bill those indexes but it verifies that they help improve the performance before publishing it to the application. So by the time the developer is finished with that app and it's ready to be deployed, it's actually also been optimized by the developers buddy, the Oracle autonomous database. So, you know, it's a really nice helping hand for developers when they're building any app especially data-driven apps. >> I like how you sort of gave us, you know the truth here is you don't always know where you're going when you're building an app. It's like it goes from you are trying to build it and they will come to start building it and we'll figure out where it's going to go. With Agile that's kind of how it works. But so I wonder, can you give some examples of maybe customers or maybe genericize them if you need to. Data-driven apps in the cloud where customers were able to drive more efficiency, where the cloud buddy allowed the customers to do more with less? >> No, we have tons of these but I'll try and keep it to just a couple. One that comes to mind straight away is retrace. These folks built a blockchain app in the Oracle Cloud that allows manufacturers to actually share the supply chain with the consumer. So the consumer can see exactly, who made their product? Using what raw materials? Where they were sourced from? How it was done? All of that is visible to the consumer. And in order to be able to share that they had to work on a very diverse set of data. So they had everything from JSON documents to images as well as your traditional transactions in there. And they store all of that information inside the Oracle autonomous database, they were able to build their app and deploy it on the cloud. And they were able to do all of that very, very quickly. So, you know, that ability to work on multiple different data types in a single database really helped them build that product and get it to market in a very short amount of time. Another customer that's doing something really, really interesting is MindSense. So these guys operate the largest mines in Canada, Chile, and Peru. But what they do is they put these x-ray devices on the massive mechanical shovels that are at the cove or at the mine face. And what that does is it senses the contents of the buckets inside these mining machines. And it's looking to see at that content, to see how it can optimize the processing of the ore inside in that bucket. So they're looking to minimize the amount of power and water that it's going to take to process that. And also of course, minimize the amount of waste that's going to come out of that project. So all of that sensor data is sent into an autonomous database where it's going to be processed by a whole host of different users. So everything from the mine engineers to the geo scientists, to even their own data scientists utilize that data to drive their business forward. And what I love about these guys is they're not happy with building just one app. MindSense actually use our built-in low core development environment, APEX that comes as part of the autonomous database and they actually produce applications constantly for different aspects of their business using that technology. And it's actually able to accelerate those new apps to the business. It takes them now just a couple of days or weeks to produce an app instead of months or years to build those new apps. >> Great, thank you for that Maria. Gerald, I'm going to push you again. So, I said upfront and talked about microservices and the cloud and containers and you know, anybody in the developer space follows that very closely. But some of the things that we've been talking about here people might look at that and say, well, they're kind of antithetical to microservices. This is our Oracles monolithic approach. But when you think about the benefits of microservices, people want freedom of choice, technology choice, seen as a big advantage of microservices and containers. How do you address such an argument? >> Yeah, that's an excellent question and I get that quite often. The microservices architecture in general as I said before had architectures, Linux distributions, et cetera. It's kind of always a bit of like there's an academic approach and there's a pragmatic approach. And when you look at the microservices the original definitions that came out at the early 2010s. They actually never said that each microservice has to have a database. And they also never said that if a microservice has a database, you have to use a different technology for each microservice. Just like they never said, you have to write a microservice in a different programming language, right? So where I'm going with this is like, yes you know, sometimes when you look at some vendors out there, some niche players, they push this message or they jump on this academic approach of like each microservice has the best tool at hand or I'd use a different database for your purpose, et cetera. Which almost often comes across like us. You know, we want to stay part of the conversation. Nothing stops a developer from, you know using a multimodal database for the microservice and just using that as a document store, right? Or just using that as a relational database. And, you know, sometimes I mean, it was actually something that happened that was really interesting yesterday I don't know whether you follow Dave or not. But Facebook had an outage yesterday, right? And Facebook is one of those companies that are seen as the Silicon Valley, you know know how to do microservices companies. And when you add through the outage, well, what happened, right? Some unfortunate logical error with configuration as a force that took a database cluster down. So, you know, there you have it where you go like, well, maybe not every microservice is actually in fact talking to its own database or its own special purpose database. I think there, you know, well, what we should, the industry should be focusing much more on this argument of which technology to use? What's the right tool for a job? Is more to ask themselves, what business problem actually are we trying to solve? And therefore what's the right approach and the right technology for this. And so therefore, just as I said before, you know multimodal databases they do have strong benefits. They have many built-in functionalities that are already there and they allow you to reduce this complexity of having to know many different technologies, right? And so it's not only to store different data models either you know, treat a multimodal database as a chasing documents store or a relational database but most databases are multimodal since 20 plus years. But it's also actually being able to perhaps if you store that data together, you can perhaps actually derive additional value for somebody else but perhaps not for your application. But like for example, if you were to use Oracle Database you can actually write queries on top of all of that data. It doesn't really matter for our query engine whether it's the data is format that then chase or the data is formatted in rows and columns you can just rather than query over it. And that's actually very powerful for those guys that have to, you know get the reporting done the end of the day, the end of the week. And for those guys that are the data scientists that they want to figure out, you know which product performed really well or can we tweak something here and there. When you look into that space you still see a huge divergence between the guys to put data in kind of the altarpiece style and guys that try to derive new insights. And there's still a lot of ETL going around and, you know we have big data technologies that some of them come and went and some of them came in that are still around like Apache Spark which is still like a SQL engine on top of any of your data kind of going back to the same concept. And so I will say that, you know, for developers when we look at microservices it's like, first of all, is the argument you were making because the vendor or the technology you want to use tells you this argument or, you know, you kind of want to have an argument to use a specific technology? Or is it really more because it is the best technology, to best use for this given use case for this given application that you have? And if so there's of course, also nothing wrong to use a single purpose technology either, right? >> Yeah, I mean, whenever I talk about Oracle I always come back to the most important applications, the mission critical. It's very difficult to architect databases with microservices and containers. You have to be really, really careful. And so and again, it comes back to what we were talking before about with Maria that the complexity and the recovery. But Gerald I want to stay with you for a minute. So there's other data management technologies popping out there. I mean, I've seen some people saying, okay just leave the data in an S3 bucket. We can query that, then we've got some magic sauce to do that. And so why are you optimistic about you know, traditional database technology going forward? >> I would say because of the history of databases. So one thing that once struck me when I came to Oracle and then got to meet great people like Juan Luis and Andy Mendelsohn who had been here for a long, long time. I come to realization that relational databases are around for about 45 years now. And, you know, I was like, I'm too young to have been around then, right? So I was like, what else was around 45 years? It's like just the tech stack that we have today. It's like, how does this look like? Well, Linux only came out in 93. Well, databases pre-date Linux a lot rather than as I started digging I saw a lot of technologies come and go, right? And you mentioned before like the technologies that data management systems that we had that came and went like the columnar databases or XML databases, object databases. And even before relational databases before Cot gave us the relational model there were apparently these networks stores network databases which to some extent look very similar to adjacent documents. There wasn't a harder storing data and a hierarchy to format. And, you know when you then start actually reading the Cot paper and diving a little bit more into the relation model, that's I think one important crux in there that most of the industry keeps forgetting or it hasn't been around to even know. And that is that when Cot created the relational model, he actually focused not so much on the application putting the data in, but on future users and applications still being able to making sense out of the data, right? And that's kind of like I said before we had those network models, we had XML databases you have adjacent documents stores. And the one thing that they all have along with it is like the application that puts the data in decides the structure of the data. And that's all well and good if you had an application of the developer writing an application. It can become really tricky when 10 years later you still want to look at that data and the application that the developer is no longer around then you go like, what does this all mean? Where is the structure defined? What is this attribute? What does it mean? How does it correlate to others? And the one thing that people tend to forget is that it's actually the data that's here to stay not someone who does the applications where it is. Ideally, every company wants to store every single byte of data that they have because there might be future value in it. Economically may not make sense that's now much more feasible than just years ago. But if you could, why wouldn't you want to store all your data, right? And sometimes you actually have to store the data for seven years or whatever because the laws require you to. And so coming back then and you know, like 10 years from now and looking at the data and going like making sense of that data can actually become a lot more difficult and a lot more challenging than having to first figure out and how we store this data for general use. And that kind of was what the relational model was all about. We decompose the data structures into tables and columns with relationships amongst each other so therefore between each other. So that therefore if somebody wants to, you know typical example would be well you store some purchases from your web store, right? There's a customer attribute in it. There's some credit card payment information in it, just some product information on what the customer bought. Well, in the relational model if you just want to figure out which products were sold on a given day or week, you just would query the payment and products table to get the sense out of it. You don't need to touch the customer and so forth. And with the hierarchical model you have to first sit down and understand how is the structure, what is the customer? Where is the payment? You know, does the document start with the payment or does it start with the customer? Where do I find this information? And then in the very early days those databases even struggled to then not having to scan all the documents to get the data out. So coming back to your question a bit, I apologize for going on here. But you know, it's like relational databases have been around for 45 years. I actually argue it's one of the most successful software technologies that we have out there when you look in the overall industry, right? 45 years is like, in IT terms it's like from a star being the ones who are going supernova. You have said it before that many technologies coming and went, right? And just want to add a more really interesting example by the way is Hadoop and HDFS, right? They kind of gave us this additional promise of like, you know, the 2010s like 2012, 2013 the hype of Hadoop and so forth and (mumbles) and HDFS. And people are just like, just put everything into HDFS and worry about the data later, right? And we can query it and map reduce it and whatever. And we had customers actually coming to us they were like, great we have half a petabyte of data on an HDFS cluster and we have no clue what's stored in there. How do we figure this out? What are we going to do now? Now you had a big data cleansing problem. And so I think that is why databases and also data modeling is something that will not go away anytime soon. And I think databases and database technologies are here for quite a while to stay. Because many of those are people they don't think about what's happening to the data five years from now. And many of the niche players also and also frankly even Amazon you know, following with this single purpose thing is like, just use the right tool for the job for your application, right? Just pull in the data there the way you wanted. And it's like, okay, so you use technologies all over the place and then five years from now you have your data fragmented everywhere in different formats and, you know inconsistencies, and, and, and. And those are usually when you come back to this data-driven business critical business decision applications the worst case scenario you can have, right? Because now you need an army of people to actually do data cleansing. And there's not a coincidence that data science has become very, very popular the last recent years as we kind of went on with this proliferation of different database or data management technologies some of those are not even database. But I think I leave it at that. >> It's an interesting talk track because you're right. I mean, no schema on right was alluring, but it definitely created some problems. It also created an entire, you know you referenced the hyper specialized roles and did the data cleansing component. I mean, maybe technology will eventually solve that problem but it hasn't up at least up tonight. Okay, last question, Maria maybe you could start off and Gerald if you want to chime in as well it'd be great. I mean, it's interesting to watch this industry when Oracle sort of won the top database mantle. I mean, I watched it, I saw it. It was, remember it was Informix and it was (indistinct) too and of course, Microsoft you got to give them credit with SQL server, but Oracle won the database wars. And then everything got kind of quiet for awhile database was sort of boring. And then it exploded, you know, all the, you know not only SQL and the key-value stores and the cloud databases and this is really a hot area now. And when we looked at Oracle we said, okay, Oracle it's all about Oracle Database, but we've seen the kind of resurgence in MySQL which everybody thought, you know once Oracle bought Sun they were going to kill MySQL. But now we see you investing in HeatWave, TimesTen, we talked about In-Memory databases before. So where do those fit in Maria in the grand scheme? How should we think about Oracle's database portfolio? >> So there's lots of places where you'd use those different things. 'Cause just like any other industry there are going to be new and boutique use cases that are going to benefit from a more specialized product or single purpose product. So good examples off the top of my head of the kind of systems that would benefit from that would be things like a stock exchange system or a telephone exchange system. Both of those are latency critical transaction processing applications where they need microsecond response times. And that's going to exceed perhaps what you might normally get or deploy with a converged database. And so Oracle's TimesTen database our In-Memory database is perfect for those kinds of applications. But there's also a host of MySQL applications out there today and you said it yourself there Dave, HeatWave is a great place to provision and deploy those kinds of applications because it's going to run 100 times faster than AWS (mumbles). So, you know, there really is a place in the market and in our customer's systems and the needs they have for all of these different members of our database family here at Oracle. >> Yeah, well, the internet is basically running in the lamp stack so I see MySQL going away. All right Gerald, will give you the final word, bring us home. >> Oh, thank you very much. Yeah, I mean, as Maria said, I think it comes back to what we discussed before. There is obviously still needs for special technologies or different technologies than a relational database or multimodal database. Oracle has actually many more databases that people may first think of. Not only the three that we have already mentioned but there's even SP so the Oracle's NoSQL database. And, you know, on a high level Oracle is a data management company, right? And we want to give our customers the best tools and the best technology to manage all of their data. Rather than therefore there has to be a need or there should be a part of the business that also focuses on this highly specialized systems and this highly specialized technologies that address those use cases. And I think it makes perfect sense. It's like, you know, when the customer comes to Oracle they're not only getting this, take this one product you know, and if you don't like it your problem but actually you have choice, right? And choice allows you to make a decision based on what's best for you and not necessarily best for the vendor you're talking to. >> Well guys, really appreciate your time today and your insights. Maria, Gerald, thanks so much for coming on The Cube. >> Thank you very much for having us. >> And thanks for watching this Cube conversation this is Dave Vellante and we'll see you next time. (upbeat music)

>> Narrator: From around the globe, it's theCUBE.  With digital coverage of IBM Think 2021. Brought to you by IBM. >> 'Kay. Welcome back, everyone to theCUBE's coverage of IBM Think 2021. I'm John Furrier, your host of the theCUBE. We here with a great guest, Maria Winans who's the CMO of the new spin-out, the name, Kyndryl. Maria, great to see you, CUBE alumni, thanks for comin' on theCUBE. Appreciate it. >> Yes, no, thank you. Happy to be here. >> So, I was really excited about this because the new name has been announced of the spin-out, Kyndryl it's the name. It's been some time. What's been the reception? Well, the strategy and the reception. I want to get into this, the brand. But what's been the reception so far of the name Kyndryl? >> Yeah. So, let me, so, let me start by saying that, really, again, excited to be here. This is Think 2021. And excited to kind of tell you a little bit about Kyndryl. Kyndryl, we announced it on April 12th. It was our reveal of the name, been long anticipated. So, I think the response has been positive. It's been long anticipated and it was very well received by the market, and by our own kind of internal employees that are part of Kyndryl. And the reason being that it's very different, it's very new. And it also signals directly where this company is going, and what this company is about. Because the underlining of the word Kyndryl is twofold. One, it's "kin," which is, stands for kinship. So, it's about partnerships, it's about the relationships, it's about the enduring and nurture relationships that we have work with our customers, as well as our employees, and the way that we work. And "dryl" is from tendril. Tendril is about growth. It's about new growth. It's about continuous growth. So, it's the growth that we want to set this company for, but more importantly, the growth around, you know, in conjunction with our customers. So, kinship, tendril, Kyndryl. And at the heart of our company, it's all about the people. And the relationships with our customers. >> Wow. That's awesome. Well, thanks for giving us some insight into the name. I was going to ask that question but you nailed it. So, I like this because the theme here, "Think" this year. And this is an industry theme, but it's really prominent how you guys are executing with the whole IBM red hat and the whole system coming together with hybrid cloud is, the word ecosystem is, has kind of this new meaning and this vibe of working together in a network effect, creating integrations, so it's like up and down the stack, whether it's technical or personal relationships, or business relationships, there's a communal effect here, whether it's API is integrating together. >> Right. >> Or relationships. So, I love the name. What was the process? I'm always curious like, how long does it take? (chuckles) Sure, it's like. >> Yeah! No, no, no, it's a great question, 'cause it's not like, it's not like we hate you like naming anything, right? It's not like naming your dog like somebody says it's, the corporate naming process is very rigorous. It has been a journey for us like any other corporate business that's naming you know, their strategy, their brand strategy. And we worked with, as you can imagine, with our legal teams, with our regulatory teams, we looked at linguistics. We worked with linguistic experts from around the world, over 70 because we're global company. So, it was very important for us, not only to understand how Kyndryl would land in our global markets, but more importantly also, is what it would stand for. And so we did a lot of interviews with our employees, we did interviews with obviously, with our customers and prospects. We looked at trends, we looked at our competitors, we did market research. And what, you know, and within that, we wanted to land on something that really was at the heart of what this company was about. And after all of those kind of legalities that we went to, it was, we were very, very fortunate that at the top of our list, was actually one of our favorites from the beginning. And that was Kyndryl because at the heart of Kyndryl, it really is about our people. And that's what really what we wanted this company to stand for. This is a business, that in a company, that at its foothold, is 90,000 experts in their field that are going to be part of this amazing company. And what we wanted to do is speak to what was that the kind of at the core of the idea behind this brand. What did we want to stand for and what were we going to be. And that it was that we were going to be a brand that stood at the heart of progress. That's our brand idea for not only the businesses that we are part of or with, but at the heart of progress, and at the core was our people and the work that we do. The work that we do for our customers. So, it's super exciting to be able to land on something that really can represent that and also differentiates us from the rest of our competitors in the market. >> So, I love the overview. Just real quick question on the language thing, was there, does it mean the same thing in different languages? >> Yeah, and that's something that now is what we're working on is, how do we land it into all the different markets in the appropriate meaning, again, that stands for relationships and growth. Relationships and growth. And that's the work that we have to do across all of our major markets where we do business. And that's the exciting part, to kind of work with our local teams. Because this company at its foothold, is what the work that we do in the markets that we compete with our people, and with our customers. >> You know, got to ask, you know what, I remember I look at some of the branding exercises that I've been involved in and talk to experts because I'm not a brand expert, but I see a lot of like, there's a lot of work that goes into it. You mentioned a little bit, insight into how that is there. Is there like an architecture for the brand strategy, 'cause you, at a high level, I love what you're bringing in, kind of the purpose of the brand. What's the brand strategy for Kyndryl? You mentioned some of the core principles, first principles. Is there like an architecture where here's the purpose, here's our mission, and here's like the founding principles. Take us through the brand strategy of Kyndryl. >> Yeah. Well, and at the heart, there is a brand idea, right? It is a little bit of what I talked about. The brand idea is that we are at the heart of progress. The people and the work that we do. And so, one of the things that we wanted to do is really look at the art and the science, bring humanity into the way that we were going to activate this brand. And that really is where our brand idea came about which is at the heart of progress. At the heart of progress because our purpose as a brand is that together, and that is at all levels together, each of us, you know, advances the vital systems that power human progress. Together, each of us advance the vital systems that power human progress. That is our purpose as a company. And the idea, the brand idea is that, you know, at a nutshell, we're at the heart of progress for our customers, for each other. And underlining that, it's about the beliefs. We want to really look at how do we instill this healthy digital economy to ensure that we accelerate humanity's progress. You know, and so that's, you know, the whole idea of healthy relationships, purposeful relationships that are about long-term and sustainability with our customers. The openness that we want to encourage in the diverse perspectives across our company. To promote stronger partnerships with our customers and with our strategic partners. And then more importantly, it really had to represent the belief that the right people, the right teams with the right mindset can do anything. And you know, that they want, anything can be accomplished. Again, at the heart where the people. But what was also important in this, is that we worked on our brand strategy and our purpose, our brand ideas, and what were going to be our beliefs around enduring relationships, open partnerships, right skills, right people. But at the same time, there was a culture platform. We wanted to be everything that we have been at IBM, brought the greatness of being part of the IBM company, but more importantly, and what our customers look to us for, but then more importantly, what is it that we want to lean into as we move forward? And what was very important was, how do we activate our experts and really bring the continuum that what our customers expect from us, the expertise, and that we're about with our people, and lean into this, we want to have and activate a culture where our people continue to be these devoted experts that are all about how they're focused and committed to shared success with our customers. We're empathetic and curious about really understanding where our customers are today, and where they want to go tomorrow. We're restless. And that's another word that we want to really activate in our culture was, we're restless. And that means we are continuously improving ourselves, our skills, and focused on the opportunity, and every opportunity with bringing energy and bringing excitement to the work that we do. And then we're anticipating, we're anticipating the what next. Bringing insights and looking at making these kind of connections outside of where our customers may be today, opportunities for tomorrow. And that really is at the heart of our culture platform that we developed in conjunction with our brand strategy in support of continuing to do business with our customers in the way that we have been and what they expect from us coming from IBM, but the platform that we're setting forward. >> That's a great master class gem you dropped there in terms of brand architecture and vision, great culture. I love the progress because it feels like that's what people want. They want to move faster and they want a positive future. And I think this idea of, you know, open, innovation, progress, inclusiveness, inclusion, diversity, community, it's the new way of working. What's, what do you look for in the future as this all comes together? What's most exciting to you? About the future- >> Yeah, what's exciting is that this company is about the service and our people. You know, so as part of any new independent company, at the heart of what we do, is, and really our offering, or the people. And that's why it's super important that here we are a company that is at the heart of progress because of the people and the work that we do. We design, we run, we manage the most modern, you know, efficient, and reliable technology that our customers expect from us. And they run crucial, crucial parts of their organizations, their business. You know, we're the heart and lungs, we're essential to these customers. And that's the opportunity ahead, is how do we continue to build those enduring relationships, and more importantly, what excites me as CMO for this brand is that the heart of what I get to do is really, our brand is our people. And how do we best show up, every single day. And how do we build a culture because building a culture is how you show up for each other, how you show up for your customers, and how you continuously improve and lean on each other in the way that we kind of have set ourselves forward. So, that to me is exciting to really work at the heart of progress because of the people, and then the work that we do for our customers. >> That's super exciting. I love that cultural vibe because what that is, is that's the future. And now, as people are connected, whether they're go back to hybrid office or remote, the working together progress creates bonds of creation. This co-creation, somethin' that we love here at theCUBE, we love working with you guys, co-creating content together. These experiences of the creation together, the solutions for the future really makes a big difference. This is game-changing as a psychology, also people want to be part of that. And that creates these expert, network, it creates the people value, the inclusiveness. If you can thread that needle, it's a magical formula. Don't you agree? >> Right. No, totally agree, it creates belief. And as much as that we like to say, we're super excited about the name, we're super, super excited about the way we're showing up. I don't know if you've seen even the brand creative, very different colors, very different twist on the way that our brand's written in a very warm red. That what's exciting about it is, you know, is the best of companies are not just the brand and the logo. It's really the brand experience. And that is the way that we need to show up with our best of service with the customer, you know, interactions that are best in class. And a culture platform that really you know, provides that experience and shows up as a company that Kyndryl has the opportunity to be and grow to be. >> Maria Winans, CMO, Kyndryl, great to talk to you. What a great career you've having, what a run. You're on a great wave here with a great brand, great brand promise. Love the progress, love the culture, love the name. Congratulations, thanks for coming on theCUBE. >> No, thank you, and thank you for having me here. Appreciate it. >> Okay. This is IBM Think 2021 Cube coverage. I'm John Furrier, your host. Thanks for watching. (techno music) ♪ Da di ya ♪ ♪ Da ♪ ♪ Di ♪ (graphics tinkle)

>>Hi, my name is Maria Winans and I am the CMO for Kendrell. What inspires me is that I get the opportunity to launch a brand new company and into the marketplace. What's been challenging about Covid is not being able to work together with my team in the co creation of the collaborative way that we have been working over the past year and agile. And what excites me about, think is really being able to share our brand strategy at Kendrell with our customers and really showing them the opportunity together ahead of us.

>>from around the globe, >>It's the cube with digital coverage of IBM, think 2021 brought to you by IBM. Okay, welcome back everyone to the cubes coverage of IBM think 2021 john for your host of the QB here with a great guest Maria Winans, who's the CMO of the new spin out, the name Kendrell. Maria. Great to see you cube alumni. Thanks for coming on the Q appreciate it. >>Yes, no, thank you. Happy to be here. >>So I was really excited about this because the new name has been announced of the spin out, Kendra, what's the name? It's been some time, what's been the reception and well the strategy and the reception to get into the brain. But what's been the reception so far? The name Kendrell? >>Yeah, So let me, so let me start by saying that really again, excited to be here, this is think 2021 excited to kind of tell you a little bit about Kendra Kendra, we announced it on april 12, it was how a reveal of the name. Been long anticipated. So I think the, the response has been positive, it's been long anticipated and it was very well received by the market and buy our own kind of internal employees that are part of Kendrell. Um and the reason being that it's very different, it's very new and it also signals directly where this company is going and what this company is about because the underlining of the word Kindle is twofold one, it's kin which stands for kinship, so it's about partnerships, it's about the relationships, it's about the enduring and nurture relationships that we have worked with our customers as well as our employees and the way that we work and drill is from tendril tendrils, is about growth, it's about new growth, it's about continuous growth, so it's the growth that we want to set this company for but more importantly the growth around, you know, in conjunction with our customers. So kinship Kendrell, Kendrell and at the heart of our company it's all about the people and the relationships with our customers. >>That's awesome. Well thanks for giving some insight into the nature is going to ask that question, but you nailed it. So I like this because the theme here think this year and this is an industry theme, but it's really prominent how you guys are executing with the whole IBM red hat and the whole system coming together with hybrid cloud is the word ecosystems has come this new meaning and this vibe of working together in a network effect, creating integrations. So it's like up and down the stack, whether it's technical or personal relationships or business relationships, there's a communal effect here, whether it's a p is integrating together or relationships. So I love the name. What was the process? I'm always curious like how long does it take? Sure. It's like >>yeah, you know, it's a great question because it's not like it's not like we like naming anything right, It's not like naming your dog, like somebody says it's the corporate naming process is very rigorous. Um It has been a journey for us, like any other corporate business that's naming, you know, their strategy, their brand strategy. And um we worked with, as you can imagine with our legal teams, with our regulatory teams. We looked at uh linguistics, we work with linguistic experts from around the world over 70 because we're a global company. So it was very important for us not only to understand how Kendra would land in our global markets, but more importantly also is what it would stand for. And so we did a lot of interviews with our employees, we did interviews with, obviously with our customers and prospects. We looked at trends, we looked at our competitors, we did market research and you know, and within that we wanted to land on something that really was at the heart of what this company was about. Um, and after all of those uh, kind of legalities that we went to, it was, we were very, very fortunate that at the top of our list was actually one of our favorites from the beginning. Um and that was kinda cool because at the heart of Kendrell, it really is about our people. Um, and that's really what we wanted. This company is stand for, this is a business that in a company that his foothold is 90,000 experts in their field, they're going to be part of this amazing company. And what we wanted to do is speak to what was at the kind of at the core of the idea behind this brand, what did we want to stay again for and what we're going to be, and that it was that we were going to be a brand that stood at the heart of progress, um that's our brand idea for not only the businesses that we are part of or with, but at the heart of progress, and at the core was our people and the work that we do, the work that we do for our customers. So it's super exciting to be able to land on something that really can represent that, and also differentiates us from the rest of our competitors in the market. >>So I love the overview. Just real quick question on the language thing was that doesn't mean the same thing in different languages. >>Yeah. And that's something that now is what we're, what we're working on is how do we landed into all the different markets in the appropriate meeting again, That stands for relationships and growth, relationships and growth, and that's the work that we have to do across all of our major markets where we do business. And that's the exciting part to kind of work with our local teams because this company at the end it's foot hole, is what the work that we do in the markets that we compete with our people and with our customers, >>got to ask, you know what, remember I look at some of the branding exercises I've been involved in and talk to experts because I'm not a brand expert, but I see a lot of like there's a lot of work that goes into it. You mentioned a little bit of insight into how that is there. Is there like an architecture for the brand strategy? Because you have a high level I love you bring it into the purpose of the brand. What's the brand strategy for Kendrell? You mentioned some of the core principles. First principles. Is there like an architecture where here's the purpose, here's our mission and here's like the founding principles, take us through the brand strategy >>at the at the heart. There is a brand idea, right? It's a little bit of what I talked about. The brand idea is that we are at the heart of progress, the people and the work that we do. And so one of the things that we wanted to do is really look at the art and the science bring humanity into the way that we were going to activate this brand And that really is where our brand idea came about. Which is at the heart of progress, at the heart of progress, because our purpose as a brand is that together and that is at all levels together. Each of us, you know, advances the vital systems that power human progress together. Each of us advance the vital systems of power human progress, that is our purpose as a company. And the idea of the brand idea is that that, you know, at a nutshell, were at the heart of progress for our customers for each other. And underlining that is about the beliefs we want to really look at, how do we instill this healthy digital economy, um to ensure that we accelerate humanity's progress. And so that's, you know, the whole idea of healthy relationships, purposeful relationships that are about long term and sustainability with our customers, the openness that we want to encourage in the diverse perspectives across our company to promote stronger partnerships with our customers and with our strategic partners. And then more importantly, it really had to represent the belief that the right people, the right teams with the right mindset can do anything, you know, that they want, anything can be accomplished again at the horror were heart where the people. But what was also important in this is that we worked on our brand strategy and our purpose, our brand ideas and what we're going to be our believes around enduring relationships, open partnerships, right skills, right people. But at the same time there was a culture of platform. We wanted to be everything that we have been at. IBM brought the greatness of being part of the IBM company, but more importantly, what our customers look to us for. But then more importantly, what is it that we want to lean into as we move forward and what was very important was how do we activate our experts and really bring the continuum that what our customers expect from us, the expertise and that that we're about with our people and lean into this. We want to have and activate a culture. Where are people continue to be these devoted experts that are all about how they're focused and committed to shared success with? Our customers were empathetic, were and curious about really understanding where our customers are today and where they want to go tomorrow. We're restless and that's another word that we want to really activate in our culture, which were restless. That means we are continuously improving ourselves our skills and focused on the opportunity and every opportunity with bringing energy and bringing excitement to the work that we do. And then we're anticipating we're anticipating the what next? Bringing insights and looking at making these kind of connections outside of where our customers maybe today opportunities for tomorrow. And that really is at the heart of our cultural platform that we developed in conjunction with our brand strategy in support of continuing to do business with our customers in the way that we have and what they expect from us. Um coming from IBM. But the platform that we're sitting forward, >>that's a great uh masterclass gem you dropped there in terms of brand architecture, envision great culture. I love the progress because it feels like that's what people want. They want to move faster and they want a positive future. And I think this idea of, you know, open innovation, progress, inclusive nests inclusion, diversity community. It's the new way of working what what do you look for in the future as this all comes together? What's most exciting to you about? >>What's exciting is that this company is about the service and our people. So as part of any new independent company at the heart of what we do is and I really are off line are the people. And and that's why it's super important that here we are, a company that is at the heart of progress because of the people and the work that we do. We design. We run, we manage the most modern, efficient and reliable technology that our customers expect from us. And they run crucial, crucial parts of their organizations, their business. You know, where the heart and lungs were essential to these customers. And that's the opportunity ahead is how do we continue to build those enduring relationships And and more importantly, what excites me as CMO or this brand is at the heart of what I get to do is really our brand is our people. And how do we best show up every single day? And how do we build a culture? Because building a culture is how you show up for each other, how you show up for your customers. And how do you continuously improve and and lean on each other in the way that we kind of have set ourselves forward. So that to me is exciting to really work at the heart of progress because of the people and then the work that we do for our customers. >>That's super exciting. I love that cultural vibe because what that is is that's the future and now as people are connected, whether they go back to hybrid office or remote, the working together progress creates bonds of creation, this co creation. Something that we love here at the Q. We love working with you guys co creating content together. These experiences of the creation together the solutions for the future really makes a big difference. This is this is game changing it as a psychology and also people want to be part of that and that creates these expert network. It creates the people value the inclusiveness. If you can thread that needle, it's a magical formulas. Don't you agree? >>No, totally agree and it creates belief. Um and as much as I would like to say, we're super excited about the name, were super super excited about the way we're showing up. I don't know if you've seen even the brand creative, you're very different colours, very different twist on the way that our our brands written in a very warm red. That's what's exciting about it is, you know, is the best of companies are not just the brand in the logo is really the brand experience. Um, and that is the way that we need to show up with our best of service with the customer interactions that are best in class and culture platform that really, you know, provides that experience and shows up as a company that Kendrell has the opportunity to be in, growed to be >>Maria wine and CMO Kendrell, great to talk to you. What a great career you've having would have run. You had a great wave here with a great brand, great brand promise, love the progress, love the culture, love the name. Congratulations. Thanks for coming on the cube. >>No, thank you and thank you for having me here, appreciate it. >>Okay, this is IBM think 2021 Cube coverage. I'm John Kerry, your host. Thanks for watching.

>> Announcer: From theCUBE studios in Palo Alto and Boston, it's theCUBE covering IBM Think, brought to you by IBM. >> Hey, welcome back everybody to theCUBE's continuing coverage of IBM Think 2020, I'm Jeff Frick. We're in our studios in Palo Alto, and this year, IBM Think is digital, so unfortunately we're not all together at Moscone or the Stands or one of your favorite convention sites. We're bringing to you this all from people's homes, and we're excited to have our very next guest. She is Maria Winans, the CMO of North America for IBM. Maria, great to see you. >> Yeah, great to see you, thank you for having me. >> Absolutely, so let's jump into it. IBM Think 2020, the digital experience. You know, we've been going to so many IBM events for so many years, and you used to have them, you would inherit them when you brought in new companies, so there was many, many IBM events, there's a long history of IBM events. It's a really important part of your mix, but then suddenly, in mid-March, you wake up one day, and are told, "Guess what? "You can't do IBM Think in a physical event anymore." So give us a little background on what IBM thinks of events, and how important they are what you use them for, and then a little of the behind the scenes, what happened in mid-March when suddenly this thing had to go digital? >> Yeah, thank you for having me here again. theCUBE has been an integral part of many of our events, from our conferences way back when. So let me start by saying that events are at the core of our marketing strategy for driving value, for driving probe. I mean, they really are about helping us build the brand, events help us foster and nurture relationships for you and existing clients, they help us really establish that leadership. They help shape business and society, and it's a great opportunity for us to showcase our best of features, our new announcements, our product, our functionality through amazing demonstrations and labs, and more importantly, it's a great opportunity for our sellers to progress conversations and to close business. And we do all kinds of variety of events, from breakfasts to what we called roadshows, on the road, impression events, and our premier flagship event, which is Think 2020, it's the one time of year where IBM comes together, and it's a great opportunity to really showcase one idea. And that's what the Think 2020 is about. >> That's awesome. So when you guys, again, woke up mid-March, we got to change this thing, good for IBM to actually hold the date. Most of the people that we work with, which are numerous, either flat out canceled the date, postponed it to some future date where maybe things are a little bit more back to normal, or went with the digital, but even with the digital, they postponed. So as you think about what digital means, what a digital event kind of affords you, I think there's way too much conversation about what digital isn't, vis-a-vis the physical, it just isn't, it's not the same as being together. And yet on the other hand, there's a whole lot of new things you can do on digital, that you just can't do with a physical conference, so how did you guys search those things out, define what a digital event is, and then really get in a position to deliver on that promise? >> Yeah, so let me talk about that in a couple of forms. First of all, we know that our attendees perceive value our event if this really heavily depended on the in-person interactions. So as you think about that, we've had to step back and say, how do we reimagine how we deliver this meaningful, one-to-one engagement that our clients know that in a value, to really now through a digital environment, and really reimagine that whole interaction, while still maintaining that very personalized, best in class experience that our clients value, and that's what really excites me about Think 2020. First of all, we are, so let me just highlight a couple of things of why I think, and I personally am excited about Think 2020. First of all, we have broadened our reach. We are hosting over 50,000 attendees. That's clients, partners, IBMers, influencers, and we reaping a much broader set of roles and influencers who may have not had the ability to travel before to attend an in-person event. Second, complimentary. This will be our first event that of this size, that is free. So we have many more new accounts joining us to learn about IBM for the first time. And this really opens up the doors to new business and opportunities for us. Very targeted agenda. So what we've done is we've taken an event that was going to span over five days to now two days, and we went from over 2,000 sessions that we were going to run to really now, think about how do we feature 200 sessions that are very focused, that are very targeted and very much on point in messaging of really dealing with what our clients are experiencing today with the recent world crisis. Another very exciting thing is lots in media platform. We are leveraging our very own media and AI platform that can host over a million users at once, and really increases the opportunity for engagement. So very interactive experience, you know our labs are sold out. We are completely sold out of our labs, some of our sessions are wait listed, and we're also running the opportunity to do one-on-one meetings for these two days. So while we're not in person, we have a tremendous opportunity to really offer a very interactive experience by introducing live chat throughout the sessions, and really engaging clients with each other and with their sellers during the event. And then for those that cannot attend, or cannot attend all the sessions throughout the day, we are going to have what basically we're calling content on demand. The content will live on, it will live on in different platforms, and we will be delivering the content to our clients, making it accessible at any time whenever it's convenient for them. So super excited about what the teams have done to really step back and reimagine this whole experience maintaining the interactivity, the personal engagement, and really the value add that our clients look for. >> Right, you touched on so many good themes there, and I just want to unpack them a little bit more. The first one that you talked about right off the bat was democratization. And as you said, there are many people that just can't get up and go to a conference, whether it's just bad timing for the week, they've got to run their own business, they just can't get away. So for people to be able to attend digitally, as you said, opens up an entire new pallet of participation for people that maybe couldn't come before. Another thing I think that's lost is this kind of separation of content creation, content delivery, and content consumption which is consistent with how we consume a lot of things today in our media, and very few people sit down, even for big television events, it's like the Super Bowl has really appointment television, we're creating this content now, right, it's going to be going up in the middle of IBM Think, and people might watch it on May 5th, or May 6th, they might watch it on May 10th, they might watch it May 10th 2025. So I think it's a really different way to think about it, and I'm sure as a marketer, at some point you're going to feel a little bit more freedom rather than try to force fit all the product groups and all the announcements and all the sessions, all this stuff that's got to line up for these, well it was three days in Vegas or San Francisco, now can kind of be broken up, and if it makes more sense for some information to get out earlier, it can go out earlier, it can go out later, but you know, a conference is defined by the bounds of that physical location for three days and how much can you guys get in there, where now suddenly, you don't have those binds anymore, and it really opens up a much broader opportunity for you to communicate your messages, keynote messages, product information, training in a very, very different and in some ways, I would bet liberating way. >> Yeah, I think this, what's happening here is an opportunity to really rethink in so many ways how we do marketing and what we talk about when we say digital engagement. You know, we did a recent CMO survey, which we call our C-Suite Survey, and we interviewed over 2000 CMOs, and one of the big conclusions that came out of it was that digital engagement is the future, and the way that really, what it really lands on is the fact that really digital engagement is the fair trade off of information and the exchange of value. So when you really think about that, for us, as marketers, digital engagement and value exchange comes in many forms. How we show up on our own platform, like we're doing here with Watson Media, how we show up during an event, whether it's Webinars or third parties. Even more importantly, the way that our sellers are going to engage virtually. Think about virtual sullying and Webex meetings which is really how they're having to communicate with clients today, and then how we engage socially, and that's really through all the social channels in the work that we do with the influencers. So we're going to learn a lot, we are learning a lot, we're going to test, we're going to iterate, but this whole new normal has given us an opportunity as marketers to really connect the digital and the physical in new ways. And in that, we have to really consider all the multiple facets and elements when we're thinking about digital marketing, and that to me is a tremendous opportunity because digital engagement, there are many elements, and it's going to be super important for all the marketers to really kind of step back and think about, what are those multiple elements that are going to make us, as we think about, how do we stay essential? How do we stay essential with our clients? And that is providing information when they need it, how they want to consume it, and then how do we stay relevant? I think also, when you think about digital engagement, is you got to show flexibility. The ability to pivot strategically and quickly, which is really what we've done with Think. We were ready to move forward on a physical event, amazing event the teams have been working on, and with everything going on, we wanted to maintain May 5th and 6th, we had made a commitment to our clients, and we had to pivot very quickly and be flexible of how do we reimagine Think from physical to now digital. In a digital world, user first experience is a must. It has to be compelling. It has to be an incredible user experience, and the entire experience has to be digitally connected. You know, content, as you said before, content needs to be delivered in unique ways, and where the clients are, not where you want the clients to come, so how does the content find the clients? The relationships. How do we continue to incorporate the human connection? The human connection and build those relationships with the clients, and interacting with them in meaningful ways. And I think one of the things that we've really, over the last couple of years in IBM is grounded in leverage really our data and analytics to better understand behaviors and determine what is that best digital investment, that best touch point at that best time. Very targeted. >> Frick: If it. >> Yeah. >> I'm sorry. >> No go ahead. >> I was going to say, it's just, is it a hook or crook or circumstance, but just kind of an ironic, right, that when you guys were forced to make this pivot, and I think it's a nice statement to IBM that you were able to successfully make this pivot, again, one of the interesting things about COVID is nobody saw it coming, nobody really had time to prep, nobody put in plans, there was no slow transition, it was this light switch moment. But at the same moment in time, you just got a brand new CEO who is extremely social, and Arvind announced his kind of welcome to the world and his leadership changes and some promotions and stuff via a LinkedIn post, which I found really fascinating that he's leveraging the social medium in a way that wasn't necessarily done before at IBM in the leadership suite, and then the fact that you guys are making this quick switch, you took the challenge to keep that date the same, but reinvent Think, again, is a testament to kind of a shift in IBM's culture and ability to move quickly in the face of this new challenge which nobody really saw coming to the degree and speed in which we've had to react, so it's a very, it's a very nice statement on your guys ability to execute. >> Yeah, and it's exciting, I mean I think, when I think about marketing and I've been in marketing most of my career at IBM, it's an opportunity for us to really kind of lean in and put our creative juices to work, really team together and embrace, embrace the opportunity to kind of think differently, and I think when we look at how marketing will progress, and the leadership that we can provide in this digital era, we're going to see a lot more opportunity to get much more personalized, we're going to see ChatBot being used very strategically, as we're seeing them today. We're going to look at opportunities to infuse AI in the experience to augment it, to personalize it, dynamic content delivery. We're experimenting with many platforms to really do that more effectively and recommendation engines and really continue to automate the marketing process and marketing experience all the way through to make it as compelling and as personalized as we can. So a huge opportunity for every marketer in the world, and a huge opportunity that we've embraced in IBM. >> It's just, wow, just the forcing function, just automation, we've been talking about that for a long time, taking away boring tasks so people can focus on higher level activities. But it all kinds of come back to something I want to kind of close on, and that's leadership. And Michelle Peluso had a post a couple of days ago talking about leadership. You responded to it, and we've been reaching out to a lot of the leaders in our community to get their take on, from a leadership perspective, 'cause I think the cream really rises to the top in challenging times, and this is, again, cast upon us, no preparation, ready, set, go. And it is really a call to leadership, it's leading your own people, it's really putting a voice of confidence out to your customer base, as well as just your broader community, so that's partners and all of the constituents that play. So I wonder, we've been in it for a number of weeks now, as you kind of think back on adjusting your own leadership style, as down as well as the leadership within the IBM senior team, great example, being able to pull this Think together and completely flip it on its head, if you will. Wonder if you can share what are you trying to do different, what are some best practices, who are some of the folks you're looking to to give you kind of some tips and tricks to lead in basically from your home office? >> I think challenging times like this, and I've always said it, it is with the opportunity for every leader to step up and rise to the top. Leaders are made during challenging times, leaders become during these, turning challenges into opportunities. So for me, you know as I think about my own leadership style, number one, is you put the people first. Especially during these times, act with compassion and empathy. Focus on the team's help, focus on wellness, focus on making sure that you keep everybody motivated. Lead with energy. And this is back to Michelle's article in LinkedIn, she talked about team matters an awful lot now, and connecting people and making sure that everybody's well being, it's their mind, their wellness, their activity, and they're staying connected. I think the second is productivity, is we have to keep the business going, we have to make sure that the work from home environment is safe and productive and everybody's work environment differently. Everybody has their own challenges and opportunities, and we have to acknowledge that. So productivity is important, but everybody is in their own, and you've got to be aware as a leader of those circumstances. You can't expect everything to be the same for everyone, and you've got to be ready for interruptions. You got to be ready for those kids in the background and dogs barking and certain routines that have to be adjusted to. And I think the third is around staying connected. We have various tools, and we're very fortunate in IBM, and especially in marketing, that we've really embraced the new as far as the way that we communicate using Slack, looking at how do we leverage up our tools to inform our actions in marketing, and staying connected is more important than ever. And we're doing, we're touching teammates more often, I know that I am doing one-on-one calls with my team more often than I would have done otherwise. And then being agile. Whether it's the tools, the process, the culture, for us, embracing agile has been at the core of our marketing transformation, and it's more important than ever that we stay agile, that we continue to work in feedback, in learning, in testing, and in the ways that we know best. And it's an amazing opportunity to try new things. There is no bad idea, be open to innovation, try fast, learn, ready to pivot, you know, and really what's happening in the world has given us an opportunity to really step out of our normal and some amazing ideas are coming forward and at a very fast pace, and we have to be agile and we have to be authentic to our environment. And I'll close with one thing. One of the things that we did as IBMers is we all specifically as leaders, from Arvind to Michelle to every leader at IBM, we've made a pledge. A work from home pledge, that we will support each other, and we are each given examples of the things that we are taking forward to support each other as we're living through this new normal and digital engagement. So, an incredible opportunity for every IBMer and really a prideful moment to stay strong as an IBMer, to stay strong as an individual and a leader. >> Well very good, well it shows that you've been able to accomplish this feat in pull off this really big event in the same time window that you had allocated, and completely flipped it on its mind, so it's a great testament to you, as well as the leadership team and everybody executing up and down the line. So Maria, great to catch up, thanks for your time, and really a pleasure. >> Thank you, thank you. >> All right, she's Maria, I'm Jeff, it's theCUBE's continuing coverage of IBM Think 2020, the digital experience. Thanks for watching, we'll see you next time. (inspirational digital music)

>> Announcer: From around the globe, it's theCUBE, with digital coverage of Red Hat Summit 2020, brought to you by Red Hat. >> Welcome back to theCUBE's coverage of Red Hat Summit 2020. I'm Stu Minneman and, of course, this year, the event is really happening globally where people are. So, we're talking to Red Hat executives, their partners, and we're always thrilled when we get to talk to the customer. So, joining me, from Buenos Aires, Argentina, I have Maria Alehandro-Trosee, who is the Deputy Manager of Solutions Architecture at Edenor. Alejandra, thank you so much for joining us. >> Oh, thanks to you, of course. I am pleased to be here. >> All right, so we know we are living in some challenging times right now. Certain things become very important. Everybody is working at home. Of course, Edenor is energy. So, talk about something that is essential. You look at Maslow's hierarchy, want to make sure everyone is healthy and, pretty soon after that, your company is making sure that things get running. So why don't we start with a little bit, Edenor. Tell us a little bit about the company, and your role in the organization. >> Yeah, of course, of course. Well, Edenor is the largest electricity company of Argentina with almost 5000 employees and three million customers, in parts of Buenos Aires city and surroundings, too. It represents a 9-million population. And we have the residential, commercial and industrial customers. So, we bring electricity to homes, to schools, to hospitals, to airport. And well, of course, commercial and industrial customers that are in our concession area. >> Excellent. Great, and solutions architecture. So tell us a little bit about your role there, or purview of your group. >> Well, I am part of the information systems, of the technology information direction in Edenor. And, as the solution architecture area, we are helping to establish good architectures for business objectives. For the business to meet the objectives in a very, or in the best quality, and in the best way. We are seeing how the trends, how technology moves, how industries, similar industries and companies are moving, beyond technology and architectures, and we try to go this way for the company. >> Great. So, just so I understand. So is that this infrastructure piece? Is cloud part of the mix? Where is your connection to, really, the business applications? Any developers, you know? >> Yes. I usually think about it as the glue. As the glue that join our pieces together. Applications, infrastructure, and the business that makes a solution. It involves software, but it depends on power, it depends on infrastructure, security and so on. There is an infrastructure area, a security area, a solutions area. In I.T. too. Now our I.T., too. And architecture is one of them, and we try to glue all these pieces to meet requirement. >> Yeah. I love you give that analogy of the glue, bringing things together. >> (laughs) Yeah. >> We know there, you know, the pace of technology continues to change so fast. The requirements of the business don't stand still. So, bring us inside. Help us to understand some of the integration challenges you're facing. What drivers of the business are causing you to evaluate what you're doing. And tell us a little bit about what you're using, today. >> Yeah. Well, we have had a lot of challenges. Some time ago, we had lots of integrations running. And I think that I usually see, see these challenges in several ways. The integrations that we are running, and we are having trouble. We are having a a lot of issues. Maybe issues in data, in quality, and in performance or viability, too. And, most of these issues were because of online transactions that, maybe started to grow, much more, and started to add some complexity to the system platform that was almost for batch processing. So we have a huge amount of LAN integrations, that started to be big, to be big in volume, to be critical for the business. Any maybe we don't have, we didn't have the right picture. We had to do it, a lot of hand craft job, with a lot of work force behind. A lot of micro-batches and so on, to keep things running. But with a lot of effort behind that. >> Yeah. >> Yeah, tell me. >> Yeah. Just, you know, very typical challenges that I am hearing from you. Help us understand, you know. How do you choose the technology partners that you're working with? You know, it is the paradox of choice out there. There are so many companies, so many products. You know, especially you company. You've got the DevOps pieces. I look at the DevOps tool chain today, and it is more than any one person can comprehend. So, how does Edenor approach, you know, who you integrate with? And choose the various pieces? >> Okay. Well, the center of the evaluation, or the decision, was integration. Of course, the center of the evaluation process, and the research, was about integration. But we wanted an integration platform or to be, as an architecture, an integration architecture that could solve all of the issues that I mentioned before. All of the issues that we had. But that could take Edenor to a next stage. That prepare us for what, in that time, we could see as the future of departments. And nowadays, they are almost, actual departments. But, at that time, two years ago, we are some kind of future requirements, like DevOps, micro services, APIs, and the cloud. Well, the cloud requirement was one of the first that we managed at IT. The new concept, for Edenor. And we had to manage all of that. Some platform that prepare us for all that were coming, and for cloud or high-width architecture. So, we started our research, and we found, in Red Hat, an excellent technology. But this is a technical aspect, and the other aspects that we looked for, were the experience in the region. You know, maybe there are a lot of technologies that could be great, but maybe unrepresented in our region. It's not just a case of integration, because integration platforms, the biggest, or the best integration platforms, I think they are mostly clear. But, with many technologies, it could happen that, maybe there are good technologies, but not with some presence in our local region. Adding that, I would say that experience in similar industries, and a presence and, most important for us, I mean, was, pretty well, it works really well. A supportive way of working. That the company could support us. Support all along the project. Not just the possible additional support, but also, support for all the journey. All the learning process, all the implementation process. We could find all of these in Red Hat. Of course, that's why we chose it. >> Absolutely. So, Alejandra. Tell me, where are you with the roll out of what you are using with Red Hat? What have you put into it? Give us where you are so far. >> Well, we started with an initial phase, a pilot phase, where we chose some initial services that were not so complicated, not so complex, not so critical. But, with a good sample of what we have, in terms of protocol, in terms of patterns, in terms of connectors with other systems. So we started with a kind of sample of all of that. And not, making some changes, making changes in the way of working. It's something like, well okay, let's go and try the technology. Let's put some first services, and let's learn. One of the services was not-so-complicated, but just had a lot of volume, a lot of transactions. We have almost 800,000 events per day, with that service, and was maybe the one of the most important, of that initial phase, in terms of scalability. And we could test it and see the bright of the technology, with that pilot. >> Excellent. And so what's been the result inside the organization? Has that impacted development time? Is it something that your ultimate end customers would have any positive results, after you've rolled this out? >> Well yes. After we started, or we finished the initial pilot phase, we started another phase, that consisted in a review, all the integrations, flows. And we knew which ones were the most critical, for the business, and have a lot of issues in the architecture, so we agreed with the rest of the team, solutions teams and business teams, just where to start to making real changes. So, another initiative started, that consisted in implementing a trial methodologies, in trying this on framework, for example. And we thought that it was a great combination, to try new ways of working, in this new phase of integration, with re-engineering. So, these new services, that we arrived. We are about, we are between the outage management system, the system that manages all of the technical reframe, of the electricity service, and the field management system. That is the system that manages all the work force industry, the logistics, or distributes the work, or in terms of priority. So all these flow, all of these flows are, increanals, are online flows. We have to send data, in simultaneously, just to change or to renew those priorities, all the time. To make a new schedule, and repair things better and faster. So, the business. I could say that the business and I, and our team, put a lot of increases in agility and speed. We could solve issues faster. For example, I learned about outages that could flow in terms of seconds, rather than in minutes. And, the development processes that fix. We could fix problems in production, maybe in a day, when sometimes we took weeks. So, we could find things like that, but with a new way of working, too. That could take all of the technology could being to us. >> Excellent. Well, when you talk about integration platform, traditionally middle ware, sits right in the middle between the infrastructure side of the house, and all of the app, you know, development pieces that you have. So, I am just curious. As you have rolled out the solution with Red Hat. Have there been any cultural change? You know, one of the things we have been looking at is, You know. Can tooling help bring teams together? You know. How much retraining do you need to do? How much fear and uncertainty is there, from groups? So, from an organizational standpoint. How has this gone inside of Edenor? >> Well. We have had a few huge changes. And I can mention some of them, or the most important. One of them was that we have to reorganize. Many teams have to reorganize their activities. Maybe it is not structural, or organizational chart situation, but functional. The way that the teams, maybe, organized their activity. We started to build a team where we have a project owner, a scrum master, Devs and architects from different providers, all on teams. And different specialties all working together, in the same space, with kind of dedication. I couldn't get full dedication. But yes, with a great dedication, that could give that team the autonomy, and the communication, and the collaborative space that we needed. So the teams, and managers of those teams, had to reorganize their activities. And it was possible, thanks to that. Thanks to them. But, the other aspect was that we have to learn, learn technology and learn new ways of working at the same time. And it's not just to have a training. This is an important aspect, but besides that, we have to incorporate all of these new concepts. This is a difficult, or the most difficult part, because we could do training and take courses. But we really, incorporate those new ways of working. It's really difficult. And we were, with you in the process, the team, helping the team. Just to, not to make a hybrid or something that is not the genuine. Because we wanted the genuine change, in the way of working, just to see better results. Then you, maybe we could get more flexibility, with time, with some level of maturity. But, in the first time. We saw, and our experts tell us, that it's better to attach to the pure sense of the way of working. A new way of working. So we have to incorporate all of that, to make a genuine change. >> Great. Well Alejandra. My final question, actually. I want to talk a little bit about community. So, you've been to Red Hat Summit before. Many of the things that you were talking about, and the change that you are going through. Many of the companies that I talk to. Of course, you know, the vendors are going to help you. Red Hat. They're partners. If you have a channel partner, they will help you. But often times, it is the peers in the community that are an important piece of this. That you can learn from others. You contribute back what you're learning. So, the question for you is. You know, this week, we're coming together while being apart at Red Hat Summit. So tell us how you engage with the community? The importance of Red Hat's ecosystem, and your peers in the community, around using these sorts of solutions? >> Well, I always said Red Hat people, Red Hat group that are near me, here in Argentina, and now with the U.S. guys, that I am really thankful of all of the Red Hat community. Because they've made real great things. It's really amazing to see the great technology that they could build as a community, as a whole community, in all the world. All around the world, people contributing, and coding technology. This is the biggest collaborative experience, I think, that we could see, and we could learn of. A very high collaboration, remote and very spread around the world. Really, a great inspiration for all of that, all of this, all of us. >> All right. Well Alejandra. Thank you so much for sharing your story, and all of the update with Edenor. And wish you the best of luck with the rest of the roll out of the projects you are working on. >> Oh, thanks to you for giving me this opportunity. It's a pleasure to talk to you. >> All right. Lot's more coverage from Red Hat Summit. I'm Stu Minnamen. And, as always, thank you for watching theCUBE. (gently chiming music)

live from Las Vegas it's the cube covering AWS reinvents 2018 brought to you by Amazon Web Services Intel and their ecosystem partners okay welcome back everyone live here at Amazon Web Services reinvent 2018 floor to cubes here wall-to-wall coverage - second day of three days I'm John for a table on that Dave six years and we got Maria d'marie here vice president general manager Lockheed Martin space news yesterday was the announcement of a new satellite ground station you guys are partnering with AWS this is an outside-the-box pioneering like move for amazon covered it yesterday on our blog we were giving commentary this is gonna power the iot edge and so essentially it kills the notion of an edge because if there's connectivity everywhere there is no edge the world is round and it's good space that's exactly right that's what you're doing is truly disruptive my team in lockheed martin we provide ground for satellite systems and it's generally usually a physical place that exists where you know where it is there's a large parabolic antenna this completely disrupts that whole concept it becomes a network node of antennas low-cost antennas for our customers and it's truly disruptive exactly to your point let's talk about how it works you have this thing called verge right what you're doing for the cube stats you did for orbit not related to our cube different cube different cubes overages part talk about how it works at amazon explain the system what was what's gonna how it's gonna work okay wasn't sure so amazon with we together had this collaboration which we rolled out yesterday andrew jesse from amazon AWS rolled out AWS brown station which is 12 parabolic antennas it'll be at amazon locations at there they're global regions thank you and so that allows for download of downlink of satellite data to those our system is complementary to that and separate in its low cost antennas across other areas which allows for more frequent connectivity for the satellites more frequent opportunities to downlink data and all of this is available to customers as a service so you were only paying for it when you're using it yeah it's really key when you think about the cost of entry to have access to space it's very expensive if you have to build these large parabolics this allows startups it makes provisioning a jada Center look like a picnic satellites how did it come about where'd the idea come from how would that collaboration start I'm glad you asked so we had Andrew Jesse and our executive vice president Rick Ambrose you know know each other and they had a conversation one day and they said we should do something together and we actually Teresa Carlson and I work for both of them got together got our teams together out in Denver Colorado for a two-day shark tank type activity and we just brought some of our best and brightest from both teams across all of Amazon not even just AWS but other activities and Amazon young people that just graduated from college some of our senior fellows everybody and we just put them in a room and said what are some things that what do we have that we're working on that we might be able to bring three big things the reinvent exactly I like to think it's like we call it peanut butter and chocolate because they're great separately but when you bring them together they're even better and these systems are really complementary to each other and it's just it's been really neat and the teams have had a lot of fun learning from each other it's certainly chink his connectivity to places that don't have connectivity so edge computing had a limitation between power and connectivity power you get battery low cut low you know low battery power batteries they last a long time too now satellite coverage so there's no excuse to trip the first back all the data so backhaul is huge here great huge advantage right so factory in remote areas as you guys did the announcement yesterday were there developers involved how do you see developers playing with this so let's just say I'm into space and I want to visit some satellites what do I do it so I go to the console and say you know move the satellite like a video game and like start mostly what you do is make sure that you can down link whatever type of data you work with can get to you the point of both these systems it gets data into the cloud and that's where the real magic happens because when you can get that downlink down and start using artificial intelligence machine learning the services that are available on that data now you can take action which is really what our customers missions are about it's not necessarily about the satellites or down-looking data from satellites it's about getting data that you can add and turning into the insights family so talk about space history that you guys have had and big legacy with Lockheed Martin I was seeing you know Theresa Carlson and I love to talk about space force that was announced and just the notion of having a space force it's kind of people love you know seeing you know Blue Origin and SpaceX Rockets landing back on the pads so huge interest in the culture back to space there is I have two kids I'm sorry three kids at home too that are actually interested in space I should say but yeah my kids talk about it you know we just had the Mars Lander the insight Lander Monday and we were at dinner Monday night and my kids are like mom that you know yeah we landed something on Mars like that was us yeah so it's it's really an exciting time do we have hardest space a lot of it's because so much technology has advanced recently to the point where we can do a lot more things than we've been able to do and the cost keep coming down coming down so you know NIT I we can easily envision the the heavy lifting and the before and the after can you describe what a customer's going to go through now and how it's different yes if you were gonna build a parabolic antenna it might cost a million dollars you have to have land you might need to have a fence line you have to maintain it operate it this is available as a service so you could imagine if this exists for our customers that might want to you know maybe there's a fire situation and someone needs rapid access to get imagery down to see where something's happen as a service they can connect we can get them on quickly and have their owns all kinds of other moving vehicles mobility kind of feature well I mean mostly right now we're dealing with satellites but that's a good idea that will take back I was like drone deliveries by John to your next meeting talking about video car the whole thing okay so where's this go next how do you envision it evolving after the parts of the Amazon solid connected to the cloud analytics are in the cloud a lot of horsepower absolutely you know we just went to Mars there's a lot of things they're going to be happening in deep space there's a lot of excitement about what's going on and Mars in the moon etc so I will tell you there were more ideas that came out of the shark tank I think that you know this is the start I think of a really great longer-term relationship I hope and that you know we do have some other ideas that we can't really necessarily everyone knows Jeff Bezos loves space yes joke we always say is maybe they put the data centers in space in Mars be a lot cooler Maria thanks for coming on explaining the relationship as Amazon announcement love it I think it's a super groundbreaking pioneering different but it shows where it's going great it's powering a lot of things just the beginning day one actly congratulation thank you okay live cube coverage here day two wrapping up I'm John Faraday Volante thanks for watching we'll see you tomorrow [Music]

(upbeat techno music) >> Live from Bahrain, it's theCUBE. Covering AWS Summit Bahrain. Brought to you by Amazon Web Services. >> Okay welcome back everyone, we are here in Bahrain for exclusive coverage for AWS Summit, part of Amazon's new region being launched here in the Middle East. I'm John Furrier, your host, we have two great guests from C5 Accelerator in Washington D.C., now kicking it out in Bahrain. Hadyah Fathalla, executive director C5 Accelerate and Eva Dimitriadis, good to see you again. >> Thank you. >> Chief operating officer. >> Great to be here. >> Guys, congratulations. Bahrain, D.C. >> The world. >> The world, it's global. >> Thank you, yeah. >> C5 Global. >> It's great to be here. >> It's an exciting time. I mean, I got to ask you Eva, because we had previously met, talked about interviews in D.C. Smart people that known Amazon, because Teresa and Andy Jassy and Jeff Bezos always say, "We're going to be misunderstood for a while." Come on, that's not true. (laughing) A region in this area is going to explode the entrepreneurial scene. What's your take? >> I think that's absolutely true. As we see today at the Summit, there's just such a growing number of entrepreneurs and people who are excited to embrace digital innovation. Three years ago I think the story would have been different but ever since we set up the accelerator here, which was the first once in Bahrain, we've just seen an explosion of interest and not just from Bahrain but from around the GCC. Even start ups from abroad coming and setting up here as their Middle East practice. >> Talk about C5 for a second. Let's take a minute, to explain what you guys do. I jumped ahead a little bit because I'm excited because I just love the entrepreneurial energy. This is a really important thing happening and you guys are playing a role. Talk about C5 Accelerate, what are you guys doin'? What's your business model? Just take a minute to explain as a set up. >> So I'll let Eva talk maybe more about our global operations but really C5 Accelerate a few years ago, branch the business which was largely an investment business, including innovation business and we built Bahrain's first and one the regions, in fact, first cloud enabled accelerators and Bahrain's very first technology accelerator and we did that in partnership with the Economic Development Board, the labor firm Tamkeen and obviously with AWS. Really we benefited from the first mover advantage and the thinking around that was that as Amazon grows it's geographic footprint there is great opportunity to build on the cloud in places like the Middle East where the ecosystem is nascent and there is an amazing first mover advantage. >> Yeah. >> So when we partnered with the government to build this, we realized as we do that, we also need to contribute to building a healthy ecosystem so we built this first accelerator and we have felt-- >> When was that, by the way? >> 2016. >> Great, thank you. >> Actually September marks our two year. We've since graduated five cohorts. We're gearing up for six and we have 34 start ups under our belt. Our first cohort was an all Bahraini cohort and today we're very proud to say that actually half of the start ups that have graduated from this program that is based out of Bahrain are international start ups. That's what we're doing locally. Maybe Eva can tell you a little bit more about what we're doing on a global scale. >> You know and that's important. I want to make sure you got that out about having a bunch of start ups under your belt because when I went to the start up Bahrain session yesterday I was really, really impressed by two things. One is, just the smart energy, the smart people who like understand entrepreneurship. Either went to school for it or have learned through the scar tissue of trial and tribulations like myself. And then the entrepreneurs were there themselves. >> Mm-hmm. >> And you know a healthy entrepreneurial community when they start bitchin' and moanin', they're all chirping away, they're hungry. There's a hungry appetite for entrepreneurship here and creating but it's not fake entrepreneurship. They're really hungry. They're, where's the cash? Where's the capital? So this is really a positive sign. >> It is and I want to add something really quick before Eva jumps in, I think in the past two years what's great about a small ecosystem and the ability to pivot and build fast is you actually see the impact that you can have as an individual and as a company and as a community really on the landscape. But also regionally we've had great collaborative efforts across the GCC and in the region with partners in Saudi and Kuwait and Egypt and in Jordan so I think there's a lot of momentum that we're riding on now, and I think it's a great time to be building in the tech space. >> Well Eva, before you get to your comments. I just want to follow up on the comment around Saudi and different regions because this is a trend that has been happening for a while in Silicon Valley, as you know. People have been leaving Silicon Valley, because it's cost to live there, but people have been putting engineering teams outside of Silicon Valley. I mean, 20 years ago, you only went outside of Silicon Valley or the US to outsource which is not really product development, it's just coding. Then the trend became real engineering and product development, real chops outside. We just had Abdul on from Saudi and he was talking about his shape of his team, the psychology, the make up of the people, it's just not in Saudi Arabia. It's in China, it's all over the world. As developers are working across the world, this is a really big deal. I mean this is the new dynamic. >> Yep. >> Diverse teams, geo located, no borders, this is going to change the political landscape. It's a cultural shift. >> Definitely, I mean I think it's a while before we have here the same secret sauce that exists in Silicon Valley or that has existed there for the past decade or so. But the emphasis on training and upscaling is huge and as we've heard a number of times today, there are so many incentives to do so for free so you can actually learn to code, you can become a certified AWS coder for free in Bahrain. Which is a phenomenal advantage and step up. I mean, no one would pay me to do that in the UK. I think that, along with a number of other initiatives are really going to leap frog the development here. And in terms of what you talk about, the sort of the landscape and geo location, it goes in so many different directions now. There's no single focus so we had a Swiss company last year come and incorporate in Bahrain, and hire developers here to grow their business. It can go in so many different directions. >> Yeah, the winner take all business model is an old business model and now it's everyone's winning so it's a little bit of flattening of the wealth and the opportunities but the pie is getting bigger. >> Yes. >> I think this is the dynamic that cloud and Amazon continues to demonstrate that the Oracles, for instance, of the world, we got to win it all, lock everyone in and we got to own it. That ethos is not, that dog's not hunting, as they say. This is changing the entrepreneurial landscape and the other thing I observe is the younger generation. Leveling up is very easy to them. It's like a video game, right? Leveling up is AI, blockchain, I think one of your companies I talked to, oh we're doing a blockchain implementation. They will eat up the cloud. >> Mm. >> I mean it's going to be like, pretty fast. >> You mentioned-- >> So I'm expecting some accelerated. >> Definitely. I mean you mentioned hungry but they're also fearless. The entrepreneurs that we work with have that perfect mix of a super smart idea and an understanding of a niche sector of the market but also this resilience and recklessness that you need to embrace the opportunity. And all the scary stuff that comes with it. >> And I think adding to that, I think what's great with Amazon coming to Bahrain, with us working across the globe, it's a cross pollination that happens because whether we like it or not, like Eva said, we are not Silicon Valley yet and maybe we don't aspire to be specifically Silicon Valley and we want to build our own unique ecosystem but the lessons learned from the likes of Silicon Valley and London and Singapore and China and everywhere else in the world. >> Yeah. >> Really helps build, not just the skills required but the grit that could otherwise be absent. >> The grit's key, yeah. >> And it can engender the kind of cultural shift that's necessary so you need, so you can develop these robust and resilient qualities that are necessary for a founder. >> Well, that's a really great point. I moved from the east coast in the US to California with my first start up because that's where the action was and I can tell ya, I've been there 20 years and I've been an entrepreneur doing things ever since. And there's a fallacy of trying to emulate Silicon Valley. Every i dotted, t crossed and trying to take the playbook. There's no direct match, however, there's some consistencies in there. That's grit, creativity, openness, capital markets and community and this is something that you guys kind of have in place. And then adapting that to your culture. Now I will say that my impression here is it feels a little bit Silicon Valley because it's a little bit more open and loose. People like to go fast. Fast and loose is the Silicon Valley way. Dubai's a little bit more like New York to me. So I can feel more, valley-like here. I'm not saying that Dubai's bad, I'm just saying it's different cultures. Bigger, its more ... >> There's definitely a lot of agility here. I think one of the other advantages which leads back into what C5 is as a whole, we're primarily an investment business. We have a venture capital fund based in the UK. What we're really looking for is investible, scalable business models where we're de risking the cost of capital with cloud computing because that is how ultimately these start ups scale. Another benefit that we really see in this market is value for money. If you're a start up in Silicon Valley and you get to the stage that some of our start ups get to when they finish their program, your valuation is pretty much always triple what we would see here, so valuation's a very sensitive subject. Our start ups hate talking about it. We structure our deals with them in a way that generally avoids having a valuation. >> It's very easy to do business here. You just keep on increasing the valuation, all the stars will come dropping to your doorstep. >> It's a nuanced area. >> Yeah. >> But that being said, you can get really good value for money businesses but more importantly you're investing in the teams and the entrepreneurs and there's no shortage of that here. >> Let's talk about the ecosystem here and then let's talk about the women in tech because one of the things that blew me away yesterday was Teresa Carlson held a women breakfast and for the first time I got kicked off a table because they wanted to make room for the workshop. >> Sorry about that. (laughing) >> I'm like, wait a minute. This is not an inclusive environment. Sorry, no, we need the table. Okay, I know, I was happy to tap out. But I wasn't expecting that and the energy and the, just really, again, this event, they had to lock the doors for the keynote so there's really a big interest across the board. Talk about the ecosystem and then the women in tech situation. >> So I think the ecosystem is an interesting question because, I mean, we work very collaboratively. Like I said, even though this initiative largely was kind of envisioned by the government and mainly by the Economic Development Board and I'm sure you got a chance to speak to Khalid Humaidan, he might have given you a bit of an idea of how this started off but really the EBD threw this idea of start up Bahrain to the community and said, "Look, you guys lead on it." And it took a little bit of time for the community to figure out what that really means and what it's going to look like but it really made the community and ourselves also think pragmatically about what we want this ecosystem to look like. So even though it's not as mature, like I said, as other ecosystems further away and especially in the west, it is coming together very nicely because it's coming together as a collaborative effort. You see a very good continuous consultative work between private sector, public sector, the start ups and then the other stakeholders, including ourselves, and academia. We still have a long way to go, I think specially in areas and this is something that I always emphasize, is to shift the culture you really need to start at a much younger age so at schools, at universities. We engage with them and are keen to do more on that front but I think we are laying the foundation for what I hope in the next five, 10 years will be a pretty competitive entrepreneurial and start up-- >> It might be sooner. >> Hopefully sooner. >> Yeah. >> I think we have the right recipe now to build a robust ecosystem. >> Yeah, I can say I can attest to that after what I saw yesterday. Your thoughts? >> Yeah I mean our team in Bahrain is 100% Bahraini. I'm based in London, but Hadyah here leads a phenomenal team who are all Bahraini citizens. Being the island that it is, we know everybody so Hadyah's done an excellent job of engaging with everyone from schools to universities to post grads to public sector, private sector. So really all the stakeholders in the ecosystem are engaged and everyone from the oil and gas industry to the finance sphere are thinking about how innovation can advance their businesses so that they don't get left behind at the train station. >> Yeah. >> It's really top of mind and top of agenda which is a very invigorating scenario. I think, going back to some of the initiatives, from bankruptcy laws to having a fintech bay with the Central Bank of Bahrain, there's just so much, like they're constantly pushing the envelope to make this a friendly environment for entrepreneurs to come and do business. >> And I want to add one thing. There's always this question of, does government have a role to drive innovation and create an ecosystem? >> They do. >> I think Bahrain is a good example for others in the region and even beyond to say actually government does have an important role. >> They do. >> If you look at Bahrain, it's government that has been very flexible and nimble in terms of moving to accommodate. Whether it's the new bankruptcy laws or allowing for the fintech sandbox and a cloud first policy and shaping the start up Bahrain. The government has taken the lead on a lot of these initiatives so it's a good example of how there can be a top down approach to building an entrepreneurial landscape but also where the bottom needs to come and meet the top so I think Bahrain a good example. >> Just to reiterate, my observation is that they know how to get things going and sponsor but they're also listening and self aware and even on theCUBE here, we heard comments like, we'll get out of the way. >> Mm-hmm. >> Now that's the difference between good judgment. >> Mm-hmm. >> You know? And, no, no I funded you, I own you, I mean I've seen that in the public sector or, we're going to fund you as an NGO and then I kind of own you so come to my receptions and be my show horse-- >> Mascot. >> Show all of my people how good I am, donating money. So there's a little bit of a balance between enabling. >> Yep. >> But at the end of the day, this is going to be a fast pace and that's where I think the speed, knowing when to get out of the way and letting the community go. I mean, people like speed here. Cars are driving fast, you got a Formula 1 race track up at 14 months. >> They like speed but sometimes things are surprisingly slow. >> Yes. >> So it's incredible that we are where we are. You asked about women in tech and I think there's something there that we're really proud of. C5 globally, 43% of the start up founders that we've supported through our accelerators are women. In terms of diversity, we're thrilled about that statistic. We'd like it be 50%. >> Yep. >> And I think that the Middle East, we're seeing so much hunger from women entrepreneurs and women who want to learn to code to be founders and we want to do everything in our power to enable that. >> Computer science degrees coming out of the university? >> Absolutely. Hadyah here had this fantastic idea a year ago to found what we call C5 Nebula. I'll let Hadyah talk about why we came up with that name and how it relates to our business but this is now a new stream of our business which really it's a membership platform where all women globally are invited to join and we provide education, upscaling, jogs, connectivity, mentorships and through this network we are allowing a complete globalization of the talent and skills that we have. >> Yeah. >> So you can be a student in D.C. wanting to come and volunteer to work for a company here and we will make that match happen. I think it's a very exciting phase for us and we've seen so much demand for this program. Maybe Hadyah can talk about why we came up with this name? >> Yeah, so like Eva said, we, I'm Bahraini, we've always had, we've been lucky to have been pioneering and have work very closely men and have had really equal opportunity but in industries like tech, globally, women's representation is lower than that of men and there are areas where there's still work to be done. >> A lot of work to be done, yeah. >> So last year, actually, with the first AWS Summit, when Teresa was out here, we figured we do a women in tech breakfast. When we were curating that guest list we couldn't find that many women and we didn't know if wasn't that we didn't know them or that they didn't exist and we realized really we need to put together something to bring all the women together and work more closely so we built Nebula, really to, like Eva said, do three things and a little more. One is the connectivity side of things and then the upscaling but also to raise awareness and appreciation. >> What is Nebula? >> What is? >> What is Nebula? >> So Nebula, scientifically it's an astrological, astronomical phenomenon-- >> But it's your network group, is that what it's called? >> It's a platform. >> Okay. >> So it's actually been officially launched three weeks ago, you can go online and visit it and it's a platform that allows you to become a member of Nebula and gives you access to mentorship, to opportunities to upscale and train but also to raise awareness and appreciation for the amazing opportunities for women in the tech space. >> Is there a URL? >> There is a URL, it's-- >> We've been debating what is is today. (laughing) >> It's www.c5nebula.com. >> Okay, I'll put it up, publish it with the video. >> And what it means, it's the Latin word for cloud and it's where stars are born. >> Yeah. It's also, what's important, is it's a compilation of a bunch of different clouds and electrons and it's a mess, it's a bit of a mess but it's a lot of forces working together and I guess the moral of the story is, we can create stars in the space but we all have to work together and it all has to come together to-- >> And it's powerful when you work together. >> Only 10% of VC funding worldwide goes to women founder companies and 1% of that goes to women of color so there's some staggering statistics there. Globally, this is not a Middle East problem, this is globally a real big area of disparity that we're trying to help address. >> Well you guys know our door's open in California and Boston, and certainly the women in tech, we got a big network, we can merge them into the Nebula connect our networks. >> We would love that. >> We would love that. >> We're open and anything you guys have to share with us we love co-creating with the communities, that's what we do at theCUBE. Thanks for coming on and sharing. >> Thanks for having us. >> Thank you, John. It's been a pleasure. >> You got a great mission. Big supporter. C5 Accelerate, they're the ones on the ground, making things happen, gettin' those sparks of entrepreneurship and helping them capture them into one community, create some energy and some momentum and help people create value and also capture the value, that's what it's all about here. You got Amazon Web Services' region in the Middle East, CUBE coverage continues after this short break. (upbeat techno music)

live from Stanford University in Palo Alto California it's the cube covering women in data science conference 2018 brought to you by Stanford welcome to the cube we are alive at Stanford University I'm Lisa Martin and we are at the 3rd annual women in data science conference or woods whiz if you're not familiar is a one-day technical conference that has keynote speakers technical vision talks as well as a career panel and we are fortunate to have guests from all three today it's also an environment it's really a movement that's aimed at inspiring and educating data scientists globally and supporting women in the field this event is remarkable in its third year they are expecting to reach sit down for this 100,000 people today we were here at Stanford this is the main event in person but there's over 150 plus regional events around the globe in 50 plus countries and I think those numbers will shift up during the day and I'll be sure to brief you on that we're excited to be joined by one of the speakers featured on mainstage this morning not only a cube alum not returning to us but also the first ever female president of Harvey Mudd College dr. Maria Klawe a maria welcome back to the cube thank you it's great to be here it's so exciting to have you here I love you representing with your t-shirt there I mentioned you are the first-ever female president of Harvey Mudd you've been in this role for about 12 years and you've made some pretty remarkable changes there supporting women in technology you gave some stats this morning in your talk a few minutes ago share with us what you've done to improve the percentages of females in faculty positions as well as in this student body well the first thing I should say is as president I do nothing nothing it's like a good job the whole thing that makes it work at Harvey Mudd is we are community that's committed to diversity and inclusion and so everything we do we try to figure out ways that we will attract people who are underrepresented so that's women in areas like computer science and engineering physics it's people of color in all areas of science and engineering and it's also LGTB q+ i mean it's you know it's it's muslims it's it's just like all kinds of things and our whole goal is to show that it doesn't matter what race you are doesn't matter what gender or anything else if you bring hard work and persistence and curiosity you can succeed i love that especially the curiosity part one of the things that you mentioned this morning was that for people don't worry about the things that you you might think you're not good at i thought that was a very important message as well as something that I heard you say previously on the cube as well and that is the best time that you found to reach women young women and to get them interested in stem as even a field of study is the first semester in college and I should with you off camera that was when I found stem in biology tell me a little bit more about that and how what are some of the key elements that you find about that time in a university career that are so I guess right for inspire inspiration so I think the thing is that when you're starting in college if somebody can introduce you to something you find fun engaging and if you can really discover that you can solve major issues in the world by using these ideas these concepts the skills you're probably going to stay in that and graduate in that field whereas if somebody does that to when you're in middle school there's still lots of time to get put off and so our whole idea is that we emphasize creativity teamwork and problem-solving and we do that whether it's in math or an engineering or computer science or biology we just in all of our fields and when we get young women and young men excited about these possibilities they stick with it and I love that you mentioned the word fun and curiosity I can remember exactly where I was and bio 101 and I was suddenly I'd like to biology but never occurred to me that I would ever have the ability to study it and it was a teacher that showed me this is fun and also and I think you probably do this too showed that you believe in someone you've got talent here and I think that that inspiration coming from a mentor whether you know it's a mentor or not is a key element there that is one that I hope all of the the viewers today and the women that are participating in which have the chance to find so one of the things every single one of us can do in our lives is encourage others and you know it's amazing how much impact you can have I met somebody who's now a faculty person at Stanford she did her PhD in mechanical engineering her name is Allison Marsden I hadn't seen her for I don't know probably almost 12 years and she said she came up to me and she said I met you just as I was finishing my PhD and you gave me a much-needed pep talk and you know that is so easy to do believing in people encouraging them and it makes so much difference it does I love that so wins is as I mentioned in the third annual and the growth that they have seen is unbelievable I've not seen anything quite like it in in tech in terms of events it's aimed at inspiring not just women and data science but but data science in general what is it about wizz that attracted you and what are some of the key things that you shared this morning in your opening remarks well so the thing that attracts me about weeds is the following data science is growing exponentially in terms of the job opportunities in terms of the impact on the world and what I love about withes is that they had the insight this flash of genius I think that they would do a conference where all the speakers would be women and just that they would show that there are women all over the world who are contributing to data science who are loving it who are being successful and it's it's the crazy thing because in some ways it's really easy to do but nobody had done it right and it's so clear that there's a need for this when you think about all of the different locations around the world that are are doing a width version in Nigeria in Mumbai in London in you know just all across the world there are people doing this yeah so the things I shared are number one oh my goodness this is a great time to get into data science it's just there's so many opportunities in terms of career opportunities but there's so many opportunities to make a difference in the world and that's really important number two I shared that it's you never too old to learn math and CS and you know my example is my younger sister who's 63 and who's learning math and computer science at the northern Alberta Institute of Technology Nate all the other students are 18 to 24 she suffers from fibromyalgia she's walked with a walker she's quite disabled she's getting A's and a-pluses it's so cool and you know I think for every single person in the world there's an opportunity to learn something new and the most important thing is hard work and perseverance that it's so much more important than absolutely anything else I agree with that so much it's it's such an inspiring time but I think that you said there was clearly a demand for this what Wits has done in such a short time period demonstrates massive demand the stats that I was reading the last couple of days that show that women with stem degrees only 26% of them are actually working in STEM fields that's very low and and even can start from things like how how companies are recruiting talent and the messages that they're sending may be the right ones maybe not so much so I have a great example for you about companies recruiting talent so about three years ago I was no actually almost four years ago now I was talking in a conference called HR 50 and it's a conference that's aimed at the chief human resource officers of 50 multinationals and my talk I was talking for 25 minutes on how to recruit and retain women in tech careers and afterwards the chief HR officer from Accenture came up to me and she said you know we hire 17,000 software engineers a year Justin India 17,000 and she said we've been coming in at 30 percent female and I want to get that up to 45 she said you told me some really good things I could use she she said you told me how to change the way we advertise jobs change the way we interview for jobs four months later her name is Ellen Chowk Ellen comes up to me at another conference this has happens to be the most powerful women's summit that's run by Fortune magazine every year and she comes up and she says Maria I implemented different job descriptions we changed the way we interview and I also we started actually recruiting at Women's College engineering colleges in India as well as co-ed once she said we came in at 42% Wow from 30 to 42 just making those changes crying I went Ellen you owe me you're joining my more my board and she did right and you know they have Accenture has now set a goal of being at 50/50 in technical roles by 2025 Wow they even continued to come in all around the world they're coming in over 40% and then they've started really looking at how many women are being promoted to partners and they've moved that number up to 30% in the most recent year so you know it's a such a great example of a company that just decided we're gonna think about how we advertise we're going to think about how we interview we're gonna think about how we do promotions and we're going to make it equitable and from a marketing perspective those aren't massive massive changes so whether it expects quite simple exactly yeah these are so the thing I think about so when I look at what's happening at Harvey Mudd and how we've gotten more women into computer science engineering physics into every discipline it's really all about encouragement and support it's about believing in people it's about having faculty who when they start teaching a class the perhaps is technically very rigorous they might say this is a really challenging course every student in this course who works hard is going to succeed it's setting that expectation that everyone can succeed it's so important I think back to physics and college and how the baseline was probably 60% in terms of of grades scoring and you went in with intimidation I don't know if I can do this and it sounds like again a such a simple yet revolutionary approach that you're taking let's make things simple let's be supportive and encouraging yet hopefully these people will get enough confidence that they'll be able to sustain that even within themselves as they graduate and go into careers whether they stay in academia or go in industry and I know you've got great experiences in both I have I so I've been very lucky and I've been able to work both in academia and in industry I will say so I worked for IBM Research for eight years early in my career and you know I tribute a lot of my success as a leader since then to the kind of professional development that I got as a manager at IBM Research and you know what I think is that I there's not that much difference between creating a great learning environment and a great work environment and one of the interesting results that came out of a study at Google sometime in the last few months is they looked at what made senior engineering managers successful and the least important thing was their knowledge of engineering of course they all have good knowledge of engineering but it was empathy ability to mentor communication skills ability to encourage all of these kinds of things that we think of as quote unquote soft skills but to actually change the world and and on those sasuke's you know we hear a lot about the hard skills if we're thinking about data scientists from a role perspective statistical analysis etcetera but those soft skills empathy and also the ability to kind of bring in different perspectives for analyzing data can really have a major impact on every sector and socially in the world today and that's why we need women and people of color and people who are not well represented in these fields because data science is changing everything in the world absolutely is and if we want those changes to be for the better we really need diverse perspectives and experiences influencing things that get made because you know algorithms are not algorithms can be hostile and negative as well as positive and you know good for the world and you need people who actually will raise the questions about the ethics of algorithms and how it gets used there's a great book about how math can be used for the bad of humanity as well as the good of humanity and until we get enough people with different perspectives into these roles nobody's going to be asking those questions right right well I think with the momentum that we're feeling in this movement today and it sounds like what you're being able to influence greatly at Mudd for the last twelve years plus there is there are our foundations that are being put in place with not just on the education perspective but on the personal perspective and in inspiring the next generation giving them helping them I should say achieve the confidence that they need to sustain them throughout their career summary I thank you so much for finding the time to join us this morning on the cube it's great to have you back and we can't wait to talk to you next year and hear what great things do you influence and well next twelve months well it's wonderful to have a chance to talk with you as well thank you so much excellent you've been watching the cube we're live at Stanford University for the third annual women in data science wins conference join the conversation hashtag wins 2018 I'm Lisa Martin stick around I'll be right back with my next guest after a short break

>> Announcer: Live from New Orleans, it's theCUBE. Covering VeeamON 2017, brought to you by Veeam. >> Welcome back to New Orleans everybody, I'm Dave Vellante with Stu Miniman. This is theCUBE, the leader in live tech-coverage. This is day one of our continuous coverage of VeeamON, continuous coverage of continuous data protection. Big theme here today. Maria Olson is here, she's the vice president of Global & Strategic Alliances at NetApp. Andy Vandeveld is back, he's the vice president of Global Alliances at Veeam. Folks, welcome to theCUBE, good to see you again. >> Thank you, nice to be here. >> Thank you. >> So, first of all, let's start with Maria. So VeeamON, big show, a lot of action. How's it going? >> You know, the energy here is amazing here. I remember being at VeeamON years before, and what I see here in terms of the number of customers and partners, and starting to see the big growth in the enterprise market. And all the announcements and innovation that they've made today is fantastic. >> There's like a groundswell right? We've been following NetApp for years. You guys have the best snapshot technology in the marketplace, customers love it and very efficient, and have always had an interesting take on data protection. And data fabric obviously is a big theme of NetApp these days, so explain that to us and we can get into how you guys partner. >> Sure absolutely, so most companies think of us as a storage company, but we really have evolved from a storage company to a data management company. We have a full portfolio of products, including all of our All Flash FAS offerings. We did an acquisition, which was our largest acquisition with SolidFire as well. We also have back up to Cloud offerings with our AltaVault offering that backs up to Azure and Amazon. We have StorageGRID Webscale. We have a very full, large portfolio. What all this allows customers to do, and where NetApp is heading is in terms of being able to manage and move the date, regardless of where it's at. So I call this, the gold opportunity. I just came back from SAPPHIRE, you talk to Bill McDermott, he talks about how data's gold. You heard the same thing here with Peter McKay as well. And to me the whole thing, it doesn't matter if the gold's there, you got to be able to manage it, and monetize, and do something with it. And that's what NetApp helps provide. >> So Andy, that sounds very consistent with the strategy that Veeam is putting forth. >> Yes. >> That we heard certainly this morning, and throughout this conference. So what's the partnership? Where do you pick up and NetApp leave off, or vice versa? >> Well, so in the date protection space, it's the ability to manage the data, to make sure that it's getting into a form that can be stored and accessed and available as quickly as possible, is really what we're focusing on. And to do that, we need partners like NetApp, who have the infrastructure assets that we can leverage. Particularly as we move more and more into the enterprise business with enterprise customers. Those customer's are spitting off a lot of data. They need their data to be available as quickly as possible in the case of an outage or some other disruption to their business. And to do that, Veeam needs infrastructure partners that have robust portfolios that can handle that sort of requirement, and that's where the relationship with NetApp comes into play. And it's been very good for us over the years. >> I like this notion of data fabric, has a connotation of fluidity, and it sort of reminds me of the Veeam Waves here a little bit. So explain more Maria, if you will, the data fabric, what is that concept, how are customers actually getting value out of it? >> Absolutely, so data fabric was more of a framework, right? We don't have a SKU that you just go buy data fabric. It's really a framework and a portfolio of products, integrated with our ecosystem of partners like Veeam, to be able to manage and move the data. Regardless if it's on PRIM, or where they want to go as part of their digital transformation. So customers are all at different phases in terms of where they want to go, in terms of becoming more of a digitally-oriented business. And we help get them there through the journey, because of the strength that we have on the on premise side, as well as the integrations that we've done with our partner ecosystem, specifically with Veeam and others. So we can help move them in that direction. >> So take that a little bit further, in terms of, so the customer sees this vast portfolio. Andy you were talking before about NetApps infrastructure. It's pretty vast, it's a leader in it's space. What are they asking you guys for? What are they challenging you to do? Specifically in the context of data protection. >> So customers are asking us, number one, make sure that it's simple. And that's one of the big value props that Veeam makes, number one. >> And NetApp over the years. >> And NetApp too. That it's always on and available. That there is no disaster that occurs, that the data is there, that we know where it is, that we can manage it, we can back it up. Those are the big things. The third things customers are asking for, is help us in terms of, how do we digitally transform our business? It's the business outcome that they're looking for. Of which, the products that NetApp and Veeam does, is a subset of that, that helps them on that journey. So they can actually digitally migrate, and become more of a digitally-oriented business, with our offerings helping in the whole backup and recovery and whole data management space. >> Yeah and I would just sort of tag onto that, customer's consumption models are changing. So they're on PRIM, they're in a private Cloud, they're in a public Cloud. The way that they consume is changing, and it's different. And no two look the same. And I think what customers are telling us is, let us decide how we're going to consume. You just be able to accommodate that consumption. And that's really what we've been focusing on. So if it's in an on PRIM environment, great. If it's in a public Cloud, fantastic. If it's some hybrid model, that's great too. We can accommodate that, and that's really what customers are asking us. As well as making sure that we accommodate the various business models that exist. So whether it's purchasing licenses, or some subscription-based models or whatever, they want that flexibility and that's what they're asking us to provide. >> Maria, I'm wondering if you have any joint customers that you're highlighting here at the show, or any specific examples you might be able to walk us through. >> So we have several joint customers, as a matter of fact, you heard Peter McKay talk about 210,000 customers. Of those, 30% are NetApp, so it's a very big area. And now, in terms of some of the announcements they've made, in terms of supporting NaaS, in terms of physical environment. NetApp is the leader in that space, so it's even going to become broader. So you saw today, in terms of Peter McKay talking about the Denver Broncos, that's a big NetApp customer in terms of the solutions that they have there. Also, Telefónica was announced there. Very large service provider. It's another very big NetApp customer. So there's a lot of customers in the enterprise space. Veeam's more known in terms of the s and v space, but when you start to look at the momentum they've had in going up the stack, there's a lot of enterprise customers that we actually are jointly engaging with. >> I would just say that the more that we penetrate the enterprise market and the service provider market, the more that we're going to need partnerships like we have with NetApp. To become stronger, because they're the trusted advisors, the ones that the customers are listening to. It's easier for us just to ride on their coattails into these opportunities than to try to create these relationships all ourselves. That's what makes this such a great partnership for us. >> The Cloud service customer channel base has come up a couple times today. But we haven't really explored some of the fundamental assumptions behind it. And what I want to ask you guys is, everybody sees the ascendancy of Amazon. Very impressive, amazing growth. Yet at the same time, your respective Cloud service provider businesses are also growing very rapidly. >> Maria: Very much. >> So you've got the disruption to the traditional legacy enterprise business we all have covered that very well. But there's not much been discussed about what's going to happen within the Cloud business. There's maybe some camp that says, okay everything's going to go to Amazon and I think many people believe that. But what's happening within the Cloud service provider base? It seems to be quite fragmented, which is a good thing for you guys. It seems to be local in nature, very specialized services, and ability to compete with Amazon and Azure, because they're not competing necessarily with scale volume, they're competing in other ways. So I wonder if you could help us unpack that a little bit. As to what's happening in your respective bases there. >> Yeah, so we're seeing a lot of momentum in the service provider space. So we've sold a lot of storage and data management over to what the large new service providers of the world. The IBM SoftLayers, the Azures, Google Cloud Platform. All of them as well as the existing ones, the AT&Ts and the Verizons and Telefónicas of the world. And so we continue to see a fragmentation there. You kind of have the new world service providers, and the old world service providers. And they're all trying to figure out the business model, so they can make sure that they're all going to be there over the next 20, 25 years to see how this whole game evolves. But we have a big footprint in both of those camps. And as a matter of fact, one of the things I love about the relationship between NetApp an Veeam, is we're companies that are embracing Cloud. We're not fighting Cloud, we're really trying to embrace it. So we have multiple offerings in terms of NetApp across our storage and date management, across all the new emerging Cloud players, and the existing one. And Veeam also has pretty deep relationships. They just announced today in offerings with AWS, and with Microsoft Azure as well. >> Dave: Anything you'd add Andy? >> Yeah, I think you're right about the market being a little bit more fragmented. There are smaller, more specialized Cloud providers. And there's a set of customers that want that. So I think it kind of gets back to the point that I was making earlier, which is the consumption models are changing. And who they consume from, in terms of Cloud, is not 100% consistent, and so we need to be able to deliver the technology that can accommodate whatever that decision is that the customer makes. >> From a partnership perspective, how does something like this start? And what do you, I mean obviously you say, let's go to market together. That's a logical starting point, but then there's maybe some other integration that has to take place. What do you guys sort of set out to accomplish? What are the milestones, the metrics, that you try to, how do you measure success on a partnership like this? How do you know when it's going to work, and is working? >> Yeah, that's a great question. Number one, you first have to have alignment in terms of what solutions you're going to go out there and build. And I think part of the secret of the success of the relationship, if you think back in terms of, NetApp made a big bet in virtualized environments. In doing big differentiated offerings with VMware. Even though their owned by EMC. And we we're extremely successful, 50,000 joint customers. You look at Veeam, they made a big bet with VMware, so our installed basis and the co-nih-va-tion and development that we've done already there, is already paid off there in spades. So number one, you got to have the co-nih-va-tion and the solution that you're building. The second thing is an aligned go-to-market, in terms of what is our go-to-market plan, how are we doing that through the channel? Is it a comprehensive program? What does that look like? And then it comes down to people at the end of the day, and the culture. Do the companies have really good cultures and people that really want to go at, and execute those plans? >> Yeah, and we have strong alignment at the executive levels as well, which helps. Because you need to have that sort of strategic vision, you're looking out 18 months, 24 months. Are we in alignment? And I think that helps. I would say another strong metric for Veeam is our Net Promoter Score, we're 73, it's off the charts, it's fantastic. That doesn't happen if you're not delivering the right solutions with the right set of partners. And to us, that's just another metric of, how successful are these partnerships? Particularly the one that we have with NetApp. >> And actually, I looked at NetApps Net Promoter Score, and we're 64, so we're way up there as well. So that's another area that we're very aligned as well. >> You know NPS is interesting. If you're, you're not really a one-product company, but you're smaller, and so it's easier to have a high NPS when you're smaller. Now, of course you've got on-tap. >> I wanted to be on that graph up there on the key note. >> That's pretty good. (group laughing) I was at ServiceNow last week, and they have a very happy customer base, and they were touting their, I think 53 NPS. And that's, so 60's for a company the size of NetApp. And you guys, like you say, off the charts. So that's impressive, go ahead Stu. >> Yeah just the last piece you talked about, some of the announcements that were made that impact, including in v 10, there's going to be NaaS. We look forward, anything that we should be looking to measure success of the partnerships, and anything that your companies are working on together that you can speak to. >> Well I think at the end of the day, it's customers and revenue. Ensuring that that continues to grow. Veeam's on fire, they've got 210,000 customers, they're growing at 450-- >> 245,000 at the end of-- >> 45, and every day they're adding 200 customers a day. >> Peter corrected me. (group laughing) >> Right, yeah exactly, so I really think we measure it by customers and revenue, in terms of how we're driving. And then new solution areas, like I said, with Cloud we're very aligned in both companies, embracing Cloud. Big opportunity to go after some of these service provider areas. >> Yeah, I think we're going to continue to focus on delivering joint solutions. That's really kind of, if I had to put my finger on one thing, watch this space. It's joint solutions we want to put out to the marketplace that are going to benefit our customers. >> All right, we have to leave it there. Thanks very much for coming on theCUBE. It was great to see you. >> All right, thank you. >> Thank you. Appreciate it. >> You're welcome. All right, keep it right there everybody. We'll be back, rockin' New Orleans with theCube VeeamON 2017. (upbeat techno music) (keyboard typing)

(light music) >> Announcer: TheCUBE's live coverage is made possible by funding from Dell Technologies. Creating technologies that drive human progress. (upbeat music) >> Welcome back to the Fira in Barcelona. Dave Vellante with Dave Nicholson. Lisa Martin's been here all week. John Furrier is in our Palo Alto studio, banging out all the news. Don't forget to check out siliconangle.com, thecube.net. This is day four, our last segment, winding down. MWC23, super excited to be here. Wayne Duso, friend of theCUBE, VP of engineering from products at AWS is here with Iyad Tarazi, who's the CEO of Federated Wireless. Gents, welcome. >> Good to be here. >> Nice to see you. >> I'm so stoked, Wayne, that we connected before the show. We texted, I'm like, "You're going to be there. I'm going to be there. You got to come on theCUBE." So thank you so much for making time, and thank you for bringing a customer partner, Federated Wireless. Everybody knows AWS. Iyad, tell us about Federated Wireless. >> We're a software and services company out of Arlington, Virginia, right outside of Washington, DC, and we're really focused on this new technology called Shared Spectrum and private wireless for 5G. Think of it as enterprises consuming 5G, the way they used to consume WiFi. >> Is that unrestricted spectrum, or? >> It is managed, organized, interference free, all through cloud platforms. That's how we got to know AWS. We went and got maybe about 300 products from AWS to make it work. Quite sophisticated, highly available, and pristine spectrum worth billions of dollars, but available for people like you and I, that want to build enterprises, that want to make things work. Also carriers, cable companies everybody else that needs it. It's really a new revolution for everyone. >> And that's how you, it got introduced to AWS. Was that through public sector, or just the coincidence that you're in DC >> No, I, well, yes. The center of gravity in the world for spectrum is literally Arlington. You have the DOD spectrum people, you have spectrum people from National Science Foundation, DARPA, and then you have commercial sector, and you have the FCC just an Uber ride away. So we went and found the scientists that are doing all this work, four or five of them, Virginia Tech has an office there too, for spectrum research for the Navy. Come together, let's have a party and make a new model. >> So I asked this, I'm super excited to have you on theCUBE. I sat through the keynotes on Monday. I saw Satya Nadella was in there, Thomas Kurian there was no AWS. I'm like, where's AWS? AWS is everywhere. I mean, you guys are all over the show. I'm like, "Hey, where's the number one cloud?" So you guys have made a bunch of announcements at the show. Everybody's talking about the cloud. What's going on for you guys? >> So we are everywhere, and you know, we've been coming to this show for years. But this is really a year that we can demonstrate that what we've been doing for the IT enterprise, IT people for 17 years, we're now bringing for telcos, you know? For years, we've been, 17 years to be exact, we've been bringing the cloud value proposition, whether it's, you know, cost efficiencies or innovation or scale, reliability, security and so on, to these enterprise IT folks. Now we're doing the same thing for telcos. And so whether they want to build in region, in a local zone, metro area, on-prem with an outpost, at the edge with Snow Family, or with our IoT devices. And no matter where they want to start, if they start in the cloud and they want to move to the edge, or they start in the edge and they want to bring the cloud value proposition, like, we're demonstrating all of that is happening this week. And, and very much so, we're also demonstrating that we're bringing the same type of ecosystem that we've built for enterprise IT. We're bringing that type of ecosystem to the telco companies, with CSPs, with the ISP vendors. We've seen plenty of announcements this week. You know, so on and so forth. >> So what's different, is it, the names are different? Is it really that simple, that you're just basically taking the cloud model into telco, and saying, "Hey, why do all this undifferentiated heavy lifting when we can do it for you? Don't worry about all the plumbing." Is it really that simple? I mean, that straightforward. >> Well, simple is probably not what I'd say, but we can make it straightforward. >> Conceptually. >> Conceptually, yes. Conceptually it is the same. Because if you think about, firstly, we'll just take 5G for a moment, right? The 5G folks, if you look at the architecture for 5G, it was designed to run on a cloud architecture. It was designed to be a set of services that you could partition, and run in different places, whether it's in the region or at the edge. So in many ways it is sort of that simple. And let me give you an example. Two things, the first one is we announced integrated private wireless on AWS, which allows enterprise customers to come to a portal and look at the industry solutions. They're not worried about their network, they're worried about solving a problem, right? And they can come to that portal, they can find a solution, they can find a service provider that will help them with that solution. And what they end up with is a fully validated offering that AWS telco SAS have actually put to its paces to make sure this is a real thing. And whether they get it from a telco, and, and quite frankly in that space, it's SIs such as Federated that actually help our customers deploy those in private environments. So that's an example. And then added to that, we had a second announcement, which was AWS telco network builder, which allows telcos to plan, deploy, and operate at scale telco network capabilities on the cloud, think about it this way- >> As a managed service? >> As a managed service. So think about it this way. And the same way that enterprise IT has been deploying, you know, infrastructure as code for years. Telco network builder allows the telco folks to deploy telco networks and their capabilities as code. So it's not simple, but it is pretty straightforward. We're making it more straightforward as we go. >> Jump in Dave, by the way. He can geek out if you want. >> Yeah, no, no, no, that's good, that's good, that's good. But actually, I'm going to ask an AWS question, but I'm going to ask Iyad the AWS question. So when we, when I hear the word cloud from Wayne, cloud, AWS, typically in people's minds that denotes off-premises. Out there, AWS data center. In the telecom space, yes, of course, in the private 5G space, we're talking about a little bit of a different dynamic than in the public 5G space, in terms of the physical infrastructure. But regardless at the edge, there are things that need to be physically at the edge. Do you feel that AWS is sufficiently, have they removed the H word, hybrid, from the list of bad words you're not allowed to say? 'Cause there was a point in time- >> Yeah, of course. >> Where AWS felt that their growth- >> They'll even say multicloud today, (indistinct). >> No, no, no, no, no. But there was a period of time where, rightfully so, AWS felt that the growth trajectory would be supported solely by net new things off premises. Now though, in this space, it seems like that hybrid model is critical. Do you see AWS being open to the hybrid nature of things? >> Yeah, they're, absolutely. I mean, just to explain from- we're a services company and a solutions company. So we put together solutions at the edge, a smart campus, smart agriculture, a deployment. One of our biggest deployment is a million square feet warehouse automation project with the Marine Corps. >> That's bigger than the Fira. >> Oh yeah, it's bigger, definitely bigger than, you know, a small section of here. It's actually three massive warehouses. So yes, that is the edge. What the cloud is about is that massive amount of efficiency has happened by concentrating applications in data centers. And that is programmability, that is APIs that is solutions, that is applications that can run on it, where people know how to do it. And so all that efficiency now is being ported in a box called the edge. What AWS is doing for us is bringing all the business and technical solutions they had into the edge. Some of the data may send back and forth, but that's actually a smaller piece of the value for us. By being able to bring an AWS package at the edge, we're bringing IoT applications, we're bringing high speed cameras, we're able to integrate with the 5G public network. We're able to bring in identity and devices, we're able to bring in solutions for students, embedded laptops. All of these things that you can do much much faster and cheaper if you are able to tap in the 4,000, 5,000 partners and all the applications and all the development and all the models that AWS team did. By being able to bring that efficiency to the edge why reinvent that? And then along with that, there are partners that you, that help do integration. There are development done to make it hardened, to make the data more secure, more isolated. All of these things will contribute to an edge that truly is a carbon copy of the data center. >> So Wayne, it's AWS, Regardless of where the compute, networking and storage physically live, it's AWS. Do you think that the term cloud will sort of drift away from usage? Because if, look, it's all IT, in this case it's AWS and federated IT working together. How, what's your, it's sort of a obscure question about cloud, because cloud is so integrated. >> You Got this thing about cloud, it's just IT. >> I got thing about cloud too, because- >> You and Larry Ellison. >> Because it's no, no, no, I'm, yeah, well actually there's- >> There's a lot of IT that's not cloud, just say that okay. >> Now, a lot of IT that isn't cloud, but I would say- >> But I'll (indistinct) cloud is an IT tool, and you see AWS obviously with the Snow fill in the blank line of products and outpost type stuff. Fair to say that you're, doesn't matter where it is, it could be AWS if it's on the edge, right? >> Well, you know, everybody wants to define the cloud as what it may have been when it started. But if you look at what it was when it started and what it is today, it is different. But the ability to bring the experience, the AWS experience, the services, the operational experience and all the things that Iyad had been talking about from the region all to all the way to, you know, the IoT device, if you would, that entire continuum. And it doesn't matter where you start. Like if you start in region and you need to bring your value to other places because your customers are asking you to do so, we're enabling that experience where you need to bring it. If you started at the edge, and- but you want to build cloud value, you know, whether it's again, cost efficiency, scalability, AI, ML or analytics into those capabilities, you can start at the edge with the same APIs, with the same service, the same capabilities, and you can build that value in right from the get go. You don't build this bifurcation or many separations and try to figure out how do I glue them together? There is no gluing together. So if you think of cloud as being elastic, scalable flexible, where you can drive innovation, it's the same exact model on the continuum. And you can start at either end, it's up to you as a customer. >> And I think if, the key to me is the ecosystem. I mean, if you can do for this industry what you've done for the technology- enterprise technology business from an ecosystem standpoint, you know everybody talks about flywheel, but that gives you like the massive flywheel. I don't know what the ratio is, but it used to be for every dollar spent on a VMware license, $15 is spent in the ecosystem. I've never heard similar ratios in the AWS ecosystem, but it's, I go to reinvent and I'm like, there's some dollars being- >> That's a massive ecosystem. >> (indistinct). >> And then, and another thing I'll add is Jose Maria Alvarez, who's the chairman of Telefonica, said there's three pillars of the future-ready telco, low latency, programmable networks, and he said cloud and edge. So they recognizing cloud and edge, you know, low latency means you got to put the compute and the data, the programmable infrastructure was invented by Amazon. So what's the strategy around the telco edge? >> So, you know, at the end, so those are all great points. And in fact, the programmability of the network was a big theme in the show. It was a huge theme. And if you think about the cloud, what is the cloud? It's a set of APIs against a set of resources that you use in whatever way is appropriate for what you're trying to accomplish. The network, the telco network becomes a resource. And it could be described as a resource. We, I talked about, you know, network as in code, right? It's same infrastructure in code, it's telco infrastructure as code. And that code, that infrastructure, is programmable. So this is really, really important. And in how you build the ecosystem around that is no different than how we built the ecosystem around traditional IT abstractions. In fact, we feel that really the ecosystem is the killer app for 5G. You know, the killer app for 4G, data of sorts, right? We started using data beyond simple SMS messages. So what's the killer app for 5G? It's building this ecosystem, which includes the CSPs, the ISVs, all of the partners that we bring to the table that can drive greater value. It's not just about cost efficiency. You know, you can't save your way to success, right? At some point you need to generate greater value for your customers, which gives you better business outcomes, 'cause you can monetize them, right? The ecosystem is going to allow everybody to monetize 5G. >> 5G is like the dot connector of all that. And then developers come in on top and create new capabilities >> And how different is that than, you know, the original smartphones? >> Yeah, you're right. So what do you guys think of ChatGPT? (indistinct) to Amazon? Amazon turned the data center into an API. It's like we're visioning this world, and I want to ask that technologist, like, where it's turning resources into human language interfaces. You know, when you see that, you play with ChatGPT at all, or I know you guys got your own. >> So I won't speak directly to ChatGPT. >> No, don't speak from- >> But if you think about- >> Generative AI. >> Yeah generative AI is important. And, and we are, and we have been for years, in this space. Now you've been talking to AWS for a long time, and we often don't talk about things we don't have yet. We don't talk about things that we haven't brought to market yet. And so, you know, you'll often hear us talk about something, you know, a year from now where others may have been talking about it three years earlier, right? We will be talking about this space when we feel it's appropriate for our customers and our partners. >> You have talked about it a little bit, Adam Selipsky went on an interview with myself and John Furrier in October said you watch, you know, large language models are going to be enormous and I know you guys have some stuff that you're working on there. >> It's, I'll say it's exciting. >> Yeah, I mean- >> Well proof point is, Siri is an idiot compared to Alexa. (group laughs) So I trust one entity to come up with something smart. >> I have conversations with Alexa and Siri, and I won't judge either one. >> You don't need, you could be objective on that one. I definitely have a preference. >> Are the problems you guys solving in this space, you know, what's unique about 'em? What are they, can we, sort of, take some examples here (indistinct). >> Sure, the main theme is that the enterprise is taking control. They want to have their own networks. They want to focus on specific applications, and they want to build them with a skeleton crew. The one IT person in a warehouse want to be able to do it all. So what's unique about them is that they're now are a lot of automation on robotics, especially in warehousing environment agriculture. There simply aren't enough people in these industries, and that required precision. And so you need all that integration to make it work. People also want to build these networks as they want to control it. They want to figure out how do we actually pick this team and migrate it. Maybe just do the front of the house first. Maybe it's a security team that monitor the building, maybe later on upgrade things that use to open doors and close doors and collect maintenance data. So that ability to pick what you want to do from a new processors is really important. And then you're also seeing a lot of public-private network interconnection. That's probably the undercurrent of this show that haven't been talked about. When people say private networks, they're also talking about something called neutral host, which means I'm going to build my own network, but I want it to work, my Verizon (indistinct) need to work. There's been so much progress, it's not done yet. So much progress about this bring my own network concept, and then make sure that I'm now interoperating with the public network, but it's my domain. I can create air gaps, I can create whatever security and policy around it. That is probably the power of 5G. Now take all of these tiny networks, big networks, put them all in one ecosystem. Call it the Amazon marketplace, call it the Amazon ecosystem, that's 5G. It's going to be tremendous future. >> What does the future look like? We're going to, we just determined we're going to be orchestrating the network through human language, okay? (group laughs) But seriously, what's your vision for the future here? You know, both connectivity and cloud are on on a continuum. It's, they've been on a continuum forever. They're going to continue to be on a continuum. That being said, those continuums are coming together, right? They're coming together to bring greater value to a greater set of customers, and frankly all of us. So, you know, the future is now like, you know, this conference is the future, and if you look at what's going on, it's about the acceleration of the future, right? What we announced this week is really the acceleration of listening to customers for the last handful of years. And, we're going to continue to do that. We're going to continue to bring greater value in the form of solutions. And that's what I want to pick up on from the prior question. It's not about the network, it's not about the cloud, it's about the solutions that we can provide the customers where they are, right? And if they're on their mobile phone or they're in their factory floor, you know, they're looking to accelerate their business. They're looking to accelerate their value. They're looking to create greater safety for their employees. That's what we can do with these technologies. So in fact, when we came out with, you know, our announcement for integrated private wireless, right? It really was about industry solutions. It really isn't about, you know, the cloud or the network. It's about how you can leverage those technologies, that continuum, to deliver you value. >> You know, it's interesting you say that, 'cause again, when we were interviewing Adam Selipsky, everybody, you know, all journalists analysts want to know, how's Adam Selipsky going to be different from Andy Jassy, what's the, what's he going to do to Amazon to change? And he said, listen, the real answer is Amazon has changed. If Andy Jassy were here, we'd be doing all, you know, pretty much the same things. Your point about 17 years ago, the cloud was S3, right, and EC2. Now it's got to evolve to be solutions. 'Cause if that's all you're selling, is the bespoke services, then you know, the future is not as bright as the past has been. And so I think it's key to look for what are those outcomes or solutions that customers require and how you're going to meet 'em. And there's a lot of challenges. >> You continue to build value on the value that you've brought, and you don't lose sight of why that value is important. You carry that value proposition up the stack, but the- what you're delivering, as you said, becomes maybe a bigger or or different. >> And you are getting more solution oriented. I mean, you're not hardcore solutions yet, but we're seeing more and more of that. And that seems to be a trend. We've even seen in the database world, making things easier, connecting things. Not really an abstraction layer, which is sort of antithetical to your philosophy, but it creates a similar outcome in terms of simplicity. Yeah, you're smiling 'cause you guys always have a different angle, you know? >> Yeah, we've had this conversation. >> It's right, it's, Jassy used to say it's okay to be misunderstood. >> That's Right. For a long time. >> Yeah, right, guys, thanks so much for coming to theCUBE. I'm so glad we could make this happen. >> It's always good. Thank you. >> Thank you so much. >> All right, Dave Nicholson, for Lisa Martin, Dave Vellante, John Furrier in the Palo Alto studio. We're here at the Fira, wrapping out MWC23. Keep it right there, thanks for watching. (upbeat music)

>> Narrator: theCUBE's live coverage is made possible by funding from Dell Technologies, creating technologies that drive human progress. (upbeat music) >> Welcome back to the Fira in Barcelona. This is Dave Vellante with David Nicholson. Lisa Martin is also here. This is day two of our coverage of MWC 23 on theCUBE. We're super excited. We're in between hall four and five. Stop by if you're here. Dennis Hoffman is here. He's the senior vice president and general manager of the Telecom systems business at Dell Technologies, and he's joined by Yousef Khalidi, who's the corporate vice president of Azure for Operators from Microsoft. Gents, Welcome. >> Thanks, Dave. >> Thank you. >> So we saw Satya in the keynote. He wired in. We saw T.K. came in. No AWS. I don't know. They're maybe not part of the show, but maybe next year they'll figure it out. >> Indeed, indeed. >> Lots of stuff happened in the Telecom, but the Azure operator distributed service is the big news, you guys got here. What's that all about? >> Oh, first of all, we changed the name. >> Oh, you did? >> You did? >> Oh, yeah. We have a real name now. It's called the Azure Operator Nexus. >> Oh, I like Nexus better than that. >> David: That's much better, much better. >> Dave: The engineers named it first time around. >> I wish, long story, but thank you for our marketing team. But seriously, not only did we rename the platform, we expanded the platform. >> Dave: Yeah. >> So it now covers the whole spectrum from the far-edge to the public cloud as well, including the near-edge as well. So essentially, it's a hybrid platform that can also run network functions. So all these operators around you, they now have a platform which combines cloud technologies with the choice where they want to run, optimized for the network. >> Okay and so, you know, we've talked about the disaggregation of the network and how you're bringing kind of engineered systems to the table. We've seen this movie before, but Dennis, there are differences, right? I mean, you didn't really have engineered systems in the 90s. You didn't have those integration points. You really didn't have the public cloud, you didn't have AI. >> Right. >> So you have all those new powers that you can tap, so give us the update from your perspective, having now spent a day and a half here. What's the vibe, what's the buzz, and what's your take on everything? >> Yeah, I think to build on what Yousef said, there's a lot going on with people still trying to figure out exactly how to architect the Telecom network of the future. They know it's got to have a lot to do with cloud. It does have some pretty significant differences, one of those being, there's definitely got to be a hybrid component because there are pieces of the Telecom network that even when modernized will not end up centralized, right? They're going to be highly distributed. I would say though, you know, we took away two things, yesterday, from all the meetings. One, people are done, I think the network operators are done, questioning technology readiness. They're now beginning to wrestle with operationalization of it all, right? So it's like, okay, it's here. I can in fact build a modern network in a very cloud native way, but I've got to figure out how to do that all. And another big part of it is the ecosystem and certainly the partnership long standing between Dell and Microsoft which we're extending into this space is part of that, making it easier on people to actually acquire, deploy, and importantly, support these new technologies. >> So a lot of the traditional carriers, like you said, they're sort of beyond the technology readiness. Jose Maria Alvarez in the keynote said there are three pillars to the future Telecom network. He said low latency, programmable networks, and then cloud and edge, kind of threw that in. You agree with that, Yousef? (Dave and Yousef speaking altogether) >> I mean, we've been for years talking about the cloud and edge. >> Yeah. >> Satya for years had the same graphic. We still have it. Today, we have expanded the graphic a bit to include the network as one, because you can have a cloud without connectivity as well but this is very, very, very, very much true. >> And so the question then, Dennis, is okay, you've got disruptors, we had Dish on yesterday. >> Oh, did you? Good. >> Yeah, yeah, and they're talking about what they're doing with, you know, ORAN and all the applications, really taking account of it. What I see is a developer friendly, you know, environment. You got the carriers talking about how they're going to charge developers for APIs. I think they've published eight APIs which is nowhere near enough. So you've got that sort of, you know, inertia and yet, you have the disruptors that are going to potentially be a catalyst to, you know, cross the chasm, if you will. So, you know, put on your strategy hat. >> Yeah. >> Dave: How do you see that playing out? >> Well, they're trying to tap into three things, the disruptors. You know, I think the thesis is, "If I get to a truly cloud native, communications network first, I ought to have greater agility so that I can launch more services and create more revenue streams. I ought to be lower cost in terms of both acquisition cost and operating cost, right, and I ought to be able to create scale between my IT organization, everything I know how to do there and my Telecom network." You know, classic, right? Better, faster, cheaper if I embrace cloud early on. And people like Dish, you know, they have a clean sheet of paper with which to do that. So innovation and rate of innovation is huge for them. >> So what would you do? We put your Clay Christensen hat on, now. What if you were at a traditional Telco who's like, complaining about- >> You're going to get me in trouble. >> Dave: Come on, come on. >> Don't do it. >> Dave: Help him out. Help him out, help him out. So if, you know, they're complaining about CapEx, they're highly regulated, right, they want net neutrality but they want to be able to sort of dial up the cost of those using the network. So what would you do? Would you try to disrupt yourself? Would you create a skunkworks? Would you kind of spin off a disruptor? That's a real dilemma for those guys. >> Well for mobile network operators, the beauty of 5G is it's the first cloud native cellular standard. So I don't know if anybody's throwing these terms around, but 5G SA is standalone, right? >> Dave: Yeah, yeah. >> So a lot of 'em, it's not a skunkworks. They're just literally saying, "I've got to have a 5G network." And some of 'em are deciding, "I'm going to stand it up all by itself." Now, that's duplicative expense in a lot of ways, but it creates isolation from the two networks. Others are saying, "No, it's got to be NSA. I've got to be able to combine 4G and 5G." And then you're into the brownfield thing. >> That's the hybrid. >> Not hybrid as in cloud, but hybrid as in, you know. >> Yeah, yeah. >> It's a converge network. >> Dave: Yeah, yeah. >> So, you know, I would say for a lot of them, they're adopting, probably rightly so, a wait and see attitude. One thing we haven't talked about and you got to get on the table, their high order bit is resilience. >> Dave: Yeah, totally. >> David: Yeah. >> Right? Can't go down. It's national, secure infrastructure, first responder. >> Indeed. >> Anytime you ask them to embrace any new technology, the first thing that they have to work through in their minds is, you know, "Is the juice worth the squeeze? Like, can I handle the risk?" >> But you're saying they're not questioning the technology. Aren't they questioning ORAN in terms of the quality of service, or are they beyond that? >> Dennis: They're questioning the timing, not the inevitability. >> Okay, so they agree that ORAN is going to be open over time. >> At some point, RAN will be cloud native, whether it's ORAN the spec, open RAN the concept, (Yousef speaking indistinctly) >> Yeah. >> Virtual RAN. But yeah, I mean I think it seems pretty evident at this point that the mainframe will give way to open systems once again. >> Dave: Yeah, yeah, yeah. >> ERAN, ecosystem RAN. >> Any RAN. (Dave laughing) >> You don't have to start with the ORAN where they're inside the house. So as you probably know, our partner AT&T started with the core. >> Dennis: They almost all have. >> And they've been on the virtualization path since 2014 and 15. And what we are working with them on is the hybrid cloud model to expand all the way, if you will, as I mentioned to the far-edge or the public cloud. So there's a way to be in the brownfield environment, yet jump on the new bandwagon of technology without necessarily taking too much risk, because you're quite right. I mean, resiliency, security, service assurance, I mean, for example, AT&T runs the first responder network for the US on their network, on our platform, and I'm personally very familiar of how high the bar is. So it's doable, but you need to go in stages, of course. >> And they've got to do that integration. >> Yes. >> They do. >> And Yousef made a great point. Like, out of the top 30 largest Telcos by CapEx outside of China, three quarters of them have virtualized their core. So the cloudification, if you will, software definition run on industry standard hardware, embraced cloud native principles, containerized apps, that's happened in the core. It's well accepted. Now it's just a ripple-down through the network which will happen as and when things are faster, better, cheaper. >> Right. >> So as implemented, what does this look like? Is it essentially what we used to loosely refer to as Azure stacked software, running with Dell optimized Telecom infrastructure together, sometimes within a BBU, out in a hybrid cloud model communicating back to Azure locations in some cases? Is that what we're looking at? >> Approximately. So you start with the near-edge, okay? So the near-edge lives in the operator's data centers, edges, whatever the case may be, built out of off the shelf hardware. Dell is our great partner there but in principle, it could be different mix and match. So once you have that true near-edge, then you can think of, "Okay, how can I make sure this environment is as uniform, same APIs, same everything, regardless what the physical location is?" And this is key, key for the network function providers and the NEPs because they need to be able to port once, run everywhere, and it's key for the operator to reduce their costs. You want to teach your workforce, your operations folks, if you will, how to manage this system one time, to automation and so forth. So, and that is actually an expansion of the Azure capabilities that people are familiar with in a public cloud, projected into different locations. And we have technology called Arc which basically models everything. >> Yeah, yeah. >> So if you have trained your IT side, you are halfway there, how to manage your new network. Even though of course the network is carrier graded, there's different gear. So yes, what you said, a lot of it is true but the actual components, whatever they might be running, are carrier grade, highly optimized, the next images and our solution is not a DIY solution, okay? I know you cater to a wide spectrum here but for us, we don't believe in the TCO. The proper TCO can be achieved by just putting stuff by yourself. We just published a report with Analysys Mason that shows that our approach will save 36 percent of the cost compared to a DIY approach. >> Dave: What percent? >> 36 percent. >> Dave: Of the cost? >> Of, compared to DIY, which is already cheaper than classical models. >> And there's a long history of fairly failed DIY, right, >> Yeah. >> That preceded this. As in the early days of public cloud, the network operators wrestled with, "Do I have to become one to survive?" >> Dave: Yeah. Right. >> So they all ended up having cloud projects and by and large, they've all dematerialized in favor of this. >> Yeah, and it's hard for them to really invest at scale. Let me give you an example. So, your biggest tier one operator, without naming anybody, okay, how many developers do they have that can build and maintain an OS image, or can keep track of container technology, or build monitoring at scale? In our company, we have literally thousands of developers doing it already for the cloud and all we're doing for the operator segment is customizing it and focusing it at the carrier grade aspects of it. But so, I don't have half a dozen exterior experts. I literally have a building of developers who can do that and I'm being literal, here. So it's a scale thing. Once you have a product that you can give to multiple people, everybody benefits. >> Dave: Yeah, and the carriers are largely, they're equipment engineers in a large setting. >> Oh, they have a tough job. I always have total respect what they do. >> Oh totally, and a lot of the work happens, you know, kind of underground and here they are. >> They are network operators. >> They don't touch. >> It's their business. >> Right, absolutely, and they're good at it. They're really good at it. That's right. You know, you think about it, we love to, you know, poke fun at the big carriers, but think about what happened during the pandemic. When they had us shift everything to remote work, >> Dennis: Yes. >> Landline traffic went through the roof. You didn't even notice. >> Yep. That's very true. >> I mean, that's the example. >> That's very true. >> However, in the future where there's innovation and it's going to be driven by developers, right, that's where the open ecosystem comes in. >> Yousef: Indeed. >> And that's the hard transition for a lot of these folks because the developers are going to win that with new workloads, new applications that we can't even think of. >> Dennis: Right. And a lot of it is because if you look at it, there's the fundamental back strategy hat back on, fundamental dynamics of the industry, forced investment, flat revenues. >> Dave: Yeah. Right. >> Very true. >> Right? Every few years, a new G comes out. "Man, I got to retool this massive thing and where I can't do towers, I'm dropping fiber or vice a versa." And meanwhile, most diversification efforts into media have failed. They've had to unwind them and resell them. There's a lot of debt in the industry. >> Yousef: Yeah. >> Dennis: And so, they're looking for that next big, adjacent revenue stream and increasingly deciding, "If I don't modernize my network, I can't get it." >> Can't do it. >> Right, and again, what I heard from some of the carriers in the keynote was, "We're going to charge for API access 'cause we have data in the network." Okay, but I feel like there's a lot more innovation beyond that that's going to come from the disruptors. >> Dennis: Oh yeah. >> Yousef: Yes. >> You know, that's going to blow that away, right? And then that may not be the right model. We'll see, you know? I mean, what would Microsoft do? They would say, "Here, here's a platform. Go develop." >> No, I'll tell you. We are actually working with CAMARA and GSMA on the whole API layer. We actually announced a service as well as (indistinct). >> Dave: Yeah, yeah, right. >> And the key there, frankly, in my opinion, are not the disruptors as in operators. It's the ISV community. You want to get developers that can write to a global set of APIs, not per Telco APIs, such that they can do the innovation. I mean, this is what we've seen in other industries, >> Absolutely. >> That I critically can think of. >> This is the way they get a slice of that pie, right? The recent history of this industry is one where 4G LTE begot the smartphone and app store era, a bevy of consumer services, and almost every single profit stream went somewhere other than the operator, right? >> Yousef: Someone else. So they're looking at this saying, "Okay, 5G is the enterprise G and there's going to be a bevy of applications that are business service related, based on 5G capability and I can't let the OTT, over the top, thing happen again." >> Right. >> They'll say that. "We cannot let this happen." >> "We can't let this happen again." >> Okay, but how do they, >> Yeah, how do they make that not happen? >> Not let it happen again? >> Eight APIs, Dave. The answer is eight APIs. No, I mean, it's this approach. They need to make it easy to work with people like Yousef and more importantly, the developer community that people like Yousef and his company have found a way to harness. And by the way, they need to be part of that developer community themselves. >> And they're not, today. They're not speaking that developer language. >> Right. >> It's hard. You know, hey. >> Dennis: Hey, what's the fastest way to sell an enterprise, a business service? Resell Azure, Teams, something, right? But that's a resale. >> Yeah, that's a resale thing. >> See, >> That's not their service. >> They also need to free their resources from all the plumbing they do and leave it to us. We are plumbers, okay? >> Dennis: We are proud plumbers. >> We are proud plumbers. I'm a plumber. I keep telling people this thing. We had the same discussion with banks and enterprises 10 years ago, by the way. Don't do the plumbing. Go add value on the top. Retool your workforce to do applications and work with ISVs to the verticals, as opposed to either reselling, which many do, or do the plumbing. You'd be surprised. Traditionally, many operators do around, "I want to plumb this thing to get this small interrupt per second." Like, who cares? >> Well, 'cause they made money on connectivity. >> Yes. >> And we've seen this before. >> And in a world without telephone poles and your cables- >> Hey, if what you have is a hammer, everything's a nail, right? And we sell connectivity services and that's what we know how to do, and that both build and sell. And if that's no longer driving a revenue stream sufficient to cover this forced investment march, not to mention Huawei rip and government initiatives to pull infrastructure out and accelerate investment, they got to find new ways. >> I mean, the regulations have been tough, right? They don't go forward and ask for permission. They really can't, right? They have to be much more careful. >> Dennis: It is tough. >> So, we don't mean to sound like it's easy for these guys. >> Dennis: No, it's not. >> But it does require a new mindset, new skillsets, and I think some of 'em are going to figure it out and then pff, the wave, and you guys are going to be riding that wave. >> We're going to try. >> Definitely. Definitely. >> As a veteran of working with both Dell and Microsoft, specifically Azure on things, I am struck by how you're very well positioned in this with Microsoft in particular. Because of Azure's history, coming out of the on-premises world that Microsoft knows so well, there's a natural affinity to the hybrid nature of Telecom. We talk about edge, we talk about hybrid, this is it, absolutely the center of it. So it seems like a- >> Yousef: Indeed. Actually, if you look at the history of Azure, from day one, and I was there from day one, we always spoke of the hybrid model. >> Yeah. >> The third point, we came from the on-premises world. >> David: Right. >> And don't get me wrong, I want people to use the public cloud, but I also know due to physics, regulation, geopolitical boundaries, there's something called on-prem, something called an edge here. I want to add something else. Remember our deal on how we are partner-centric? We're applying the same playbook, here. So, you know, for every dollar we make, so many of it's been done by the ecosystem. Same applies here. So we have announced partnerships with Ericson, Nokia, (indistinct), all the names, and of course with Dell and many others. The ecosystem has to come together and customers must retain their optionality to drum up whatever they are on. So it's the same playbook, with this. >> And enterprise technology companies are, actually, really good at, you know, decoding the customer, figuring out specific requirements, making some mistakes the first time through and then eventually getting it right. And as these trends unfold, you know, you're in a good position, I think, as are others and it's an exciting time for enterprise tech in this industry, you know? >> It really is. >> Indeed. >> Dave: Guys, thanks so much for coming on. >> Thank you. >> Dave: It's great to see you. Have a great rest of the show. >> Thank you. >> Thanks, Dave. Thank you, Dave. >> All right, keep it right there. John Furrier is live in our studio. He's breaking down all the news. Go to siliconangle.com to go to theCUBE.net. Dave Vellante, David Nicholson and Lisa Martin, we'll be right back from the theater in Barcelona, MWC 23 right after this short break. (relaxing music)

(gentle music) >> Announcer: "theCube's" live coverage is made possible by funding from Dell Technologies, creating technologies that drive human progress. (upbeat music) (logo whooshing) >> Hey, everyone, welcome back to "theCube's" coverage of day one, MWC23 live from Barcelona, Lisa Martin here with Dave Vellante. Dave, we've got some great conversations so far This is the biggest, most packed show I've been to in years. About 80,000 people here so far. >> Yeah, down from its peak of 108, but still pretty good. You know, a lot of folks from China come to this show, but with the COVID situation in China, that's impacted the attendance, but still quite amazing. >> Amazing for sure. We're going to be talking about trends and mobility, and all sorts of great things. We have a couple of guests joining us for the first time on "theCUBE." Please welcome Dr. Srinivas Mukkamala or Sri, chief product officer at Ivanti. And Dave Shepherd, VP Ivanti. Guys, welcome to "theCUBE." Great to have you here. >> Thank you. >> So, day one of the conference, Sri, we'll go to you first. Talk about some of the trends that you're seeing in mobility. Obviously, the conference renamed from Mobile World Congress to MWC mobility being part of it, but what are some of the big trends? >> It's interesting, right? I mean, I was catching up with Dave. The first thing is from the keynotes, it took 45 minutes to talk about security. I mean, it's quite interesting when you look at the shore floor. We're talking about Edge, we're talking about 5G, the whole evolution. And there's also the concept of are we going into the Cloud? Are we coming back from the Cloud, back to the Edge? They're really two different things. Edge is all decentralized while you recompute. And one thing I observed here is they're talking about near real-time reality. When you look at automobiles, when you look at medical, when you look at robotics, you can't have things processed in the Cloud. It'll be too late. Because you got to make millisecond-based stations. That's a big trend for me. When I look at staff... Okay, the compute it takes to process in the Cloud versus what needs to happen on-prem, on device, is going to revolutionize the way we think about mobility. >> Revolutionize. David, what are some of the things that you're saying? Do you concur? >> Yeah, 100%. I mean, look, just reading some of the press recently, they're predicting 22 billion IoT devices by 2024. Everything Sri just talked about there. It's growing exponentially. You know, problems we have today are a snapshot. We're probably in the slowest place we are today. Everything's just going to get faster and faster and faster. So it's a, yeah, 100% concur with that. >> You know, Sri, on your point, so Jose Maria Alvarez, the CEO of Telefonica, said there are three pillars of the future of telco, low latency, programmable networks, and Cloud and Edge. So, as to your point, Cloud and low latency haven't gone hand in hand. But the Cloud guys are saying, "All right, we're going to bring the Cloud to the Edge." That's sort of an interesting dynamic. We're going to bypass them. We heard somebody, another speaker say, "You know, Cloud can't do it alone." You know? (chuckles) And so, it's like these worlds need each other in a way, don't they? >> Definitely right. So that's a fantastic way to look at it. The Cloud guys can say, "We're going to come closer to where the computer is." And if you really take a look at it with data localization, where are we going to put the Cloud in, right? I mean, so the data sovereignty becomes a very interesting thing. The localization becomes a very interesting thing. And when it comes to security, it gets completely different. I mean, we talked about moving everything to a centralized compute, really have massive processing, and give you the addition back wherever you are. Whereas when you're localized, I have to process everything within the local environment. So there's already a conflict right there. How are we going to address that? >> Yeah. So another statement, I think, it was the CEO of Ericsson, he was kind of talking about how the OTT guys have heard, "We can't let that happen again. And we're going to find new ways to charge for the network." Basically, he's talking about monetizing the API access. But I'm interested in what you're hearing from customers, right? 'Cause our mindset is, what value you're going to give to customers that they're going to pay for, versus, "I got this data I'm going to charge developers for." But what are you hearing from customers? >> It's amazing, Dave, the way you're looking at it, right? So if we take a look at what we were used to perpetual, and we said we're going to move to a subscription, right? I mean, everybody talks about subscription economy. Telcos on the other hand, had subscription economy for a long time, right? They were always based on usage, right? It's a usage economy. But today, we are basically realizing on compute. We haven't even started charging for compute. If you go to AWS, go to Azure, go to GCP, they still don't quite charge you for actual compute, right? It's kind of, they're still leaning on it. So think about API-based, we're going to break the bank. What people don't realize is, we do millions of API calls for any high transaction environment. A consumer can't afford that. What people don't realize is... I don't know how you're going to monetize. Even if you charge a cent a call, that is still going to be hundreds and thousands of dollars a day. And that's where, if you look at what you call low-code no-code motion? You see a plethora of companies being built on that. They're saying, "Hey, you don't have to write code. I'll give you authentication as a service. What that means is, Every single time you call my API to authenticate a user, I'm going to charge you." So just imagine how many times we authenticate on a single day. You're talking a few dozen times. And if I have to pay every single time I authenticate... >> Real friction in the marketplace, David. >> Yeah, and I tell you what. It's a big topic, right? And it's a topic that we haven't had to deal with at the Edge before, and we hear it probably daily really, complexity. The complexity's growing all the time. That means that we need to start to get insight, visibility. You know? I think a part of... Something that came out of the EU actually this week, stated, you know, there's a cyber attack every 11 seconds. That's fast, right? 2016, that was 40 seconds. So actually that speed I talked about earlier, everything Sri says that's coming down to the Edge, we want to embrace the Edge and that is the way we're going to move. But customers are mindful of the complexity that's involved in that. And that, you know, lens thought to how are we going to deal with those complexities. >> I was just going to ask you, how are you planning to deal with those complexities? You mentioned one ransomware attack every 11 seconds. That's down considerably from just a few years ago. Ransomware is a household word. It's no longer, "Are we going to get attacked?" It's when, it's to what extent, it's how much. So how is Ivanti helping customers deal with some of the complexities, and the changes in the security landscape? >> Yeah. Shall I start on that one first? Yeah, look, we want to give all our customers and perspective customers full visibility of their environment. You know, devices that are attached to the environment. Where are they? What are they doing? How often are we going to look for those devices? Not only when we find those devices. What applications are they running? Are those applications secure? How are we going to manage those applications moving forward? And overall, wrapping it round, what kind of service are we going to do? What processes are we going to put in place? To Sri's point, the low-code no-code angle. How do we build processes that protect our organization? But probably a point where I'll pass to Sri in a moment is how do we add a level of automation to that? How do we add a level of intelligence that doesn't always require a human to be fixing or remediating a problem? >> To Sri, you mentioned... You're right, the keynote, it took 45 minutes before it even mentioned security. And I suppose it's because they've historically, had this hardened stack. Everything's controlled and it's a safe environment. And now that's changing. So what would you add? >> You know, great point, right? If you look at telcos, they're used to a perimeter-based network. >> Yep. >> I mean, that's what we are. Boxed, we knew our perimeter. Today, our perimeter is extended to our home, everywhere work, right? >> Yeah- >> We don't have a definition of a perimeter. Your browser is the new perimeter. And a good example, segueing to that, what we have seen is horizontal-based security. What we haven't seen is verticalization, especially in mobile. We haven't seen vertical mobile security solutions, right? Yes, you hear a little bit about automobile, you hear a little bit about healthcare, but what we haven't seen is, what about food sector? What about the frontline in food? What about supply chain? What security are we really doing? And I'll give you a simple example. You brought up ransomware. Last night, Dole was attacked with ransomware. We have seen the beef producer colonial pipeline. Now, if we have seen agritech being hit, what does it mean? We are starting to hit humanity. If you can't really put food on the table, you're starting to really disrupt the supply chain, right? In a massive way. So you got to start thinking about that. Why is Dole related to mobility? Think about that. They don't carry service and computers. What they carry is mobile devices. that's where the supply chain works. And then that's where you have to start thinking about it. And the evolution of ransomware, rather than a single-trick pony, you see them using multiple vulnerabilities. And Pegasus was the best example. Spyware across all politicians, right? And CEOs. It is six or seven vulnerabilities put together that actually was constructed to do an attack. >> Yeah. How does AI kind of change this? Where does it fit in? The attackers are going to have AI, but we could use AI to defend. But attackers are always ahead, right? (chuckles) So what's your... Do you have a point of view on that? 'Cause everybody's crazy about ChatGPT, right? The banks have all banned it. Certain universities in the United States have banned it. Another one's forcing his students to learn how to use ChatGPT to prompt it. It's all over the place. You have a point of view on this? >> So definitely, Dave, it's a great point. First, we all have to have our own generative AI. I mean, I look at it as your digital assistant, right? So when you had calculators, you can't function without a calculator today. It's not harmful. It's not going to take you away from doing multiplication, right? So we'll still teach arithmetic in school. You'll still use your calculator. So to me, AI will become an integral part. That's one beautiful thing I've seen on the short floor. Every little thing there is a AI-based solution I've seen, right? So ChatGPT is well played from multiple perspective. I would rather up level it and say, generated AI is the way to go. So there are three things. There is human intense triaging, where humans keep doing easy work, minimal work. You can use ML and AI to do that. There is human designing that you need to do. That's when you need to use AI. >> But, I would say this, in the Enterprise, that the quality of the AI has to be better than what we've seen so far out of ChatGPT, even though I love ChatGPT, it's amazing. But what we've seen from being... It's got to be... Is it true that... Don't you think it has to be cleaner, more accurate? It can't make up stuff. If I'm going to be automating my network with AI. >> I'll answer that question. It comes down to three fundamentals. The reason ChatGPT is giving addresses, it's not trained on the latest data. So for any AI and ML method, you got to look at three things. It's your data, it's your domain expertise, who is training it, and your data model. In ChatGPT, it's older data, it's biased to the people that trained it, right? >> Mm-hmm. >> And then, the data model is it's going to spit out what it's trained on. That's a precursor of any GPT, right? It's pre-trained transformation. >> So if we narrow that, right? Train it better for the specific use case, that AI has huge potential. >> You flip that to what the Enterprise customers talk about to us is, insight is invaluable. >> Right. >> But then too much insight too quickly all the time means we go remediation crazy. So we haven't got enough humans to be fixing all the problems. Sri's point with the ChatGPT data, some of that data we are looking at there could be old. So we're trying to triage something that may still be an issue, but it might have been superseded by something else as well. So that's my overriding when I'm talking to customers and we talk ChatGPT, it's in the news all the time. It's very topical. >> It's fun. >> It is. I even said to my 13-year-old son yesterday, your homework's out a date. 'Cause I knew he was doing some summary stuff on ChatGPT. So a little wind up that's out of date just to make that emphasis around the model. And that's where we, with our Neurons platform Ivanti, that's what we want to give the customers all the time, which is the real-time snapshot. So they can make a priority or a decision based on what that information is telling them. >> And we've kind of learned, I think, over the last couple of years, that access to real-time data, real-time AI, is no longer nice to have. It's a massive competitive advantage for organizations, but it's going to enable the on-demand, everything that we expect in our consumer lives, in our business lives. This is going to be table stakes for organizations, I think, in every industry going forward. >> Yeah. >> But assumes 5G, right? Is going to actually happen and somebody's going to- >> Going to absolutely. >> Somebody's going to make some money off it at some point. When are they going to make money off of 5G, do you think? (all laughing) >> No. And then you asked a very good question, Dave. I want to answer that question. Will bad guys use AI? >> Yeah. Yeah. >> Offensive AI is a very big thing. We have to pay attention to it. It's got to create an asymmetric war. If you look at the president of the United States, he said, "If somebody's going to attack us on cyber, we are going to retaliate." For the first time, US is willing to launch a cyber war. What that really means is, we're going to use AI for offensive reasons as well. And we as citizens have to pay attention to that. And that's where I'm worried about, right? AI bias, whether it's data, or domain expertise, or algorithmic bias, is going to be a big thing. And offensive AI is something everybody have to pay attention to. >> To your point, Sri, earlier about critical infrastructure getting hacked, I had this conversation with Dr. Robert Gates several years ago, and I said, "Yeah, but don't we have the best offensive, you know, technology in cyber?" And he said, "Yeah, but we got the most to lose too." >> Yeah, 100%. >> We're the wealthiest nation of the United States. The wealthiest is. So you got to be careful. But to your point, the president of the United States saying, "We'll retaliate," right? Not necessarily start the war, but who started it? >> But that's the thing, right? Attribution is the hardest part. And then you talked about a very interesting thing, rich nations, right? There's emerging nations. There are nations left behind. One thing I've seen on the show floor today is, digital inequality. Digital poverty is a big thing. While we have this amazing technology, 90% of the world doesn't have access to this. >> Right. >> What we have done is we have created an inequality across, and especially in mobility and cyber, if this technology doesn't reach to the last mile, which is emerging nations, I think we are creating a crater back again and putting societies a few miles back. >> And at much greater risk. >> 100%, right? >> Yeah. >> Because those are the guys. In cyber, all you need is a laptop and a brain to attack. >> Yeah. Yeah. >> If I don't have it, that's where the civil war is going to start again. >> Yeah. What are some of the things in our last minute or so, guys, David, we'll start with you and then Sri go to you, that you're looking forward to at this MWC? The theme is velocity. We're talking about so much transformation and evolution in the telecom industry. What are you excited to hear and learn in the next couple of days? >> Just getting a complete picture. One is actually being out after the last couple of years, so you learn a lot. But just walking around and seeing, from my perspective, some vendor names that I haven't seen before, but seeing what they're doing and bringing to the market. But I think goes back to the point made earlier around APIs and integration. Everybody's talking about how can we kind of do this together in a way. So integrations, those smart things is what I'm kind of looking for as well, and how we plug into that as well. >> Excellent, and Sri? >> So for us, there is a lot to offer, right? So while I'm enjoying what I'm seeing here, I'm seeing at an opportunity. We have an amazing portfolio of what we can do. We are into mobile device management. We are the last (indistinct) company. When people find problems, somebody has to go remediators. We are the world's largest patch management company. And what I'm finding is, yes, all these people are embedding software, pumping it like nobody's business. As you find one ability, somebody has to go fix them, and we want to be the (indistinct) company. We had the last smile. And I find an amazing opportunity, not only we can do device management, but do mobile threat defense and give them a risk prioritization on what needs to be remediated, and manage all that in our ITSM. So I look at this as an amazing, amazing opportunity. >> Right. >> Which is exponential than what I've seen before. >> So last question then. Speaking of opportunities, Sri, for you, what are some of the things that customers can go to? Obviously, you guys talk to customers all the time. In terms of learning what Ivanti is going to enable them to do, to take advantage of these opportunities. Any webinars, any events coming up that we want people to know about? >> Absolutely, ivanti.com is the best place to go because we keep everything there. Of course, "theCUBE" interview. >> Of course. >> You should definitely watch that. (all laughing) No. So we have quite a few industry events we do. And especially there's a lot of learning. And we just raised the ransomware report that actually talks about ransomware from a global index perspective. So one thing what we have done is, rather than just looking at vulnerabilities, we showed them the weaknesses that led to the vulnerabilities, and how attackers are using them. And we even talked about DHS, how behind they are in disseminating the information and how it's actually being used by nation states. >> Wow. >> And we did cover mobility as a part of that as well. So there's a quite a bit we did in our report and it actually came out very well. >> I have to check that out. Ransomware is such a fascinating topic. Guys, thank you so much for joining Dave and me on the program today, sharing what's going on at Ivanti, the changes that you're seeing in mobile, and the opportunities that are there for your customers. We appreciate your time. >> Thank you >> Thank you. >> Yes. Thanks, guys. >> Thanks, guys. >> For our guests and for Dave Vellante, I'm Lisa Martin. You're watching "theCUBE" live from MWC23 in Barcelona. As you know, "theCUBE" is the leader in live tech coverage. Dave and I will be right back with our next guest. (gentle upbeat music)

>>Well, hello everybody at John Wallace here on the Cube, and glad to have you along here for day two of our coverage here at AWS Reinvent 22. We're up in the global startup program, which is part of AWS's Startup Showcase, and I've got Kevin Farley with me. He is the director of Strategic Alliances with Maria Day db. And Kevin, good to see you this morning. Good to see you, John. Thanks for joining us. Thank >>You. >>Appreciate it. Yeah. First off, tell us about Maria db. Sure. Obviously data's your thing. Yep. But to share that with some folks at home who might not be familiar with your offering. >>Yeah. So Maria DB's been around as a corporate entity for 10 plus years, and we have a massive customer base. You know, there's a billion downloads from Docker Hub, 75% of the Fortune 500. We have an enormous sea of really happy users. But what we realize is that all of these users are really thinking about what do we, what does it mean to transform it? What does cloud modernization mean? And how do we build a strategy on something we really love to drive it into the cloud and take it to the future. So what we launched about two years ago, two and a half years ago, is Skye. It's our database as a service. It leverages all the best elements, what we provide on the enterprise platform. It marries to the AWS cloud, and it really provides the best of both worlds for our >>Customers. So in your thought then, what, what problem is that solving? >>I think what you see in the overall database market is that many people have been using what we would call legacy technology. There's been lots of sort of stratification and mixes of different database solutions. All of them come with some promise, and all of 'em come with a lot of compromise. So I think what the market is really looking for is something that can take what they know and love, can bring it to the cloud and can survive the port drive the performance and scale. That completely changes the landscape, especially as you think about what modern data needs look like, right? What people did 10 years ago with the exponential scale of data no longer works. And what they need is something that not only can really deliver against their core business values and their core business deliverables, but gets 'em to the future. How do we drive something new? How do we innovate? How do we change the game? And I think what we built with AWS really delivers what we call cloud scale. It's taking something that is the best technology, and I as a V can build, marrying it to, you know, Kubernetes layer, marrying it to global availability, thinking about having true global high availability across all of your environments and really delivering that to customers through an integrated partnership. >>Could we see this coming? I mean, because you know data, right? I mean, yeah, we, we, everybody talked about the tsunami of growth, you know, >>Back 10 >>Sure. 11 years ago. But, but maybe the headlights didn't go far enough or, or, but, but you could see that there was going to be crunch time. >>There's no doubt. And I think that this has been a, there's, there's been these sort of pocket solutions, right? So if you think at the entire no sequel world, right? People said, oh, I need scale, I can get it, but what do I have to give up asset compliance? So I have to change the way I think about what data is and how I, I can govern it. So there's been these things that deliver on half the promise, but there's never been something that comes together and really drives what we deliver through CIQ is something called expand. So distributed SQL really tied to the SQL Query language, having that asset data. So having everything you need without the compromise built on the cloud allows you to scale out and allows you to think about, I can actually do exponential layers of, of data, data modeling, data querying, complete read, write, driving that forward. And I think it gives us a whole nother dynamic that we can deliver on in a way that hasn't been before. And I think that's kind of the holy grail of what people are looking for is how am I building modern applications and how do I have a database in the cloud that's really gonna support >>It? You know, you talk about distributed, you know, sequel and, and I mean, there's a little mystery behind it, isn't there? Or at least maybe not mystery. There's a little, I guess, confusion or, or just misunderstanding. I mean, I, how, nail that down a little bit. I >>Would say the best way to say it, honestly, this is the great thing, is it people believe it's too good to be true. And I think what we see over and over >>Again, you know, what they say about that. >>But this is the great part is, you know, you know, we've just had two taste studies recently with aws, with HIT labs and Certified power, both on expand, both proof in the pudding. They did the POCs, they're like, oh my God, this works. If you watch the keynote yesterday, you know, Adam had a slide that was, you know, as big as the entire room and it highlighted Samsung and they said, you know, we're doing 80,000 requests per second. So the, you know, the story there is that AWS is able as, as an entity with their scale and their breadth to handle that kind of workload. But guess what that is? That's MariaDB expand underneath there driving all of that utilization. So it's already there, it's already married, it's already in the cloud, and now we're taking it to a completely different level with a fully managed database solution. Right? >>How impressive is that? Right? I mean, you would think that somebody out there who, I mean that that volume, that kind of capacity is, is mind blowing. >>I mean, to your kind of previous point, it's like one of those things, do I see what's coming and it's here, right? You know, it's, is it actually ever gonna be possible? And now we're showing that it really is on a daily basis for some of the biggest brands in the world. We're also seeing companies moving off not only transitioning from, you know, MariaDB or myse, but all of the big licensed, you know, conversions as well. So you think about Oracle DBS Bank is one of our biggest customers, one of the largest Oracle conversions in the world onto MariaDB. And now thinking about what is the promise of connecting that to the cloud? How do you take things that you're currently doing, OnPrem delivering a hybrid model that also then starts to say, Hey, here's my path to cloud modernization. Skye gives me that bridge. And then you take it one layer farther and you think about multi-cloud, right? That's one of the things that's critical that ISVs can really only deliver in a meaningful way, is how can we have a solution for a customer that we can take to any availability zone. We can have performance, proximity, cost, proximity. We're always able to have that total data dexterity across any environment we need and we can build on that for the future. >>So if, if we're talking about cloud database and there's so many good things going forward here. You're talking about easy use and scalability and all that. But as with ever have you talked about this, there's some push and there's some pull. Yeah. So, so what's the, what's the other side that's still, you know, you that you think has to be >>Addressed? And I think that's a great question. So there's, we see that there's poll, right? We've seen these deals, this pipeline growth, this, there's great adoption. But what I think we're still not at the point of massive hockey stick adoption is that customers still don't fully understand the capabilities distributed SQL and the power they can actually deliver. So the more we drive case studies, the more we drive POCs, the more we prove the model, I think you're gonna see just a massive adoption scale. And I also think customers are tired of doing lots of different things in lots of different pockets. So neither one of the key elements of Sky SQL is we can do both transactional and analytical data out of the same database driven by the same proxy. So what, instead of having DBAs and developers try to figure out, okay, I'm gonna pull from this database here. >>Yeah. That there, it's, it's this big spaghetti wire concept that is super expensive and super time intensive. So the ability to write modern applications and pull data from both pockets and really be able to have that as a seamless entity and deliver that to customers is massive. I mean, another part of the keynote yesterday was a new deliverable, like kind of no etl. Adam talked about Aurora and Redshift and the massive complexity of what used to exist for getting data back and forth. You also have to pay for two different databases. It's super expensive. So I think the idea that you can take the real focus of AWS and US is customer value. How do you deliver that next thing that changes the game? Always utilizes AWS delivers on that promise, but then takes a net new technology that really starts to think about how do we bring things together? How do we make it more simple? How do we make it more powerful? And how do we deliver more customer value as we go forward? >>But you know, if, if I'm, I'm still an on-prim guy, just pretend I'm not saying I am. Just pretend I just for the sake of the discussion here, it's like I just can't let it go. Yeah. Right. I, I still, you know, there's control, there's the known versus the unknown. The uncertain. Yeah. So twist my arm just a little bit more and get me over the hum. >>Well, first of all, you don't have to, right? And there's gonna be some industries and some verticals that will always have elements of their business that will be OnPrem. Guess what? We make the best based in the world. It can be MariaDB, but there's those that then say, these, these elements of our business are gonna be far more effective moving to the cloud. So we give you Skye, there's a natural symbiotic bridge between everything we do and how we deliver it. Where you can be hybrid and it's great. You can adopt the cloud as your business needs grow. And you can have multi-cloud. This is that, that idea that you can, can have your cake and eat it too, right? You can literally have all these elements of your business met without these big pressure to say, you gotta throw that away. You gotta move to this. It's really, how do you kind of gracefully adopt the cloud in a way that makes sense for your business? Where are you trying to drive your business? Is it time to value, right? Is it governance? Is it is there's different elements of what matters the most to individual businesses. You know, we wanna address those and we can address >>Those. So you're saying you don't have to dive >>In, you don't have to dive >>In. You, you can, you can go ankle deep, knee deep, whatever you wanna >>Do. Absolutely. And you know, some of the largest MariaDB users still have massive, massive on-prem implementations. And that's okay. But there's elements that are starting to fall behind. There's cost savings, there's things that they need to do in the cloud that they can't do. OnPrem. And that's where expand Skye really says, okay, here is your platform. Grow as you want to, migrate as you want to. And we're there every step along the way. We, we also provide a whole Sky DBA team. Some guys just say, I wanna get outta the database world at all. This is, this is expensive, it's costly and it's difficult to be an expert. So you can bring in our DBA team and they'll man and run, they'll, they'll run your entire environment. They'll optimize it, you know, they'll troubleshoot it, they'll bug fix, they'll do everything for you. So you can just say, I just wanna focus on building phenomenal applications for my customers. And the database game as we knew it is not something that I know I want to invest in anymore. Right. I wanna make that transition >>That makes that really, yeah. You know, I mean really attractive to a lot of people because you are, you talk about a lot of headache there. Yeah. So let's talk about AWS before Sure. I let you go just about that relationship. Okay. You've talked about the platform that it provides you and, and obviously the benefits, but just talk about how you've worked with AWS over the years Yep. And, and how you see that relationship allowing you to expand your services, no pun intended. >>For sure. So, I mean, I would start with the way we even contemplated architecture. You know, we worked with the satisfactory team. We made sure that the things that we built were optimized in their environment. You know, I think it was a lot of collaboration on how does this combined entity really make the most value for our customers? How does it make the most sense for our developers as we build it out? Then we work in the, in the global startup team. So the strategic element of who we are, not all startups are created equal, right? We have, right, we have 75% of the Fortune 100, we've got over a billion downloads. So, you know, we come in with promise. And the reason this partnership is so valuable and the reason there's so much investment going forward is cuz what really, what do the cloud guys care about? >>The very, very most, they want all of these mission critical, big workloads that are on prem to land in their cloud. What do we have a massive, massive TAM sitting out there, these customers that could go to aws. So we both see, like if we can deliver incredible value to that customer base, these big workloads will end up in aws. They'll use other AWS services. And as we scale and grow, you know, we have that platform that's already built for it. So I think that when you go back to like the tenants, the core principles of aws, the one that always stands out, the one that we always kind of lean back on is, are we delivering customer value? Is this the best thing for the customer? Because we do have some competition just like many other, other partners do, right? So there is Aurora and there is rds and there is times when that's a great service for a customer. But when people are really thinking about where do I need my database to go? Where do I really need to be set for the future growth? Where am I gonna get the kind of ROI I need going forward? That's where you can go, Hey, sky sql, expand distributed sql. This is the best game in town. It's built on aws and collectively, you know, we're gonna present that to a customer. I'm >>Sold. Done. >>I love it. Right? >>Maria db, check 'em out, they're on the show floor. Great traffic. I know at at the, at the booth. They're here at AWS Reinvent. So check 'em out. Maria db. Thanks >>Kevin. Hey, thanks John. Appreciate your >>Time. Appreciate Great. That was great. Right back with more, you're watching the cube, the leader in high tech coverage.

>>When Oracle acquired my SQL via the Sun acquisition, nobody really thought the company would put much effort into the platform preferring to focus all the wood behind its leading Oracle database, Arrow pun intended. But two years ago, Oracle surprised many folks by announcing my SQL Heatwave a new database as a service with a massively parallel hybrid Columbia in Mary Mary architecture that brings together transactional and analytic data in a single platform. Welcome to our latest database, power panel on the cube. My name is Dave Ante, and today we're gonna discuss Oracle's MySQL Heat Wave with a who's who of cloud database industry analysts. Holgar Mueller is with Constellation Research. Mark Stammer is the Dragon Slayer and Wikibon contributor. And Ron Westfall is with Fu Chim Research. Gentlemen, welcome back to the Cube. Always a pleasure to have you on. Thanks for having us. Great to be here. >>So we've had a number of of deep dive interviews on the Cube with Nip and Aggarwal. You guys know him? He's a senior vice president of MySQL, Heatwave Development at Oracle. I think you just saw him at Oracle Cloud World and he's come on to describe this is gonna, I'll call it a shock and awe feature additions to to heatwave. You know, the company's clearly putting r and d into the platform and I think at at cloud world we saw like the fifth major release since 2020 when they first announced MySQL heat wave. So just listing a few, they, they got, they taken, brought in analytics machine learning, they got autopilot for machine learning, which is automation onto the basic o l TP functionality of the database. And it's been interesting to watch Oracle's converge database strategy. We've contrasted that amongst ourselves. Love to get your thoughts on Amazon's get the right tool for the right job approach. >>Are they gonna have to change that? You know, Amazon's got the specialized databases, it's just, you know, the both companies are doing well. It just shows there are a lot of ways to, to skin a cat cuz you see some traction in the market in, in both approaches. So today we're gonna focus on the latest heat wave announcements and we're gonna talk about multi-cloud with a native MySQL heat wave implementation, which is available on aws MySQL heat wave for Azure via the Oracle Microsoft interconnect. This kind of cool hybrid action that they got going. Sometimes we call it super cloud. And then we're gonna dive into my SQL Heatwave Lake house, which allows users to process and query data across MyQ databases as heatwave databases, as well as object stores. So, and then we've got, heatwave has been announced on AWS and, and, and Azure, they're available now and Lake House I believe is in beta and I think it's coming out the second half of next year. So again, all of our guests are fresh off of Oracle Cloud world in Las Vegas. So they got the latest scoop. Guys, I'm done talking. Let's get into it. Mark, maybe you could start us off, what's your opinion of my SQL Heatwaves competitive position? When you think about what AWS is doing, you know, Google is, you know, we heard Google Cloud next recently, we heard about all their data innovations. You got, obviously Azure's got a big portfolio, snowflakes doing well in the market. What's your take? >>Well, first let's look at it from the point of view that AWS is the market leader in cloud and cloud services. They own somewhere between 30 to 50% depending on who you read of the market. And then you have Azure as number two and after that it falls off. There's gcp, Google Cloud platform, which is further way down the list and then Oracle and IBM and Alibaba. So when you look at AWS and you and Azure saying, hey, these are the market leaders in the cloud, then you start looking at it and saying, if I am going to provide a service that competes with the service they have, if I can make it available in their cloud, it means that I can be more competitive. And if I'm compelling and compelling means at least twice the performance or functionality or both at half the price, I should be able to gain market share. >>And that's what Oracle's done. They've taken a superior product in my SQL heat wave, which is faster, lower cost does more for a lot less at the end of the day and they make it available to the users of those clouds. You avoid this little thing called egress fees, you avoid the issue of having to migrate from one cloud to another and suddenly you have a very compelling offer. So I look at what Oracle's doing with MyQ and it feels like, I'm gonna use a word term, a flanking maneuver to their competition. They're offering a better service on their platforms. >>All right, so thank you for that. Holger, we've seen this sort of cadence, I sort of referenced it up front a little bit and they sat on MySQL for a decade, then all of a sudden we see this rush of announcements. Why did it take so long? And and more importantly is Oracle, are they developing the right features that cloud database customers are looking for in your view? >>Yeah, great question, but first of all, in your interview you said it's the edit analytics, right? Analytics is kind of like a marketing buzzword. Reports can be analytics, right? The interesting thing, which they did, the first thing they, they, they crossed the chasm between OTP and all up, right? In the same database, right? So major engineering feed very much what customers want and it's all about creating Bellevue for customers, which, which I think is the part why they go into the multi-cloud and why they add these capabilities. And they certainly with the AI capabilities, it's kind of like getting it into an autonomous field, self-driving field now with the lake cost capabilities and meeting customers where they are, like Mark has talked about the e risk costs in the cloud. So that that's a significant advantage, creating value for customers and that's what at the end of the day matters. >>And I believe strongly that long term it's gonna be ones who create better value for customers who will get more of their money From that perspective, why then take them so long? I think it's a great question. I think largely he mentioned the gentleman Nial, it's largely to who leads a product. I used to build products too, so maybe I'm a little fooling myself here, but that made the difference in my view, right? So since he's been charged, he's been building things faster than the rest of the competition, than my SQL space, which in hindsight we thought was a hot and smoking innovation phase. It kind of like was a little self complacent when it comes to the traditional borders of where, where people think, where things are separated between OTP and ola or as an example of adjacent support, right? Structured documents, whereas unstructured documents or databases and all of that has been collapsed and brought together for building a more powerful database for customers. >>So I mean it's certainly, you know, when, when Oracle talks about the competitors, you know, the competitors are in the, I always say they're, if the Oracle talks about you and knows you're doing well, so they talk a lot about aws, talk a little bit about Snowflake, you know, sort of Google, they have partnerships with Azure, but, but in, so I'm presuming that the response in MySQL heatwave was really in, in response to what they were seeing from those big competitors. But then you had Maria DB coming out, you know, the day that that Oracle acquired Sun and, and launching and going after the MySQL base. So it's, I'm, I'm interested and we'll talk about this later and what you guys think AWS and Google and Azure and Snowflake and how they're gonna respond. But, but before I do that, Ron, I want to ask you, you, you, you can get, you know, pretty technical and you've probably seen the benchmarks. >>I know you have Oracle makes a big deal out of it, publishes its benchmarks, makes some transparent on on GI GitHub. Larry Ellison talked about this in his keynote at Cloud World. What are the benchmarks show in general? I mean, when you, when you're new to the market, you gotta have a story like Mark was saying, you gotta be two x you know, the performance at half the cost or you better be or you're not gonna get any market share. So, and, and you know, oftentimes companies don't publish market benchmarks when they're leading. They do it when they, they need to gain share. So what do you make of the benchmarks? Have their, any results that were surprising to you? Have, you know, they been challenged by the competitors. Is it just a bunch of kind of desperate bench marketing to make some noise in the market or you know, are they real? What's your view? >>Well, from my perspective, I think they have the validity. And to your point, I believe that when it comes to competitor responses, that has not really happened. Nobody has like pulled down the information that's on GitHub and said, Oh, here are our price performance results. And they counter oracles. In fact, I think part of the reason why that hasn't happened is that there's the risk if Oracle's coming out and saying, Hey, we can deliver 17 times better query performance using our capabilities versus say, Snowflake when it comes to, you know, the Lakehouse platform and Snowflake turns around and says it's actually only 15 times better during performance, that's not exactly an effective maneuver. And so I think this is really to oracle's credit and I think it's refreshing because these differentiators are significant. We're not talking, you know, like 1.2% differences. We're talking 17 fold differences, we're talking six fold differences depending on, you know, where the spotlight is being shined and so forth. >>And so I think this is actually something that is actually too good to believe initially at first blush. If I'm a cloud database decision maker, I really have to prioritize this. I really would know, pay a lot more attention to this. And that's why I posed the question to Oracle and others like, okay, if these differentiators are so significant, why isn't the needle moving a bit more? And it's for, you know, some of the usual reasons. One is really deep discounting coming from, you know, the other players that's really kind of, you know, marketing 1 0 1, this is something you need to do when there's a real competitive threat to keep, you know, a customer in your own customer base. Plus there is the usual fear and uncertainty about moving from one platform to another. But I think, you know, the traction, the momentum is, is shifting an Oracle's favor. I think we saw that in the Q1 efforts, for example, where Oracle cloud grew 44% and that it generated, you know, 4.8 billion and revenue if I recall correctly. And so, so all these are demonstrating that's Oracle is making, I think many of the right moves, publishing these figures for anybody to look at from their own perspective is something that is, I think, good for the market and I think it's just gonna continue to pay dividends for Oracle down the horizon as you know, competition intens plots. So if I were in, >>Dave, can I, Dave, can I interject something and, and what Ron just said there? Yeah, please go ahead. A couple things here, one discounting, which is a common practice when you have a real threat, as Ron pointed out, isn't going to help much in this situation simply because you can't discount to the point where you improve your performance and the performance is a huge differentiator. You may be able to get your price down, but the problem that most of them have is they don't have an integrated product service. They don't have an integrated O L T P O L A P M L N data lake. Even if you cut out two of them, they don't have any of them integrated. They have multiple services that are required separate integration and that can't be overcome with discounting. And the, they, you have to pay for each one of these. And oh, by the way, as you grow, the discounts go away. So that's a, it's a minor important detail. >>So, so that's a TCO question mark, right? And I know you look at this a lot, if I had that kind of price performance advantage, I would be pounding tco, especially if I need two separate databases to do the job. That one can do, that's gonna be, the TCO numbers are gonna be off the chart or maybe down the chart, which you want. Have you looked at this and how does it compare with, you know, the big cloud guys, for example, >>I've looked at it in depth, in fact, I'm working on another TCO on this arena, but you can find it on Wiki bod in which I compared TCO for MySEQ Heat wave versus Aurora plus Redshift plus ML plus Blue. I've compared it against gcps services, Azure services, Snowflake with other services. And there's just no comparison. The, the TCO differences are huge. More importantly, thefor, the, the TCO per performance is huge. We're talking in some cases multiple orders of magnitude, but at least an order of magnitude difference. So discounting isn't gonna help you much at the end of the day, it's only going to lower your cost a little, but it doesn't improve the automation, it doesn't improve the performance, it doesn't improve the time to insight, it doesn't improve all those things that you want out of a database or multiple databases because you >>Can't discount yourself to a higher value proposition. >>So what about, I wonder ho if you could chime in on the developer angle. You, you followed that, that market. How do these innovations from heatwave, I think you used the term developer velocity. I've heard you used that before. Yeah, I mean, look, Oracle owns Java, okay, so it, it's, you know, most popular, you know, programming language in the world, blah, blah blah. But it does it have the, the minds and hearts of, of developers and does, where does heatwave fit into that equation? >>I think heatwave is gaining quickly mindshare on the developer side, right? It's not the traditional no sequel database which grew up, there's a traditional mistrust of oracles to developers to what was happening to open source when gets acquired. Like in the case of Oracle versus Java and where my sql, right? And, but we know it's not a good competitive strategy to, to bank on Oracle screwing up because it hasn't worked not on Java known my sequel, right? And for developers, it's, once you get to know a technology product and you can do more, it becomes kind of like a Swiss army knife and you can build more use case, you can build more powerful applications. That's super, super important because you don't have to get certified in multiple databases. You, you are fast at getting things done, you achieve fire, develop velocity, and the managers are happy because they don't have to license more things, send you to more trainings, have more risk of something not being delivered, right? >>So it's really the, we see the suite where this best of breed play happening here, which in general was happening before already with Oracle's flagship database. Whereas those Amazon as an example, right? And now the interesting thing is every step away Oracle was always a one database company that can be only one and they're now generally talking about heat web and that two database company with different market spaces, but same value proposition of integrating more things very, very quickly to have a universal database that I call, they call the converge database for all the needs of an enterprise to run certain application use cases. And that's what's attractive to developers. >>It's, it's ironic isn't it? I mean I, you know, the rumor was the TK Thomas Curian left Oracle cuz he wanted to put Oracle database on other clouds and other places. And maybe that was the rift. Maybe there was, I'm sure there was other things, but, but Oracle clearly is now trying to expand its Tam Ron with, with heatwave into aws, into Azure. How do you think Oracle's gonna do, you were at a cloud world, what was the sentiment from customers and the independent analyst? Is this just Oracle trying to screw with the competition, create a little diversion? Or is this, you know, serious business for Oracle? What do you think? >>No, I think it has lakes. I think it's definitely, again, attriting to Oracle's overall ability to differentiate not only my SQL heat wave, but its overall portfolio. And I think the fact that they do have the alliance with the Azure in place, that this is definitely demonstrating their commitment to meeting the multi-cloud needs of its customers as well as what we pointed to in terms of the fact that they're now offering, you know, MySQL capabilities within AWS natively and that it can now perform AWS's own offering. And I think this is all demonstrating that Oracle is, you know, not letting up, they're not resting on its laurels. That's clearly we are living in a multi-cloud world, so why not just make it more easy for customers to be able to use cloud databases according to their own specific, specific needs. And I think, you know, to holder's point, I think that definitely lines with being able to bring on more application developers to leverage these capabilities. >>I think one important announcement that's related to all this was the JSON relational duality capabilities where now it's a lot easier for application developers to use a language that they're very familiar with a JS O and not have to worry about going into relational databases to store their J S O N application coding. So this is, I think an example of the innovation that's enhancing the overall Oracle portfolio and certainly all the work with machine learning is definitely paying dividends as well. And as a result, I see Oracle continue to make these inroads that we pointed to. But I agree with Mark, you know, the short term discounting is just a stall tag. This is not denying the fact that Oracle is being able to not only deliver price performance differentiators that are dramatic, but also meeting a wide range of needs for customers out there that aren't just limited device performance consideration. >>Being able to support multi-cloud according to customer needs. Being able to reach out to the application developer community and address a very specific challenge that has plagued them for many years now. So bring it all together. Yeah, I see this as just enabling Oracles who ring true with customers. That the customers that were there were basically all of them, even though not all of them are going to be saying the same things, they're all basically saying positive feedback. And likewise, I think the analyst community is seeing this. It's always refreshing to be able to talk to customers directly and at Oracle cloud there was a litany of them and so this is just a difference maker as well as being able to talk to strategic partners. The nvidia, I think partnerships also testament to Oracle's ongoing ability to, you know, make the ecosystem more user friendly for the customers out there. >>Yeah, it's interesting when you get these all in one tools, you know, the Swiss Army knife, you expect that it's not able to be best of breed. That's the kind of surprising thing that I'm hearing about, about heatwave. I want to, I want to talk about Lake House because when I think of Lake House, I think data bricks, and to my knowledge data bricks hasn't been in the sites of Oracle yet. Maybe they're next, but, but Oracle claims that MySQL, heatwave, Lakehouse is a breakthrough in terms of capacity and performance. Mark, what are your thoughts on that? Can you double click on, on Lakehouse Oracle's claims for things like query performance and data loading? What does it mean for the market? Is Oracle really leading in, in the lake house competitive landscape? What are your thoughts? >>Well, but name in the game is what are the problems you're solving for the customer? More importantly, are those problems urgent or important? If they're urgent, customers wanna solve 'em. Now if they're important, they might get around to them. So you look at what they're doing with Lake House or previous to that machine learning or previous to that automation or previous to that O L A with O ltp and they're merging all this capability together. If you look at Snowflake or data bricks, they're tacking one problem. You look at MyQ heat wave, they're tacking multiple problems. So when you say, yeah, their queries are much better against the lake house in combination with other analytics in combination with O ltp and the fact that there are no ETLs. So you're getting all this done in real time. So it's, it's doing the query cross, cross everything in real time. >>You're solving multiple user and developer problems, you're increasing their ability to get insight faster, you're having shorter response times. So yeah, they really are solving urgent problems for customers. And by putting it where the customer lives, this is the brilliance of actually being multicloud. And I know I'm backing up here a second, but by making it work in AWS and Azure where people already live, where they already have applications, what they're saying is, we're bringing it to you. You don't have to come to us to get these, these benefits, this value overall, I think it's a brilliant strategy. I give Nip and Argo wallet a huge, huge kudos for what he's doing there. So yes, what they're doing with the lake house is going to put notice on data bricks and Snowflake and everyone else for that matter. Well >>Those are guys that whole ago you, you and I have talked about this. Those are, those are the guys that are doing sort of the best of breed. You know, they're really focused and they, you know, tend to do well at least out of the gate. Now you got Oracle's converged philosophy, obviously with Oracle database. We've seen that now it's kicking in gear with, with heatwave, you know, this whole thing of sweets versus best of breed. I mean the long term, you know, customers tend to migrate towards suite, but the new shiny toy tends to get the growth. How do you think this is gonna play out in cloud database? >>Well, it's the forever never ending story, right? And in software right suite, whereas best of breed and so far in the long run suites have always won, right? So, and sometimes they struggle again because the inherent problem of sweets is you build something larger, it has more complexity and that means your cycles to get everything working together to integrate the test that roll it out, certify whatever it is, takes you longer, right? And that's not the case. It's a fascinating part of what the effort around my SQL heat wave is that the team is out executing the previous best of breed data, bringing us something together. Now if they can maintain that pace, that's something to to, to be seen. But it, the strategy, like what Mark was saying, bring the software to the data is of course interesting and unique and totally an Oracle issue in the past, right? >>Yeah. But it had to be in your database on oci. And but at, that's an interesting part. The interesting thing on the Lake health side is, right, there's three key benefits of a lakehouse. The first one is better reporting analytics, bring more rich information together, like make the, the, the case for silicon angle, right? We want to see engagements for this video, we want to know what's happening. That's a mixed transactional video media use case, right? Typical Lakehouse use case. The next one is to build more rich applications, transactional applications which have video and these elements in there, which are the engaging one. And the third one, and that's where I'm a little critical and concerned, is it's really the base platform for artificial intelligence, right? To run deep learning to run things automatically because they have all the data in one place can create in one way. >>And that's where Oracle, I know that Ron talked about Invidia for a moment, but that's where Oracle doesn't have the strongest best story. Nonetheless, the two other main use cases of the lake house are very strong, very well only concern is four 50 terabyte sounds long. It's an arbitrary limitation. Yeah, sounds as big. So for the start, and it's the first word, they can make that bigger. You don't want your lake house to be limited and the terabyte sizes or any even petabyte size because you want to have the certainty. I can put everything in there that I think it might be relevant without knowing what questions to ask and query those questions. >>Yeah. And you know, in the early days of no schema on right, it just became a mess. But now technology has evolved to allow us to actually get more value out of that data. Data lake. Data swamp is, you know, not much more, more, more, more logical. But, and I want to get in, in a moment, I want to come back to how you think the competitors are gonna respond. Are they gonna have to sort of do a more of a converged approach? AWS in particular? But before I do, Ron, I want to ask you a question about autopilot because I heard Larry Ellison's keynote and he was talking about how, you know, most security issues are human errors with autonomy and autonomous database and things like autopilot. We take care of that. It's like autonomous vehicles, they're gonna be safer. And I went, well maybe, maybe someday. So Oracle really tries to emphasize this, that every time you see an announcement from Oracle, they talk about new, you know, autonomous capabilities. It, how legit is it? Do people care? What about, you know, what's new for heatwave Lakehouse? How much of a differentiator, Ron, do you really think autopilot is in this cloud database space? >>Yeah, I think it will definitely enhance the overall proposition. I don't think people are gonna buy, you know, lake house exclusively cause of autopilot capabilities, but when they look at the overall picture, I think it will be an added capability bonus to Oracle's benefit. And yeah, I think it's kind of one of these age old questions, how much do you automate and what is the bounce to strike? And I think we all understand with the automatic car, autonomous car analogy that there are limitations to being able to use that. However, I think it's a tool that basically every organization out there needs to at least have or at least evaluate because it goes to the point of it helps with ease of use, it helps make automation more balanced in terms of, you know, being able to test, all right, let's automate this process and see if it works well, then we can go on and switch on on autopilot for other processes. >>And then, you know, that allows, for example, the specialists to spend more time on business use cases versus, you know, manual maintenance of, of the cloud database and so forth. So I think that actually is a, a legitimate value proposition. I think it's just gonna be a case by case basis. Some organizations are gonna be more aggressive with putting automation throughout their processes throughout their organization. Others are gonna be more cautious. But it's gonna be, again, something that will help the overall Oracle proposition. And something that I think will be used with caution by many organizations, but other organizations are gonna like, hey, great, this is something that is really answering a real problem. And that is just easing the use of these databases, but also being able to better handle the automation capabilities and benefits that come with it without having, you know, a major screwup happened and the process of transitioning to more automated capabilities. >>Now, I didn't attend cloud world, it's just too many red eyes, you know, recently, so I passed. But one of the things I like to do at those events is talk to customers, you know, in the spirit of the truth, you know, they, you know, you'd have the hallway, you know, track and to talk to customers and they say, Hey, you know, here's the good, the bad and the ugly. So did you guys, did you talk to any customers my SQL Heatwave customers at, at cloud world? And and what did you learn? I don't know, Mark, did you, did you have any luck and, and having some, some private conversations? >>Yeah, I had quite a few private conversations. The one thing before I get to that, I want disagree with one point Ron made, I do believe there are customers out there buying the heat wave service, the MySEQ heat wave server service because of autopilot. Because autopilot is really revolutionary in many ways in the sense for the MySEQ developer in that it, it auto provisions, it auto parallel loads, IT auto data places it auto shape predictions. It can tell you what machine learning models are going to tell you, gonna give you your best results. And, and candidly, I've yet to meet a DBA who didn't wanna give up pedantic tasks that are pain in the kahoo, which they'd rather not do and if it's long as it was done right for them. So yes, I do think people are buying it because of autopilot and that's based on some of the conversations I had with customers at Oracle Cloud World. >>In fact, it was like, yeah, that's great, yeah, we get fantastic performance, but this really makes my life easier and I've yet to meet a DBA who didn't want to make their life easier. And it does. So yeah, I've talked to a few of them. They were excited. I asked them if they ran into any bugs, were there any difficulties in moving to it? And the answer was no. In both cases, it's interesting to note, my sequel is the most popular database on the planet. Well, some will argue that it's neck and neck with SQL Server, but if you add in Mariah DB and ProCon db, which are forks of MySQL, then yeah, by far and away it's the most popular. And as a result of that, everybody for the most part has typically a my sequel database somewhere in their organization. So this is a brilliant situation for anybody going after MyQ, but especially for heat wave. And the customers I talk to love it. I didn't find anybody complaining about it. And >>What about the migration? We talked about TCO earlier. Did your t does your TCO analysis include the migration cost or do you kind of conveniently leave that out or what? >>Well, when you look at migration costs, there are different kinds of migration costs. By the way, the worst job in the data center is the data migration manager. Forget it, no other job is as bad as that one. You get no attaboys for doing it. Right? And then when you screw up, oh boy. So in real terms, anything that can limit data migration is a good thing. And when you look at Data Lake, that limits data migration. So if you're already a MySEQ user, this is a pure MySQL as far as you're concerned. It's just a, a simple transition from one to the other. You may wanna make sure nothing broke and every you, all your tables are correct and your schema's, okay, but it's all the same. So it's a simple migration. So it's pretty much a non-event, right? When you migrate data from an O LTP to an O L A P, that's an ETL and that's gonna take time. >>But you don't have to do that with my SQL heat wave. So that's gone when you start talking about machine learning, again, you may have an etl, you may not, depending on the circumstances, but again, with my SQL heat wave, you don't, and you don't have duplicate storage, you don't have to copy it from one storage container to another to be able to be used in a different database, which by the way, ultimately adds much more cost than just the other service. So yeah, I looked at the migration and again, the users I talked to said it was a non-event. It was literally moving from one physical machine to another. If they had a new version of MySEQ running on something else and just wanted to migrate it over or just hook it up or just connect it to the data, it worked just fine. >>Okay, so every day it sounds like you guys feel, and we've certainly heard this, my colleague David Foyer, the semi-retired David Foyer was always very high on heatwave. So I think you knows got some real legitimacy here coming from a standing start, but I wanna talk about the competition, how they're likely to respond. I mean, if your AWS and you got heatwave is now in your cloud, so there's some good aspects of that. The database guys might not like that, but the infrastructure guys probably love it. Hey, more ways to sell, you know, EC two and graviton, but you're gonna, the database guys in AWS are gonna respond. They're gonna say, Hey, we got Redshift, we got aqua. What's your thoughts on, on not only how that's gonna resonate with customers, but I'm interested in what you guys think will a, I never say never about aws, you know, and are they gonna try to build, in your view a converged Oola and o LTP database? You know, Snowflake is taking an ecosystem approach. They've added in transactional capabilities to the portfolio so they're not standing still. What do you guys see in the competitive landscape in that regard going forward? Maybe Holger, you could start us off and anybody else who wants to can chime in, >>Happy to, you mentioned Snowflake last, we'll start there. I think Snowflake is imitating that strategy, right? That building out original data warehouse and the clouds tasking project to really proposition to have other data available there because AI is relevant for everybody. Ultimately people keep data in the cloud for ultimately running ai. So you see the same suite kind of like level strategy, it's gonna be a little harder because of the original positioning. How much would people know that you're doing other stuff? And I just, as a former developer manager of developers, I just don't see the speed at the moment happening at Snowflake to become really competitive to Oracle. On the flip side, putting my Oracle hat on for a moment back to you, Mark and Iran, right? What could Oracle still add? Because the, the big big things, right? The traditional chasms in the database world, they have built everything, right? >>So I, I really scratched my hat and gave Nipon a hard time at Cloud world say like, what could you be building? Destiny was very conservative. Let's get the Lakehouse thing done, it's gonna spring next year, right? And the AWS is really hard because AWS value proposition is these small innovation teams, right? That they build two pizza teams, which can be fit by two pizzas, not large teams, right? And you need suites to large teams to build these suites with lots of functionalities to make sure they work together. They're consistent, they have the same UX on the administration side, they can consume the same way, they have the same API registry, can't even stop going where the synergy comes to play over suite. So, so it's gonna be really, really hard for them to change that. But AWS super pragmatic. They're always by themselves that they'll listen to customers if they learn from customers suite as a proposition. I would not be surprised if AWS trying to bring things closer together, being morely together. >>Yeah. Well how about, can we talk about multicloud if, if, again, Oracle is very on on Oracle as you said before, but let's look forward, you know, half a year or a year. What do you think about Oracle's moves in, in multicloud in terms of what kind of penetration they're gonna have in the marketplace? You saw a lot of presentations at at cloud world, you know, we've looked pretty closely at the, the Microsoft Azure deal. I think that's really interesting. I've, I've called it a little bit of early days of a super cloud. What impact do you think this is gonna have on, on the marketplace? But, but both. And think about it within Oracle's customer base, I have no doubt they'll do great there. But what about beyond its existing install base? What do you guys think? >>Ryan, do you wanna jump on that? Go ahead. Go ahead Ryan. No, no, no, >>That's an excellent point. I think it aligns with what we've been talking about in terms of Lakehouse. I think Lake House will enable Oracle to pull more customers, more bicycle customers onto the Oracle platforms. And I think we're seeing all the signs pointing toward Oracle being able to make more inroads into the overall market. And that includes garnishing customers from the leaders in, in other words, because they are, you know, coming in as a innovator, a an alternative to, you know, the AWS proposition, the Google cloud proposition that they have less to lose and there's a result they can really drive the multi-cloud messaging to resonate with not only their existing customers, but also to be able to, to that question, Dave's posing actually garnish customers onto their platform. And, and that includes naturally my sequel but also OCI and so forth. So that's how I'm seeing this playing out. I think, you know, again, Oracle's reporting is indicating that, and I think what we saw, Oracle Cloud world is definitely validating the idea that Oracle can make more waves in the overall market in this regard. >>You know, I, I've floated this idea of Super cloud, it's kind of tongue in cheek, but, but there, I think there is some merit to it in terms of building on top of hyperscale infrastructure and abstracting some of the, that complexity. And one of the things that I'm most interested in is industry clouds and an Oracle acquisition of Cerner. I was struck by Larry Ellison's keynote, it was like, I don't know, an hour and a half and an hour and 15 minutes was focused on healthcare transformation. Well, >>So vertical, >>Right? And so, yeah, so you got Oracle's, you know, got some industry chops and you, and then you think about what they're building with, with not only oci, but then you got, you know, MyQ, you can now run in dedicated regions. You got ADB on on Exadata cloud to customer, you can put that OnPrem in in your data center and you look at what the other hyperscalers are, are doing. I I say other hyperscalers, I've always said Oracle's not really a hyperscaler, but they got a cloud so they're in the game. But you can't get, you know, big query OnPrem, you look at outposts, it's very limited in terms of, you know, the database support and again, that that will will evolve. But now you got Oracle's got, they announced Alloy, we can white label their cloud. So I'm interested in what you guys think about these moves, especially the industry cloud. We see, you know, Walmart is doing sort of their own cloud. You got Goldman Sachs doing a cloud. Do you, you guys, what do you think about that and what role does Oracle play? Any thoughts? >>Yeah, let me lemme jump on that for a moment. Now, especially with the MyQ, by making that available in multiple clouds, what they're doing is this follows the philosophy they've had the past with doing cloud, a customer taking the application and the data and putting it where the customer lives. If it's on premise, it's on premise. If it's in the cloud, it's in the cloud. By making the mice equal heat wave, essentially a plug compatible with any other mice equal as far as your, your database is concern and then giving you that integration with O L A P and ML and Data Lake and everything else, then what you've got is a compelling offering. You're making it easier for the customer to use. So I look the difference between MyQ and the Oracle database, MyQ is going to capture market more market share for them. >>You're not gonna find a lot of new users for the Oracle debate database. Yeah, there are always gonna be new users, don't get me wrong, but it's not gonna be a huge growth. Whereas my SQL heatwave is probably gonna be a major growth engine for Oracle going forward. Not just in their own cloud, but in AWS and in Azure and on premise over time that eventually it'll get there. It's not there now, but it will, they're doing the right thing on that basis. They're taking the services and when you talk about multicloud and making them available where the customer wants them, not forcing them to go where you want them, if that makes sense. And as far as where they're going in the future, I think they're gonna take a page outta what they've done with the Oracle database. They'll add things like JSON and XML and time series and spatial over time they'll make it a, a complete converged database like they did with the Oracle database. The difference being Oracle database will scale bigger and will have more transactions and be somewhat faster. And my SQL will be, for anyone who's not on the Oracle database, they're, they're not stupid, that's for sure. >>They've done Jason already. Right. But I give you that they could add graph and time series, right. Since eat with, Right, Right. Yeah, that's something absolutely right. That's, that's >>A sort of a logical move, right? >>Right. But that's, that's some kid ourselves, right? I mean has worked in Oracle's favor, right? 10 x 20 x, the amount of r and d, which is in the MyQ space, has been poured at trying to snatch workloads away from Oracle by starting with IBM 30 years ago, 20 years ago, Microsoft and, and, and, and didn't work, right? Database applications are extremely sticky when they run, you don't want to touch SIM and grow them, right? So that doesn't mean that heat phase is not an attractive offering, but it will be net new things, right? And what works in my SQL heat wave heat phases favor a little bit is it's not the massive enterprise applications which have like we the nails like, like you might be only running 30% or Oracle, but the connections and the interfaces into that is, is like 70, 80% of your enterprise. >>You take it out and it's like the spaghetti ball where you say, ah, no I really don't, don't want to do all that. Right? You don't, don't have that massive part with the equals heat phase sequel kind of like database which are more smaller tactical in comparison, but still I, I don't see them taking so much share. They will be growing because of a attractive value proposition quickly on the, the multi-cloud, right? I think it's not really multi-cloud. If you give people the chance to run your offering on different clouds, right? You can run it there. The multi-cloud advantages when the Uber offering comes out, which allows you to do things across those installations, right? I can migrate data, I can create data across something like Google has done with B query Omni, I can run predictive models or even make iron models in different place and distribute them, right? And Oracle is paving the road for that, but being available on these clouds. But the multi-cloud capability of database which knows I'm running on different clouds that is still yet to be built there. >>Yeah. And >>That the problem with >>That, that's the super cloud concept that I flowed and I I've always said kinda snowflake with a single global instance is sort of, you know, headed in that direction and maybe has a league. What's the issue with that mark? >>Yeah, the problem with the, with that version, the multi-cloud is clouds to charge egress fees. As long as they charge egress fees to move data between clouds, it's gonna make it very difficult to do a real multi-cloud implementation. Even Snowflake, which runs multi-cloud, has to pass out on the egress fees of their customer when data moves between clouds. And that's really expensive. I mean there, there is one customer I talked to who is beta testing for them, the MySQL heatwave and aws. The only reason they didn't want to do that until it was running on AWS is the egress fees were so great to move it to OCI that they couldn't afford it. Yeah. Egress fees are the big issue but, >>But Mark the, the point might be you might wanna root query and only get the results set back, right was much more tinier, which been the answer before for low latency between the class A problem, which we sometimes still have but mostly don't have. Right? And I think in general this with fees coming down based on the Oracle general E with fee move and it's very hard to justify those, right? But, but it's, it's not about moving data as a multi-cloud high value use case. It's about doing intelligent things with that data, right? Putting into other places, replicating it, what I'm saying the same thing what you said before, running remote queries on that, analyzing it, running AI on it, running AI models on that. That's the interesting thing. Cross administered in the same way. Taking things out, making sure compliance happens. Making sure when Ron says I don't want to be American anymore, I want to be in the European cloud that is gets migrated, right? So tho those are the interesting value use case which are really, really hard for enterprise to program hand by hand by developers and they would love to have out of the box and that's yet the innovation to come to, we have to come to see. But the first step to get there is that your software runs in multiple clouds and that's what Oracle's doing so well with my SQL >>Guys. Amazing. >>Go ahead. Yeah. >>Yeah. >>For example, >>Amazing amount of data knowledge and, and brain power in this market. Guys, I really want to thank you for coming on to the cube. Ron Holger. Mark, always a pleasure to have you on. Really appreciate your time. >>Well all the last names we're very happy for Romanic last and moderator. Thanks Dave for moderating us. All right, >>We'll see. We'll see you guys around. Safe travels to all and thank you for watching this power panel, The Truth About My SQL Heat Wave on the cube. Your leader in enterprise and emerging tech coverage.

>>Everyone, welcome to the cube here in Palo Alto, California for a special presentation on Cloud native at scale, enabling super cloud modern applications with Platform nine. I'm John Furry, your host of The Cube. We've got a great lineup of three interviews we're streaming today. Mattor Makki, who's the co-founder and VP of Product of Platform nine. She's gonna go into detail around Arlon, the open source products, and also the value of what this means for infrastructure as code and for cloud native at scale. Bickley the chief architect of Platform nine Cube alumni. Going back to the OpenStack days. He's gonna go into why Arlon, why this infrastructure as code implication, what it means for customers and the implications in the open source community and where that value is. Really great wide ranging conversation there. And of course, Vascar, Gort, the CEO of Platform nine, is gonna talk with me about his views on Super Cloud and why Platform nine has a scalable solutions to bring cloud native at scale. So enjoy the program, see you soon. Hello and welcome to the cube here in Palo Alto, California for a special program on cloud native at scale, enabling next generation cloud or super cloud for modern application cloud native developers. I'm John Forry, host of the Cube. Pleasure to have here me Makowski, co-founder and VP of product at Platform nine. Thanks for coming in today for this Cloudnative at scale conversation. >>Thank you for having >>Me. So Cloudnative at scale, something that we're talking about because we're seeing the, the next level of mainstream success of containers Kubernetes and cloud native develop, basically DevOps in the C I C D pipeline. It's changing the landscape of infrastructure as code, it's accelerating the value proposition and the super cloud as we call it, has been getting a lot of traction because this next generation cloud is looking a lot different, but kind of the same as the first generation. What's your view on Super cloud as it fits to cloud native as scales up? >>Yeah, you know, I think what's interesting, and I think the reason why Super Cloud is a really good and a really fit term for this, and I think, I know my CEO was chatting with you as well, and he was mentioning this as well, but I think there needs to be a different term than just multi-cloud or cloud. And the reason is because as cloud native and cloud deployments have scaled, I think we've reached a point now where instead of having the traditional data center style model, where you have a few large distributors of infrastructure and workload at a few locations, I think the model is kind of flipped around, right? Where you have a large number of micro sites. These micro sites could be your public cloud deployment, your private on-prem infrastructure deployments, or it could be your edge environment, right? And every single enterprise, every single industry is moving in that direction. And so you gotta rougher that with a terminology that, that, that indicates the scale and complexity of it. And so I think super cloud is a, is an appropriate term for >>That. So you brought a couple things I want to dig into. You mentioned Edge Notes. We're seeing not only edge nodes being the next kind of area of innovation, mainly because it's just popping up everywhere. And that's just the beginning. Wouldn't even know what's around the corner. You got buildings, you got iot, o ot, and it kind of coming together, but you also got this idea of regions, global infrastructures, big part of it. I just saw some news around cloud flare shutting down a site here, there's policies being made at scale. These new challenges there. Can you share because you can have edge. So hybrid cloud is a winning formula. Everybody knows that it's a steady state. Yeah. But across multiple clouds brings in this new un engineered area, yet it hasn't been done yet. Spanning clouds. People say they're doing it, but you start to see the toe in the water, it's happening, it's gonna happen. It's only gonna get accelerated with the edge and beyond globally. So I have to ask you, what is the technical challenges in doing this? Because it's something business consequences as well, but there are technical challenge. Can you share your view on what the technical challenges are for the super cloud across multiple edges and >>Regions? Yeah, absolutely. So I think, you know, in in the context of this, the, this, this term of super cloud, I think it's sometimes easier to visualize things in terms of two access, right? I think on one end you can think of the scale in terms of just pure number of nodes that you have, deploy number of clusters in the Kubernetes space. And then on the other access you would have your distribution factor, right? Which is, do you have these tens of thousands of nodes in one site or do you have them distributed across tens of thousands of sites with one node at each site? Right? And if you have just one flavor of this, there is enough complexity, but potentially manageable. But when you are expanding on both these access, you really get to a point where that skill really needs some well thought out, well-structured solutions to address it, right? A combination of homegrown tooling along with your, you know, favorite distribution of Kubernetes is not a strategy that can help you in this environment. It may help you when you have one of this or when you, when you scale, is not at the level. >>Can you scope the complexity? Because I mean, I hear a lot of moving parts going on there, the technology's also getting better. We we're seeing cloud native become successful. There's a lot to configure, there's a lot to install. Can you scope the scale of the problem? Because we're talking about at scale Yep. Challenges here. >>Yeah, absolutely. And I think, you know, I I like to call it, you know, the, the, the problem that the scale creates, you know, there's various problems, but I think one, one problem, one way to think about it is, is, you know, it works on my cluster problem, right? So, you know, I come from engineering background and there's a, you know, there's a famous saying between engineers and QA and the support folks, right? Which is, it works on my laptop, which is I tested this change, everything was fantastic, it worked flawlessly on my machine, on production, It's not working. The exact same problem now happens and these distributed environments, but at massive scale, right? Which is that, you know, developers test their applications, et cetera within the sanctity of their sandbox environments. But once you expose that change in the wild world of your production deployment, right? >>And the production deployment could be going at the radio cell tower at the edge location where a cluster is running there, or it could be sending, you know, these applications and having them run at my customer's site where they might not have configured that cluster exactly the same way as I configured it, or they configured the cluster, right? But maybe they didn't deploy the security policies or they didn't deploy the other infrastructure plugins that my app relies on all of these various factors at their own layer of complexity. And there really isn't a simple way to solve that today. And that is just, you know, one example of an issue that happens. I think another, you know, whole new ball game of issues come in the context of security, right? Because when you are deploying applications at scale in a distributed manner, you gotta make sure someone's job is on the line to ensure that the right security policies are enforced regardless of that scale factor. So I think that's another example of problems that occur. >>Okay. So I have to ask about scale because there are a lot of multiple steps involved when you see the success cloud native, you know, you see some, you know, some experimentation. They set up a cluster, say it's containers and Kubernetes, and then you say, Okay, we got this, we can configure it. And then they do it again and again, they call it day two. Some people call it day one, day two operation, whatever you call it. Once you get past the first initial thing, then you gotta scale it. Then you're seeing security breaches, you're seeing configuration errors. This seems to be where the hotpot is. And when companies transition from, I got this to, Oh no, it's harder than I thought at scale. Can you share your reaction to that and how you see this playing out? >>Yeah, so, you know, I think it's interesting. There's multiple problems that occur when, you know, the, the two factors of scale is we talked about start expanding. I think one of them is what I like to call the, you know, it, it works fine on my cluster problem, which is back in, when I was a developer, we used to call this, it works on my laptop problem, which is, you know, you have your perfectly written code that is operating just fine on your machine, your sandbox environment. But the moment it runs production, it comes back with p zeros and POS from support teams, et cetera. And those issues can be really difficult to try us, right? And so in the Kubernetes environment, this problem kind of multi folds, it goes, you know, escalates to a higher degree because yeah, you have your sandbox developer environments, they have their clusters and things work perfectly fine in those clusters because these clusters are typically handcrafted or a combination of some scripting and handcrafting. >>And so as you give that change to then run at your production edge location, like say you radio sell tower site, or you hand it over to a customer to run it on their cluster, they might not have not have configured that cluster exactly how you did it, or they might not have configured some of the infrastructure plugins. And so the things don't work. And when things don't work, triaging them becomes like ishly hard, right? It's just one of the examples of the problem. Another whole bucket of issues is security, which is, is you have these distributed clusters at scale, you gotta ensure someone's job is on the line to make sure that these security policies are configured properly. >>So this is a huge problem. I love that comment. That's not not happening on my system. It's the classic, you know, debugging mentality. Yeah. But at scale it's hard to do that with error prone. I can see that being a problem. And you guys have a solution you're launching, Can you share what our lawn is, this new product, What is it all about? Talk about this new introduction. >>Yeah, absolutely. I'm very, very excited. You know, it's one of the projects that we've been working on for some time now because we are very passionate about this problem and just solving problems at scale in on-prem or at in the cloud or at edge environments. And what arwan is, it's an open source project and it is a tool, it's a Kubernetes native tool for complete end to end management of not just your clusters, but your clusters. All of the infrastructure that goes within and along the sites of those clusters, security policies, your middleware plugins, and finally your applications. So what alarm lets you do in a nutshell is in a declarative way, it lets you handle the configuration and management of all of these components in at scale. >>So what's the elevator pitch simply put for what this solves in, in terms of the chaos you guys are reigning in. What's the, what's the bumper sticker? Yeah, >>What would it do? There's a perfect analogy that I love to reference in this context, which is think of your assembly line, you know, in a traditional, let's say, you know, an auto manufacturing factory or et cetera, and the level of efficiency at scale that that assembly line brings, right online. And if you look at the logo we've designed, it's this funny little robot. And it's because when we think of online, we, we think of these enterprise large scale environments, you know, sprawling at scale creating chaos because there isn't necessarily a well thought through, well structured solution that's similar to an assembly line, which is taking each components, you know, addressing them, manufacturing, processing them in a standardized way, then handing to the next stage. But again, it gets, you know, processed in a standardized way. And that's what Arlon really does. That's like the I pitch. If you have problems of scale of managing your infrastructure, you know, that is distributed. Arlon brings the assembly line level of efficiency and consistency >>For those. So keeping it smooth, the assembly on things are flowing. C C I CD pipelining. Exactly. So that's what you're trying to simplify that ops piece for the developer. I mean, it's not really ops, it's their ops, it's coding. >>Yeah. Not just developer, the ops, the operations folks as well, right? Because developers, you know, there is, the developers are responsible for one picture of that layer, which is my apps, and then maybe that middleware of application that they interface with, but then they hand it over to someone else who's then responsible to ensure that these apps are secure properly, that they are logging, logs are being collected properly, monitoring and observability integrated. And so it solves problems for both those >>Teams. Yeah. It's DevOps. So the DevOps is the cloud native developer. The OP teams have to kind of set policies. Is that where the declarative piece comes in? Is that why that's important? >>Absolutely. Yeah. And, and, and, and you know, Kubernetes really in introduced or elevated this declarative management, right? Because, you know, c communities clusters are Yeah. Or your, yeah, you know, specifications of components that go in Kubernetes are defined in a declarative way. And Kubernetes always keeps that state consistent with your defined state. But when you go outside of that world of a single cluster, and when you actually talk about defining the clusters or defining everything that's around it, there really isn't a solution that does that today. And so online addresses that problem at the heart of it, and it does that using existing open source well known solutions. >>Ed, do I wanna get into the benefits? What's in it for me as the customer developer? But I want to finish this out real quick and get your thoughts. You mentioned open source. Why open source? What's the, what's the current state of the product? You run the product group over at platform nine, is it open source? And you guys have a product that's commercial? Can you explain the open source dynamic? And first of all, why open source? Yeah. And what is the consumption? I mean, open source is great, People want open source, they can download it, look up the code, but maybe wanna buy the commercial. So I'm assuming you have that thought through, can you share open source and commercial relationship? >>Yeah, I think, you know, starting with why open source? I think it's, you know, we as a company, we have, you know, one of the things that's absolutely critical to us is that we take mainstream open source technologies components and then we, you know, make them available to our customers at scale through either a SaaS model on from model, right? But, so as we are a company or startup or a company that benefits, you know, in a massive way by this open source economy, it's only right, I think in my mind that we do our part of the duty, right? And contribute back to the community that feeds us. And so, you know, we have always held that strongly as one of our principles. And we have, you know, created and built independent products starting all the way with fi, which was a serverless product, you know, that we had built to various other, you know, examples that I can give. But that's one of the main reasons why opensource and also opensource because we want the community to really firsthand engage with us on this problem, which is very difficult to achieve if your product is behind a wall, you know, behind, behind a block box. >>Well, and that's, that's what the developers want too. I mean, what we're seeing in reporting with Super Cloud is the new model of consumption is I wanna look at the code and see what's in there. That's right. And then also, if I want to use it, I, I'll do it. Great. That's open source, that's the value. But then at the end of the day, if I wanna move fast, that's when people buy in. So it's a new kind of freemium, I guess, business model. I guess that's the way that, Well, but that's, that's the benefit. Open source. This is why standards and open source is growing so fast. You have that confluence of, you know, a way for helpers to try before they buy, but also actually kind of date the application, if you will. We, you know, Adrian Karo uses the dating me metaphor, you know, Hey, you know, I wanna check it out first before I get married. Right? And that's what open source, So this is the new, this is how people are selling. This is not just open source, this is how companies are selling. >>Absolutely. Yeah. Yeah. You know, I think, and you know, two things. I think one is just, you know, this, this, this cloud native space is so vast that if you, if you're building a close flow solution, sometimes there's also a risk that it may not apply to every single enterprises use cases. And so having it open source gives them an opportunity to extend it, expand it, to make it proper to their use case if they choose to do so, right? But at the same time, what's also critical to us is we are able to provide a supported version of it with an SLA that we, you know, that's backed by us, a SAS hosted version of it as well, for those customers who choose to go that route, you know, once they have used the open source version and loved it and want to take it at scale and in production and need, need, need a partner to collaborate with, who can, you know, support them for that production >>Environment. I have to ask you now, let's get into what's in it for the customer. I'm a customer, why should I be enthused about Arlo? What's in it for me? You know? Cause if I'm not enthused about it, I'm not gonna be confident and it's gonna be hard for me to get behind this. Can you share your enthusiastic view of, you know, why I should be enthused about Arlo customer? >>Yeah, absolutely. And so, and there's multiple, you know, enterprises that we talk to, many of them, you know, our customers, where this is a very kind of typical story that you hear, which is we have, you know, a Kubernetes distribution. It could be on premise, it could be public clouds, native es, and then we have our C I CD pipelines that are automating the deployment of applications, et cetera. And then there's this gray zone. And the gray zone is well before you can you, your CS CD pipelines can deploy the apps. Somebody needs to do all of their groundwork of, you know, defining those clusters and yeah. You know, properly configuring them. And as these things, these things start by being done hand grown. And then as the, as you scale, what typically enterprises would do today is they will have their home homegrown DIY solutions for this. >>I mean, the number of folks that I talk to that have built Terra from automation, and then, you know, some of those key developers leave. So it's a typical open source or typical, you know, DIY challenge. And the reason that they're writing it themselves is not because they want to. I mean, of course technology is always interesting to everybody, but it's because they can't find a solution that's out there that perfectly fits the problem. And so that's that pitch. I think Spico would be delighted. The folks that we've talked, you know, spoken with, have been absolutely excited and have, you know, shared that this is a major challenge we have today because we have, you know, few hundreds of clusters on s Amazon and we wanna scale them to few thousands, but we don't think we are ready to do that. And this will give us >>Stability. Yeah, I think people are scared, not sc I won't say scare, that's a bad word. Maybe I should say that they feel nervous because, you know, at scale small mistakes can become large mistakes. This is something that is concerning to enterprises. And, and I think this is gonna come up at co con this year where enterprises are gonna say, Okay, I need to see SLAs. I wanna see track record, I wanna see other companies that have used it. Yeah. How would you answer that question to, or, or challenge, you know, Hey, I love this, but is there any guarantees? Is there any, what's the SLAs? I'm an enterprise, I got tight, you know, I love the open source trying to free fast and loose, but I need hardened code. >>Yeah, absolutely. So, so two parts to that, right? One is Arlan leverages existing open source components, products that are extremely popular. Two specifically. One is Lon uses Argo cd, which is probably one of the highest rated and used CD open source tools that's out there, right? It's created by folks that are as part of Intuit team now, you know, really brilliant team. And it's used at scale across enterprises. That's one. Second is arlon also makes use of cluster api capi, which is a ES sub-component, right? For lifecycle management of clusters. So there is enough of, you know, community users, et cetera, around these two products, right? Or, or, or open source projects that will find Arlan to be right up in their alley because they're already comfortable, familiar with algo cd. Now Arlan just extends the scope of what Algo CD can do. And so that's one. And then the second part is going back to a point of the comfort. And that's where, you know, Platform nine has a role to play, which is when you are ready to deploy Alon at scale, because you've been, you know, playing with it in your DEF test environments, you're happy with what you get with it, then Platform nine will stand behind it and provide that sla. >>And what's been the reaction from customers you've talked to Platform nine customers with, with, that are familiar with, with Argo and then Arlo? What's been some of the feedback? >>Yeah, I, I, I think the feedback's been fantastic. I mean, I can give you examples of customers where, you know, initially, you know, when you are, when you're telling them about your entire portfolio of solutions, it might not strike a card right away. But then we start talking about Arlan and, and we talk about the fact that it uses Argo CD and they start opening up, they say, We have standardized on Argo and we have built these components, homegrown, we would be very interested. Can we co-develop? Does it support these use cases? So we've had that kind of validation. We've had validation all the way at the beginning of our line before we even wrote a single line of code saying this is something we plan on doing. And the customer said, If you had it today, I would've purchased it. So it's been really great validation. >>All right. So next question is, what is the solution to the customer? If I asked you, Look it, I have, I'm so busy, my team's overworked. I got a skills gap. I don't need another project that's, I'm so tied up right now and I'm just chasing my tail. How does Platform nine help me? >>Yeah, absolutely. So I think, you know, one of the core tenets of Platform nine has always been that we try to bring that public cloud like simplicity by hosting, you know, this in a lot of such similar tools in a SaaS hosted manner for our customers, right? So our goal behind doing that is taking away or trying to take away all of that complexity from customer's hands and offloading it to our hands, right? And giving them that full white glove treatment as we call it. And so from a customer's perspective, one, something like arlon will integrate with what they have so they don't have to rip and replace anything. In fact, it will, even in the next versions, it may even discover your clusters that you have today and, you know, give you an inventory and that, >>So customers have clusters that are growing, that's a sign correct call you guys. >>Absolutely. Either they're, they have massive large clusters, right? That they wanna split into smaller clusters, but they're not comfortable doing that today, or they've done that already on say, public cloud or otherwise. And now they have management challenges. So >>Especially operationalizing the clusters, whether they want to kind of reset everything and remove things around and reconfigure Yeah. And or scale out. >>That's right. Exactly. >>And you provide that layer of policy. >>Absolutely. >>Yes. That's the key value >>Here. That's right. >>So policy based configuration for cluster scale up >>Profile and policy based declarative configuration and life cycle management for clusters. >>If I asked you how this enables Super club, what would you say to that? >>I think this is one of the key ingredients to super cloud, right? If you think about a super cloud environment, there's at least few key ingredients that that come to my mind that are really critical. Like they are, you know, life saving ingredients at that scale. One is having a really good strategy for managing that scale, you know, in a, going back to assembly line in a very consistent, predictable way so that our lot solves then you, you need to compliment that with the right kind of observability and monitoring tools at scale, right? Because ultimately issues are gonna happen and you're gonna have to figure out, you know, how to solve them fast. And alon by the way, also helps in that direction, but you also need observability tools. And then especially if you're running it on the public cloud, you need some cost management tools. In my mind, these three things are like the most necessary ingredients to make Super Cloud successful. And, you know, alarm flows >>In one. Okay, so now the next level is, Okay, that makes sense. There's under the covers kind of speak under the hood. Yeah. How does that impact the app developers and the cloud native modern application workflows? Because the impact to me, seems the apps are gonna be impacted. Are they gonna be faster, stronger? I mean, what's the impact if you do all those things, as you mentioned, what's the impact of the apps? >>Yeah, the impact is that your apps are more likely to operate in production the way you expect them to, because the right checks and balances have gone through, and any discrepancies have been identified prior to those apps, prior to your customer running into them, right? Because developers run into this challenge to their, where there's a split responsibility, right? I'm responsible for my code, I'm responsible for some of these other plugins, but I don't own the stack end to end. I have to rely on my ops counterpart to do their part, right? And so this really gives them, you know, the right tooling for >>That. So this is actually a great kind of relevant point, you know, as cloud becomes more scalable, you're starting to see this fragmentation gone of the days of the full stack developer to the more specialized role. But this is a key point, and I have to ask you because if this Arlo solution takes place, as you say, and the apps are gonna be stupid, there's designed to do, the question is, what did, does the current pain look like of the apps breaking? What does the signals to the customer Yeah. That they should be calling you guys up into implementing Arlo, Argo, and, and, and on all the other goodness to automate, What are some of the signals? Is it downtime? Is it, is it failed apps, Is it latency? What are some of the things that Yeah, absolutely would be in indications of things are effed up a little bit. >>Yeah. More frequent down times, down times that are, that take longer to triage. And so you are, you know, the, you know, your mean times on resolution, et cetera, are escalating or growing larger, right? Like we have environments of customers where they, they have a number of folks on in the field that have to take these apps and run them at customer sites. And that's one of our partners. And they're extremely interested in this because the, the rate of failures they're encountering for this, you know, the field when they're running these apps on site, because the field is automating their clusters that are running on sites using their own script. So these are the kinds of challenges, and those are the pain points, which is, you know, if you're looking to reduce your, your meantime to resolution, if you're looking to reduce the number of failures that occur on your production site, that's one. And second, if you are looking to manage these at scale environments with a relatively small, focused, nimble ops team, which has an immediate impact on your, So those are, those are the >>Signals. This is the cloud native at scale situation, the innovation going on. Final thought is your reaction to the idea that if the world goes digital, which it is, and the confluence of physical and digital coming together, and cloud continues to do its thing, the company becomes the application, not where it used to be supporting the business, you know, the back office and the IIA terminals and some PCs and handhelds. Now if technology's running, the business is the business. Yeah. The company's the application. Yeah. So it can't be down. So there's a lot of pressure on, on CSOs and CIOs now and see, and boards is saying, how is technology driving the top line revenue? That's the number one conversation. Yeah. Do you see that same thing? >>Yeah. It's interesting. I think there's multiple pressures at the CXO CIO level, right? One is that there needs to be that visibility and clarity and guarantee almost that, you know, that the, the technology that's, you know, that's gonna drive your top line is gonna drive that in a consistent, reliable, predictable manner. And then second, there is the constant pressure to do that while always lowering your costs of doing it, right? Especially when you're talking about, let's say retailers or those kinds of large scale vendors, they many times make money by lowering the amount that they spend on, you know, providing those goods to their end customers. So I think those, both those factors kind of come into play and the solution to all of them is usually in a very structured strategy around automation. >>Final question. What does cloudnative at scale look like to you? If all the things happen the way we want 'em to happen, The magic wand, the magic dust, what does it look like? >>What that looks like to me is a CIO sipping at his desk on coffee production is running absolutely smooth. And his, he's running that at a nimble, nimble team size of at the most, a handful of folks that are just looking after things with things. So just >>Taking care of, and the CIO doesn't exist. There's no CSO there at the beach. >>Yeah. >>Thank you for coming on, sharing the cloud native at scale here on the cube. Thank you for your time. >>Fantastic. Thanks for having >>Me. Okay. I'm John Fur here for special program presentation, special programming cloud native at scale, enabling super cloud modern applications with Platform nine. Thanks for watching. Welcome back everyone to the special presentation of cloud native at scale, the cube and platform nine special presentation going in and digging into the next generation super cloud infrastructure as code and the future of application development. We're here at Bickley, who's the chief architect and co-founder of Platform nine b. Great to see you Cube alumni. We, we met at an OpenStack event in about eight years ago, or well later, earlier when opens Stack was going. Great to see you and great to see congratulations on the success of platform nine. >>Thank you very much. >>Yeah. You guys have been at this for a while and this is really the, the, the year we're seeing the, the crossover of Kubernetes because of what happens with containers. Everyone now was realized, and you've seen what Docker's doing with the new docker, the open source Docker now just a success Exactly. Of containerization, right? And now the Kubernetes layer that we've been working on for years is coming, bearing fruit. This is huge. >>Exactly. Yes. >>And so as infrastructure's code comes in, we talked to Bacar talking about Super Cloud, I met her about, you know, the new Arlon, our R lawn you guys just launched, the infrastructure's code is going to another level. And then it's always been DevOps infrastructure is code. That's been the ethos that's been like from day one, developers just code. Then you saw the rise of serverless and you see now multi-cloud or on the horizon, connect the dots for us. What is the state of infrastructures code today? >>So I think, I think I'm, I'm glad you mentioned it, everybody or most people know about infrastructures code. But with Kubernetes, I think that project has evolved at the concept even further. And these dates, it's infrastructure as configuration, right? So, which is an evolution of infrastructure as code. So instead of telling the system, here's how I want my infrastructure by telling it, you know, do step A, B, C, and D instead with Kubernetes, you can describe your desired state declaratively using things called manifest resources. And then the system kind of magically figures it out and tries to converge the state towards the one that you specify. So I think it's, it's a even better version of infrastructures code. >>Yeah, yeah. And, and that really means it's developer just accessing resources. Okay. Not declaring, Okay, give me some compute, stand me up some, turn the lights on, turn 'em off, turn 'em on. That's kind of where we see this going. And I like the configuration piece. Some people say composability, I mean now with open source, so popular, you don't have to have to write a lot of code. It's code being developed. And so it's into integration, it's configuration. These are areas that we're starting to see computer science principles around automation, machine learning, assisting open source. Cuz you got a lot of code that's right in hearing software, supply chain issues. So infrastructure as code has to factor in these new, new dynamics. Can you share your opinion on these new dynamics of, as open source grows, the glue layers, the configurations, the integration, what are the core issues? >>I think one of the major core issues is with all that power comes complexity, right? So, you know, despite its expressive power systems like Kubernetes and declarative APIs let you express a lot of complicated and complex stacks, right? But you're dealing with hundreds if not thousands of these yamo files or resources. And so I think, you know, the emergence of systems and layers to help you manage that complexity is becoming a key challenge and opportunity in, in this space that, >>That's, I wrote a LinkedIn post today was comments about, you know, hey, enterprise is the new breed, the trend of SaaS companies moving our consumer comp consumer-like thinking into the enterprise has been happening for a long time, but now more than ever, you're seeing it the old way used to be solve complexity with more complexity and then lock the customer in. Now with open source, it's speed, simplification and integration, right? These are the new dynamic power dynamics for developers. Yeah. So as companies are starting to now deploy and look at Kubernetes, what are the things that need to be in place? Because you have some, I won't say technical debt, but maybe some shortcuts, some scripts here that make it look like infrastructure is code. People have done some things to simulate or or make infrastructure as code happen. Yes. But to do it at scale Yes. Is harder. What's your take on this? What's your >>View? It's hard because there's a per proliferation of methods, tools, technologies. So for example, today it's very common for DevOps and platform engineering tools, I mean, sorry, teams to have to deploy a large number of Kubernetes clusters, but then apply the applications and configurations on top of those clusters. And they're using a wide range of tools to do this, right? For example, maybe Ansible or Terraform or bash scripts to bring up the infrastructure and then the clusters. And then they may use a different set of tools such as Argo CD or other tools to apply configurations and applications on top of the clusters. So you have this sprawl of tools. You, you also have this sprawl of configurations and files because the more objects you're dealing with, the more resources you have to manage. And there's a risk of drift that people call that where, you know, you think you have things under control, but some people from various teams will make changes here and there and then before the end of the day systems break and you have no idea of tracking them. So I think there's real need to kind of unify, simplify, and try to solve these problems using a smaller, more unified set of tools and methodologies. And that's something that we try to do with this new project. Arlon. >>Yeah. So, so we're gonna get into Arlan in a second. I wanna get into the why Arlon. You guys announced that at our GoCon, which was put on here in Silicon Valley at the, at the by intu. They had their own little day over there at their headquarters. But before we get there, Vascar, your CEO came on and he talked about Super Cloud at our inaugural event. What's your definition of super cloud? If you had to kind of explain that to someone at a cocktail party or someone in the industry technical, how would you look at the super cloud trend that's emerging? It's become a thing. What's your, what would be your contribution to that definition or the narrative? >>Well, it's, it's, it's funny because I've actually heard of the term for the first time today, speaking to you earlier today. But I think based on what you said, I I already get kind of some of the, the gist and the, the main concepts. It seems like super cloud, the way I interpret that is, you know, clouds and infrastructure, programmable infrastructure, all of those things are becoming commodity in a way. And everyone's got their own flavor, but there's a real opportunity for people to solve real business problems by perhaps trying to abstract away, you know, all of those various implementations and then building better abstractions that are perhaps business or application specific to help companies and businesses solve real business problems. >>Yeah, I remember that's a great, great definition. I remember, not to date myself, but back in the old days, you know, IBM had a proprietary network operating system, so to deck for the mini computer vendors, deck net and SNA respectively. But T C P I P came out of the osi, the open systems interconnect and remember, ethernet beat token ring out. So not to get all nerdy for all the young kids out there, look, just look up token ring, you'll see, you've probably never heard of it. It's IBM's, you know, connection for the internet at the, the layer too is Amazon, the ethernet, right? So if T C P I P could be the Kubernetes and the container abstraction that made the industry completely change at that point in history. So at every major inflection point where there's been serious industry change and wealth creation and business value, there's been an abstraction Yes. Somewhere. Yes. What's your reaction to that? >>I think this is, I think a saying that's been heard many times in this industry and, and I forgot who originated it, but I think the saying goes like, there's no problem that can't be solved with another layer of indirection, right? And we've seen this over and over and over again where Amazon and its peers have inserted this layer that has simplified, you know, computing and, and infrastructure management. And I believe this trend is going to continue, right? The next set of problems are going to be solved with these insertions of additional abstraction layers. I think that that's really a, yeah, it's gonna continue. >>It's interesting. I just really wrote another post today on LinkedIn called the Silicon Wars AMD Stock is down arm has been on rise, we've remember pointing for many years now, that arm's gonna be hugely, it has become true. If you look at the success of the infrastructure as a service layer across the clouds, Azure, aws, Amazon's clearly way ahead of everybody. The stuff that they're doing with the silicon and the physics and the, the atoms, the pro, you know, this is where the innovation, they're going so deep and so strong at ISAs, the more that they get that gets come on, they have more performance. So if you're an app developer, wouldn't you want the best performance and you'd wanna have the best abstraction layer that gives you the most ability to do infrastructures, code or infrastructure for configuration, for provisioning, for managing services. And you're seeing that today with service MeSHs, a lot of action going on in the service mesh area in, in this community of co con, which will be a covering. So that brings up the whole what's next? You guys just announced our lawn at ar GoCon, which came out of Intuit. We've had Maria Teel at our super cloud event, She's a cto, you know, they're all in the cloud. So they contributed that project. Where did Arlon come from? What was the origination? What's the purpose? Why our lawn, why this announcement? Yeah, >>So the, the inception of the project, this was the result of us realizing that problem that we spoke about earlier, which is complexity, right? With all of this, these clouds, these infrastructure, all the variations around and you know, compute storage networks and the proliferation of tools we talked about the Ansibles and Terraforms and Kubernetes itself, you can think of that as another tool, right? We saw a need to solve that complexity problem, and especially for people and users who use Kubernetes at scale. So when you have, you know, hundreds of clusters, thousands of applications, thousands of users spread out over many, many locations, there, there needs to be a system that helps simplify that management, right? So that means fewer tools, more expressive ways of describing the state that you want and more consistency. And, and that's why, you know, we built AR lawn and we built it recognizing that many of these problems or sub problems have already been solved. So Arlon doesn't try to reinvent the wheel, it instead rests on the shoulders of several giants, right? So for example, Kubernetes is one building block, GI ops, and Argo CD is another one, which provides a very structured way of applying configuration. And then we have projects like cluster API and cross plane, which provide APIs for describing infrastructure. So arlon takes all of those building blocks and builds a thin layer, which gives users a very expressive way of defining configuration and desired state. So that's, that's kind of the inception of, And >>What's the benefit of that? What does that give the, what does that give the developer, the user, in this case, >>The developers, the, the platform engineer, team members, the DevOps engineers, they get a a ways to provision not just infrastructure and clusters, but also applications and configurations. They get a way, a system for provisioning, configuring, deploying, and doing life cycle management in a, in a much simpler way. Okay. Especially as I said, if you're dealing with a large number of applications. >>So it's like an operating fabric, if you will. Yes. For them. Okay, so let's get into what that means for up above and below the, the, this abstraction or thin layer below the infrastructure. We talked a lot about what's going on below that. Yeah. Above our workloads at the end of the day, and I talk to CXOs and IT folks that, that are now DevOps engineers. They care about the workloads and they want the infrastructure's code to work. They wanna spend their time getting in the weeds, figuring out what happened when someone made a push that that happened or something happened. They need observability and they need to, to know that it's working. That's right. And here's my workloads running effectively. So how do you guys look at the workload side of it? Cuz now you have multiple workloads on these fabric, right? >>So workloads, so Kubernetes has defined kind of a standard way to describe workloads and you can, you know, tell Kubernetes, I want to run this container this particular way, or you can use other projects that are in the Kubernetes cloud native ecosystem, like K native, where you can express your application in more at a higher level, right? But what's also happening is in addition to the workloads, DevOps and platform engineering teams, they need to very often deploy the applications with the clusters themselves. Clusters are becoming this commodity. It's, it's becoming this host for the application and it kind of comes bundled with it. In many cases it is like an appliance, right? So DevOps teams have to provision clusters at a really incredible rate and they need to tear them down. Clusters are becoming more, >>It's coming like an EC two instance, spin up a cluster. We've heard people used words like that. That's >>Right. And before arlon you kind of had to do all of that using a different set of tools as, as I explained. So with AR loan you can kind of express everything together. You can say I want a cluster with a health monitoring stack and a logging stack and this ingress controller and I want these applications and these security policies. You can describe all of that using something we call the profile. And then you can stamp out your app, your applications and your clusters and manage them in a very, So >>It's essentially standard, like creates a mechanism. Exactly. Standardized, declarative kind of configurations. And it's like a playbook, just deploy it. Now what there is between say a script like I'm, I have scripts, I can just automate scripts >>Or yes, this is where that declarative API and infrastructure as configuration comes in, right? Because scripts, yes you can automate scripts, but the order in which they run matters, right? They can break, things can break in the middle and, and sometimes you need to debug them. Whereas the declarative way is much more expressive and powerful. You just tell the system what you want and then the system kind of figures it out. And there are these things are controllers which will in the background reconcile all the state to converge towards your desire. It's a much more powerful, expressive and reliable way of getting things done. >>So infrastructure as configuration is built kind of on, it's a super set of infrastructures code because it's >>An evolution. >>You need edge's code, but then you can configure the code by just saying do it. You basically declaring saying Go, go do that. That's right. Okay, so, alright, so cloud native at scale, take me through your vision of what that means. Someone says, Hey, what does cloud native at scale mean? What's success look like? How does it roll out in the future as you, not future next couple years. I mean people are now starting to figure out, okay, it's not as easy as it sounds. Kubernetes has value. We're gonna hear this year at CubeCon a lot of this, what does cloud native at scale >>Mean? Yeah, there are different interpretations, but if you ask me, when people think of scale, they think of a large number of deployments, right? Geographies, many, you know, supporting thousands or tens or millions of, of users there, there's that aspect to scale. There's also an equally important a aspect of scale, which is also something that we try to address with Arran. And that is just complexity for the people operating this or configuring this, right? So in order to describe that desired state, and in order to perform things like maybe upgrades or updates on a very large scale, you want the humans behind that to be able to express and direct the system to do that in, in relatively simple terms, right? And so we want the tools and the abstractions and the mechanisms available to the user to be as powerful but as simple as possible. So there's, I think there's gonna be a number and there have been a number of CNCF and cloud native projects that are trying to attack that complexity problem as well. And Arlon kind of falls in in that >>Category. Okay, so I'll put you on the spot rogue, that CubeCon coming up and now this'll be shipping this segment series out before. What do you expect to see at this year? It's the big story this year. What's the, what's the most important thing happening? Is it in the open source community and also within a lot of the, the people jockeying for leadership. I know there's a lot of projects and still there's some white space in the overall systems map about the different areas get run time and there's ability in all these different areas. What's the, where's the action? Where, where's the smoke? Where's the fire? Where's the piece? Where's the tension? >>Yeah, so I think one thing that has been happening over the past couple of coupon and I expect to continue and, and that is the, the word on the street is Kubernetes is getting boring, right? Which is good, right? >>Boring means simple. >>Well, well >>Maybe, >>Yeah, >>Invisible, >>No drama, right? So, so the, the rate of change of the Kubernetes features and, and all that has slowed but in, in a, in a positive way. But there's still a general sentiment and feeling that there's just too much stuff. If you look at a stack necessary for hosting applications based on Kubernetes, there are just still too many moving parts, too many components, right? Too much complexity. I go, I keep going back to the complexity problem. So I expect Cube Con and all the vendors and the players and the startups and the people there to continue to focus on that complexity problem and introduce further simplifications to, to the stack. >>Yeah. Vic, you've had an storied career VMware over decades with them within 12 years with 14 years or something like that. Big number co-founder here a platform. I you's been around for a while at this game, man. We talked about OpenStack, that project we interviewed at one of their events. So OpenStack was the beginning of that, this new revolution. I remember the early days it was, it wasn't supposed to be an alternative to Amazon, but it was a way to do more cloud cloud native. I think we had a Cloud Aati team at that time. We would joke we, you know, about, about the dream. It's happening now, now at Platform nine. You guys have been doing this for a while. What's the, what are you most excited about as the chief architect? What did you guys double down on? What did you guys pivot from or two, did you do any pivots? Did you extend out certain areas? Cuz you guys are in a good position right now, a lot of DNA in Cloud native. What are you most excited about and what does Platform Nine bring to the table for customers and for people in the industry watching this? >>Yeah, so I think our mission really hasn't changed over the years, right? It's been always about taking complex open source software because open source software, it's powerful. It solves new problems, you know, every year and you have new things coming out all the time, right? Opens Stack was an example and then Kubernetes took the world by storm. But there's always that complexity of, you know, just configuring it, deploying it, running it, operating it. And our mission has always been that we will take all that complexity and just make it, you know, easy for users to consume regardless of the technology, right? So the successor to Kubernetes, you know, I don't have a crystal ball, but you know, you have some indications that people are coming up of new and simpler ways of running applications. There are many projects around there who knows what's coming next year or the year after that. But platform will a, platform nine will be there and we will, you know, take the innovations from the the community. We will contribute our own innovations and make all of those things very consumable to customers. >>Simpler, faster, cheaper. Exactly. Always a good business model technically to make that happen. Yes. Yeah, I think the, the reigning in the chaos is key, you know, Now we have now visibility into the scale. Final question before we depart this segment. What is at scale, how many clusters do you see that would be a watermark for an at scale conversation around an enterprise? Is it workloads we're looking at or, or clusters? How would you, Yeah, how would you describe that? When people try to squint through and evaluate what's a scale, what's the at scale kind of threshold? >>Yeah. And, and the number of clusters doesn't tell the whole story because clusters can be small in terms of the number of nodes or they can be large. But roughly speaking when we say, you know, large scale cluster deployments, we're talking about maybe hundreds, two thousands. >>Yeah. And final final question, what's the role of the hyperscalers? You got AWS continuing to do well, but they got their core ias, they got a PAs, they're not too too much putting a SaaS out there. They have some SaaS apps, but mostly it's the ecosystem. They have marketplaces doing, doing over $2 billion billions of transactions a year and, and it's just like, just sitting there. It hasn't really, they're now innovating on it, but that's gonna change ecosystems. What's the role the cloud play in the cloud need of its scale? >>The, the hyper squares? >>Yeah, yeah. A's Azure Google, >>You mean from a business perspective, they're, they have their own interests that, you know, that they're, they will keep catering to, they, they will continue to find ways to lock their users into their ecosystem of services and, and APIs. So I don't think that's gonna change, right? They're just gonna keep well, >>They got great performance. I mean, from a, from a hardware standpoint, yes. That's gonna be key, >>Right? Yes. I think the, the move from X 86 being the dominant way and platform to run workloads is changing, right? That, that, that, that, and I think the, the hyper skaters really want to be in the game in terms of, you know, the, the new risk and arm ecosystems, the platforms. >>Yeah. Not joking aside, Paul Morritz, when he was the CEO of VMware, when he took over once said, I remember our first year doing the cube. Oh the cloud is one big distributed computer. It's, it's hardware and you got software and you got middleware and he kinda over, well he's kind of tongue in cheek, but really you're talking about large compute and sets of services that is essentially a distributed computer. Yes, >>Exactly. >>It's, we're back in the same game. Thank you for coming on the segment. Appreciate your time. This is cloud native at scale special presentation with Platform nine. Really unpacking super cloud Arlon open source and how to run large scale applications on the cloud, cloud native develop for developers. And John Furrier with the cube. Thanks for Washington. We'll stay tuned for another great segment coming right up. Hey, welcome back everyone to Super Cloud 22. I'm John Fur, host of the Cuba here all day talking about the future of cloud. Where's it all going? Making it super multi-cloud is around the corner and public cloud is winning. Got the private cloud on premise and Edge. Got a great guest here, Vascar Gorde, CEO of Platform nine, just on the panel on Kubernetes. An enabler blocker. Welcome back. Great to have you on. >>Good to see you >>Again. So Kubernetes is a blocker enabler by, with a question mark I put on on there. Panel was really to discuss the role of Kubernetes. Now great conversation operations is impacted. What's just thing about what you guys are doing at Platform nine? Is your role there as CEO and the company's position, kind of like the world spun into the direction of Platform nine while you're at the helm, right? >>Absolutely. In fact, things are moving very well and since they came to us, it was an insight to call ourselves the platform company eight years ago, right? So absolutely whether you are doing it in public clouds or private clouds, you know, the application world is moving very fast in trying to become digital and cloud native. There are many options for you to run the infrastructure. The biggest blocking factor now is having a unified platform. And that's what where we come into >>Patrick, we were talking before we came on stage here about your background and we were kind of talking about the glory days in 2000, 2001 when the first ASPs application service providers came out. Kind of a SaaS vibe, but that was kind of all kind of cloud-like >>It wasn't, >>And web services started then too. So you saw that whole growth. Now, fast forward 20 years later, 22 years later, where we are now, when you look back then to here and all the different cycles, >>In fact, you know, as we were talking offline, I was in one of those ASPs in the year 2000 where it was a novel concept of saying we are providing a software and a capability as a service, right? You sign up and start using it. I think a lot has changed since then. The tooling, the tools, the technology has really skyrocketed. The app development environment has really taken off exceptionally well. There are many, many choices of infrastructure now, right? So I think things are in a way the same but also extremely different. But more importantly now for any company, regardless of size, to be a digital native, to become a digital company is extremely mission critical. It's no longer a nice to have everybody's in the journey somewhere. >>Everyone is going digital transformation here. Even on a so-called downturn recession that's upcoming inflations sea year. It's interesting. This is the first downturn, the history of the world where the hyperscale clouds have been pumping on all cylinders as an economic input. And if you look at the tech trends, GDPs down, but not tech. Nope. Cause pandemic showed everyone digital transformation is here and more spend and more growth is coming even in, in tech. So this is a unique factor which proves that that digital transformation's happening and company, every company will need a super cloud. >>Everyone, every company, regardless of size, regardless of location, has to become modernize their infrastructure. And modernizing infrastructure is not just some, you know, new servers and new application tools. It's your approach, how you're serving your customers, how you're bringing agility in your organization. I think that is becoming a necessity for every enterprise to survive. >>I wanna get your thoughts on Super Cloud because one of the things Dave Alon and I want to do with Super Cloud and calling it that was we, I, I personally, and I know Dave as well, he can, I'll speak from, he can speak for himself. We didn't like multi-cloud. I mean not because Amazon said don't call things multi-cloud, it just didn't feel right. I mean everyone has multiple clouds by default. If you're running productivity software, you have Azure and Office 365. But it wasn't truly distributed. It wasn't truly decentralized, it wasn't truly cloud enabled. It didn't, it felt like they're not ready for a market yet. Yet public clouds booming on premise. Private cloud and Edge is much more on, you know, more, More dynamic, more unreal. >>Yeah. I think the reason why we think Super cloud is a better term than multi-cloud. Multi-cloud are more than one cloud, but they're disconnected. Okay, you have a productivity cloud, you have a Salesforce cloud, you may have, everyone has an internal cloud, right? So, but they're not connected. So you can say, okay, it's more than one cloud. So it's, you know, multi-cloud. But super cloud is where you are actually trying to look at this holistically. Whether it is on-prem, whether it is public, whether it's at the edge, it's a store at the branch. You are looking at this as one unit. And that's where we see the term super cloud is more applicable because what are the qualities that you require if you're in a super cloud, right? You need choice of infrastructure, you need, but at the same time you need a single pan or a single platform for you to build your innovations on, regardless of which cloud you're doing it on, right? So I think Super Cloud is actually a more tightly integrated orchestrated management philosophy we think. >>So let's get into some of the super cloud type trends that we've been reporting on. Again, the purpose of this event is as a pilot to get the conversations flowing with, with the influencers like yourselves who are running companies and building products and the builders, Amazon and Azure are doing extremely well. Google's coming up in third Cloudworks in public cloud. We see the use cases on premises use cases. Kubernetes has been an interesting phenomenon because it's become from the developer side a little bit, but a lot of ops people love Kubernetes. It's really more of an ops thing. You mentioned OpenStack earlier. Kubernetes kind of came out of that open stack. We need an orchestration. And then containers had a good shot with, with Docker. They re pivoted the company. Now they're all in an open source. So you got containers booming and Kubernetes as a new layer there. >>What's, >>What's the take on that? What does that really mean? Is that a new defacto enabler? It >>Is here. It's for here for sure. Every enterprise somewhere in the journey is going on. And you know, most companies are, 70 plus percent of them have 1, 2, 3 container based, Kubernetes based applications now being rolled out. So it's very much here. It is in production at scale by many customers. And it, the beauty of it is yes, open source, but the biggest gating factor is the skill set. And that's where we have a phenomenal engineering team, right? So it's, it's one thing to buy a tool and >>Just be clear, you're a managed service for Kubernetes. >>We provide, provide a software platform for cloud acceleration as a service and it can run anywhere. It can run in public private. We have customers who do it in truly multi-cloud environments. It runs on the edge, it runs at this in stores about thousands of stores in a retailer. So we provide that and also for specific segments where data sovereignty and data residency are key regulatory reasons. We also un on-prem as an air gap version. Can >>You give an example on how you guys are deploying your platform to enable a super cloud experience for your customer? Right. >>So I'll give you two different examples. One is a very large networking company, public networking company. They have hundreds of products, hundreds of r and d teams that are building different, different products. And if you look at few years back, each one was doing it on a different platforms, but they really needed to bring the agility. And they worked with us now over three years where we are their build test dev pro platform where all their products are built on, right? And it has dramatically increased their agility to release new products. Number two, it actually is a light out operation. In fact, the customer says like, like the Maytag service person, cuz we provide it as a service and it barely takes one or two people to maintain it for them. >>So it's kinda like an SRE vibe. One person managing a >>Large 4,000 engineers building infrastructure >>On their tools, >>Whatever they want on their tools. They're using whatever app development tools they use, but they use our platform. What >>Benefits are they seeing? Are they seeing speed? >>Speed, definitely. Okay. Definitely they're speeding. Speed uniformity because now they're building able to build, so their customers who are using product A and product B are seeing a similar set of tools that are being used. >>So a big problem that's coming outta this super cloud event that we're, we're seeing and we heard it all here, ops and security teams. Cause they're kind of part of one thing, but option security specifically need to catch up speed wise. Are you delivering that value to ops and security? Right? >>So we, we work with ops and security teams and infrastructure teams and we layer on top of that. We have like a platform team. If you think about it, depending on where you have data centers, where you have infrastructure, you have multiple teams, okay, but you need a unified platform. Who's your buyer? Our buyer is usually, you know, the product divisions of companies that are looking at or the CTO would be a buyer for us functionally cio definitely. So it it's, it's somewhere in the DevOps to infrastructure. But the ideal one we are beginning to see now many large corporations are really looking at it as a platform and saying we have a platform group on which any app can be developed and it is run on any infrastructure. So the platform engineering teams. So >>You working two sides to that coin. You've got the dev side and then >>And then infrastructure >>Side. >>Okay. Another customer that I give an example, which I would say is kind of the edge of the store. So they have thousands of stores. Retail, retail, you know food retailer, right? They have thousands of stores that are on the globe, 50,000, 60,000. And they really want to enhance the customer experience that happens when you either order the product or go into the store and pick up your product or buy or browse or sit there. They have applications that were written in the nineties and then they have very modern AIML applications today. They want something that will not have to send an IT person to install a rack in the store or they can't move everything to the cloud because the store operations has to be local. The menu changes based on it's classic edge. It's classic edge, yeah. Right? They can't send it people to go install rack access servers then they can't sell software people to go install the software and any change you wanna put through that, you know, truck roll. So they've been working with us where all they do is they ship, depending on the size of the store, one or two or three little servers with instructions that >>You, you say little servers like how big one like a box, like a small little box, >>Right? And all the person in the store has to do like what you and I do at home and we get a, you know, a router is connect the power, connect the internet and turn the switch on. And from there we pick it up. >>Yep. >>We provide the operating system, everything and then the applications are put on it. And so that dramatically brings the velocity for them. They manage thousands of >>Them. True plug and play >>Two, plug and play thousands of stores. They manage it centrally. We do it for them, right? So, so that's another example where on the edge then we have some customers who have both a large private presence and one of the public clouds. Okay. But they want to have the same platform layer of orchestration and management that they can use regardless of the locations. >>So you guys got some success. Congratulations. Got some traction there. It's awesome. The question I want to ask you is that's come up is what is truly cloud native? Cuz there's lift and shift of the cloud >>That's not cloud native. >>Then there's cloud native. Cloud native seems to be the driver for the super cloud. How do you talk to customers? How do you explain when someone says what's cloud native, what isn't cloud native? >>Right. Look, I think first of all, the best place to look at what is the definition and what are the attributes and characteristics of what is truly a cloud native, is CNC foundation. And I think it's very well documented, very well. >>Tucan, of course Detroit's >>Coming so, so it's already there, right? So we follow that very closely, right? I think just lifting and shifting your 20 year old application onto a data center somewhere is not cloud native. Okay? You can't put to cloud, not you have to rewrite and redevelop your application in business logic using modern tools. Hopefully more open source and, and I think that's what Cloudnative is and we are seeing a lot of our customers in that journey. Now everybody wants to be cloudnative, but it's not that easy, okay? Because it's, I think it's first of all, skill set is very important. Uniformity of tools that there's so many tools there. Thousands and thousands of tools you could spend your time figuring out which tool to use. Okay? So I think the complexity is there, but the business benefits of agility and uniformity and customer experience are truly being done. >>And I'll give you an example, I don't know how clear native they are, right? And they're not a customer of ours, but you order pizzas, you do, right? If you just watch the pizza industry, how dominoes actually increase their share and mind share and wallet share was not because they were making better pizzas or not, I don't know anything about that, but the whole experience of how you order, how you watch what's happening, how it's delivered. There were a pioneer in it. To me, those are the kinds of customer experiences that cloud native can provide. >>Being agility and having that flow to the application changes what the expectations >>Are >>For the customer. Customer, >>The customer's expectations change, right? Once you get used to a better customer experience, you learn. >>That's to wrap it up. I wanna just get your perspective again. One of the benefits of chatting with you here and having you part of the Super Cloud 22 is you've seen many cycles, you have a lot of insights. I want to ask you, given your career where you've been and what you've done and now let's CEO platform nine, how would you compare what's happening now with other inflection points in the industry? And you've been, again, you've been an entrepreneur, you sold your company to Oracle, you've been seeing the big companies, you've seen the different waves. What's going on right now put into context this moment in time around Super Cloud. >>Sure. I think as you said, a lot of battles. CARSs being been in an asb, being in a real time software company, being in large enterprise software houses and a transformation. I've been on the app side, I did the infrastructure right and then tried to build our own platforms. I've gone through all of this myself with lot of lessons learned in there. I think this is an event which is happening now for companies to go through to become cloud native and digitalize. If I were to look back and look at some parallels of the tsunami that's going on is a couple of paddles come to me. One is, think of it, which was forced to honors like y2k. Everybody around the world had to have a plan, a strategy, and an execution for y2k. I would say the next big thing was e-commerce. I think e-commerce has been pervasive right across all industries. >>And disruptive. >>And disruptive, extremely disruptive. If you did not adapt and adapt and accelerate your e-commerce initiative, you were, it was an existence question. Yeah. I think we are at that pivotal moment now in companies trying to become digital and cloudnative. You know, that is what I see >>Happening there. I think that that e-commerce is interesting and I think just to riff with you on that is that it's disrupting and refactoring the business models. I think that is something that's coming out of this is that it's not just completely changing the gain, it's just changing how you operate, >>How you think and how you operate. See, if you think about the early days of e-commerce, just putting up a shopping cart that made you an e-commerce or e retailer or an e e e customer, right? Or so. I think it's the same thing now is I think this is a fundamental shift on how you're thinking about your business. How are you gonna operate? How are you gonna service your customers? I think it requires that just lift and shift is not gonna work. >>Nascar, thank you for coming on, spending the time to come in and share with our community and being part of Super Cloud 22. We really appreciate, we're gonna keep this open. We're gonna keep this conversation going even after the event, to open up and look at the structural changes happening now and continue to look at it in the open in the community. And we're gonna keep this going for, for a long, long time as we get answers to the problems that customers are looking for with cloud cloud computing. I'm Sean Fur with Super Cloud 22 in the Cube. Thanks for watching. >>Thank you. Thank you. >>Hello and welcome back. This is the end of our program, our special presentation with Platform nine on cloud native at scale, enabling the super cloud. We're continuing the theme here. You heard the interviews Super Cloud and its challenges, new opportunities around solutions around like Platform nine and others with Arlon. This is really about the edge situations on the internet and managing the edge multiple regions, avoiding vendor lock in. This is what this new super cloud is all about. The business consequences we heard and and the wide ranging conversations around what it means for open source and the complexity problem all being solved. I hope you enjoyed this program. There's a lot of moving pieces and things to configure with cloud native install, all making it easier for you here with Super Cloud and of course Platform nine contributing to that. Thank you for watching.

>>Welcome back to super cloud 22, our inaugural event. It's a pilot event here in the cube studios we're live and streaming virtually until we do it in person. Maybe next year. I'm John fury, host of the cube with Dave Lon two great guests, distinguished engineers managers, CTOs investors. Mariana Tessel is a CTO of Intuit ins Ray founder of vertex ventures. Both have a lot of DNA. Founder allow cloud here with mark Andre and Ben Horowitz, a variety of other great ventures you've done. And now you're an investor. Yep. Maria, you've been a seasoned CTO, VP of engineering, VMware Docker Intuit. Now thanks for joining us. >>Absolutely. >>So super cloud is a, is a thing. And apparently it's got a lot of momentum and you guys got stats over there at, at Intuit in, so you're investing and we were challenged on super cloud. Our initial thesis was you build on the clouds, get all that leverage like snowflake, you get a good differentiation and then you compete and then move to other clouds. Now it's becoming a thing where I can do this. Every enterprise could possibly do it. So I want to get your guys thoughts on what you think of super cloud concept and where are the holes in it, what needs to be defined. And so we'll start with you. You've done a lot of cloud things in your day. What >>Do you think? Yeah, it's the whole cloud journey started with a desire to consolidate and desire to actually provide uniformity and, and standards driven ways of doing things. And I think Amazon was a leader there. They helped kind of teach everybody else. You know, when I was in loud cloud, we were trying to do it with proprietary stacks just wouldn't work. But once everyone standardized upon Unix and you know, the chip sets no longer became as relevant. They did a lot of good things there, but what's happened since then is now you've got competing standards at the API layer at the interface layer no longer at the chip set layer, no longer at the operating system layer. Right? So the evolution of the, the, the battles are still there. When you talk about multicloud and super cloud, though, like one of the big things you have to keep in mind is latency is not free. Latency is very expensive and it's getting even more expensive now with, with multi-cloud. So you have to really understand where the separations of boundaries are between your data, your compute, and, and the network is just there as a facilitator to help binding compute and data. Right? And I think there's a lot of bets being made across different vendors like CloudFlare Akamai, as well as Amazon Google Microsoft in terms of how they think we should take computing either to the edge, from the core or back and forth. >>These, this is structural change. I mean, this is structural, >>It's desired by incumbents, but it's not something that I'm seeing from the consumption. I'd love to hear, hear from our end's per perspective, from a consumption point of view, like how much edge computing really matters. Right. >>Mario. >>So I think there's like, there's kind of a, a story of like two, like it's kind of, you can cut it for both edges. No, no pun intended on one end. It is really simplifying to actually go into like a single cloud and standardize on it and just have everything there. But I think what over time companies find is that they end up in multiple clouds, whether like, you know, through acquisitions or through like needing to use a service in another cloud. So you do find yourself in a situation where you have multi multi-cloud and you have to kind of work through it and understand how to make it all like work and latency is an issue, but also for many, many workloads, you can work around it and you can make it work where you have workloads that actually span multiple vendors and clouds. You know, again, having said that, I would say the world is such, that is still a simplifying assumption. When if you go to a single cloud, it's much easier to just go and, and bet on that >>Easier in terms of everything's integrated, IAS works with SAS, they solve a lot of problems. >>Correct. And you can do like for your developers, you can actually provide an environment that's super homogenous, simple. You can use services easily up and down the stack. And, you know, we, we actually made that deliberate decision. When we started migrating to the cloud at the beginning, it was like, oh, let's do like hybrid we'll, you know, make it, so it work anywhere. It was so complicated. It was not worth it. >>When was the, when did you give up, what was the moment? Was there a flash point where you said, oh, this is terrible. This is >>Dead. Yeah. When, when we started to try to make it interoperable and you just see what it requires to do that and the complexity of the architecture that it just became not worth it for the gains you have. >>So speaking obviously as a SAS provider, right. So it just doesn't, it didn't make business case sense for you guys to do that. So it was super cloud. Then an infrastructure thing we just heard from Ben wa deja VI that they're not, they're going beyond instantiating their, their data cloud. They're actually running, you know, their own little snow grid. They called it. And, and then when I asked him, well, what about latency? He said, well, we copied data over, you know, so, okay. That's you have to do, but that's a singular experience with the same governance or the same security. Just wasn't worth it for you guys is what I'm hearing. >>Correct. But again, like for some workload or for some services that we want to use, we are gonna go there and we are gonna then figure out what is the work around the latency issue, whether it's like copy or, you know, redundancy. >>Well, the question I have Dave on snowflake is maybe the question for you and in the panel is snowflake a tan expansion opportunity, or is there a technical reason to go to other clouds? >>I think they wanted to leverage the hyperscale infrastructure globally. And they said that they're out there, it's a free gift. We're gonna go take it. I, I think it started with we're on AWS. Do you think? And then we're on Azure and then we're on Google. And then they said, why don't we just connect all these and make it a singular experience? And yeah, I guess it's a TA expansion as a differentiator and it's, it adds value. Right. If I can share data across that global network, >>We have customers on Azure now, >>Right? Yeah. Yeah. Of course. >>You guys don't need to go CP. What do you think about that? >>Well, I think Snowflake's in a good position cuz they work mostly with analytical workloads and you have capacity. That's always gonna increase like no one subtracts, their analytical workload like ever, right. So there was just compounded growth is like 50% or 80% for, you know, many enterprises despite their best intentions, not to collect more data, they just can't stop doing it. So it's different than if you're like an Oracle or a transactional database where you don't have those, you know, like kind of infinite growth paths. So Snowflake's gonna continue to expand footprint their customers. They don't mind as long as you, they can figure out the, the lowest cost on denominator for, for that. >>Yeah. So it makes sense to be in all the clouds >>For them, for, for them, for sure. Yeah. >>But, but, but Oracle just announced with Microsoft what I would call super cloud, a, a cross cloud database service running on OCI and Azure with very low latency and a database that looks like a, the singular experience. Yeah. With, with a PAs layers >>That lost me after OCI that's >>Okay. You know, but that's the, that's the, the BS answer for all U VCs. The do nobody develops on Oracle? Well, it's a 240 billion market cap company. Show me who you all want be. >>We're gonna talk about SRDF and em C next, you >>All want Oracle. So there we go. You throw that into, you all want Oracle to buy your companies, your funding, you know, cause, cause we all wanna be like Oracle with that kinda cash flow. But, but anyway, >>Here's, here's one thing that I'm noticing that is gonna be really practical. I think for companies that do run SA is because like, you know, you have all these solutions, whether it's like analytics or like monitoring or logging or whatever. And each one of them is very data hungry and all of them have like SAS solutions that end up copy the data, moving data to their cloud, and then they might charge you by the size of your data. It does become kind of overwhelming for companies to use that many tools and basically maybe have that data kind of charge for it, multiple places because you use it for different purposes or just in general, if you have a lot of data, you know, that that is becoming an issue. So that's something that I've noticed in our, in our own kind of, you know, a world, but it's just something that I think companies need to think about how they solve because eventually a lot of companies will say, I cannot have all these solutions, so there's no way I'm gonna be willing to have so many copies of the data and actually pay for that. >>So many times, just something to think about. >>But one of the criticisms of the super cloud concept is that it's just SAS. If I'm running workload on prem and I, and I've got, you know, a connection to the cloud, which you probably do, that's, that's SAS, what's, what's the big deal and that's not anything new or different. So I'd love to get your thoughts on that. But Goldman Sachs, for instance, just announced the service last reinvent with AWS, connecting their tools, their data, and their software from on-prem to AWS, they're offering it as a service. I'm like, Hmm. Kind of looking like Supercloud, but maybe it's just SAS. >>It could be. And like, what I'm talking about is not so much like, you know, like what you wanna connect your data. But the idea is like a lot of the providers of different services, like in the past and, and like higher layer, they're actually COPI the data. They need the data in their cloud or their solution. And it just becomes complicated and expensive is, is kind of like my point. So yes, connecting it like for you to have the data in one place and then be able to connect to it. I think that is a valid, if, if that's kinda what you think about as a super cloud, that is a valid need, I think that companies will >>Have where developers actually want access to tools that might exist. >>Also the key is developers, right? Yeah. Developers decide all decisions, not database on administrators, not, you know, a hundred percent security engineers, not admins. So what's really interesting is where are the developers going next? If you look at the current winners in the current ecosystem, companies like MongoDB, I mean, they capture the minds of yeah. The JavaScript, you know, no JS developers absolutely very early on. And I started catch base and I could tell you like the difference was that capture motion was so important. So developers are basically used to this game-like experience now where they want to see tools that are free, whether it's open source or not, they actually don't care. They just want, and they want it SAS. They want it SAS delivered on demand. Right. And pay as you go. And so there's a lot of these different frameworks coming out next generation, no code, low code, whether it's Java, JavaScript, rust, you know, whatever, you know, go Lang. And there's a lot of people fighting religious wars about how to develop the next kind of modern pattern design pattern. Okay. And that's where a lot of excitement is how we look at like investment opportunities. Like where are those big bets who are, you know, frustrated developers, who are they frustrated, what's wrong with their current environment? You know, do they really enjoy using Kubernetes or trying to use Kubernetes? Yeah. Right. Like developers have a very different view than operator, >>But you mentioned couch base. I mean, I look at couch base what they're doing with Capellas as a form of Supercloud. I mean, I think that's an excellent, they're bringing that out to the edge. We're gonna hear later on from someone from couch base. That's gonna talk about that now. It's kind of a lightweight, you know, sort of, it's gonna be a, a synchronization, but it's the beginning >>A cool new venture deal that I'm not in, but was like duck DB. I'm like, what's duck DB like, well, it's an Emory database that has like this like remote store thing. I'm like, okay, that sounds interesting. Like let's call Mike Olson cuz that sounds like sleepy cat redone red distributed world. But like it's, it's like there's a lot of people refactoring design patterns that we're all grew up with since the popup days of, you know, typical round. Right? >>Yeah. That's the refactory I think that's the big pattern. So I have to ask you guys, what are you guys investing in? We've got a couple minutes left to chat about that. What are you investing at into it from a, from a, a CTO engineering perspective and what are you investing in that feels super cloud like to you? >>Well, the, the thing that like I'm focused on is to make sure that we have absolutely best in the world development environment for our engineers, where it's modern, it's easy to use and it incorporates as many things as we can into that environment. So the engineers don't have to think about it. Like one big example would be security and how we incorporated that into development environment. So again, the engineers don't have to bother with trying to think through how they secure their workloads and every step of the way their other things that we incorporated, whether it's like rollbacks or monitoring or, you know, like baly enough other things. But I think that's really an investment that has panned off for us. We actually started investing in development environment several years ago. We started measure our development velocity and we, it actually went up by six X justly investing. So >>User experience, developer experience and productivity pretty much right. >>Yeah. AB absolutely. Yeah. That's like a big investment area for us that, you know, cloud cloud >>Sounds like super cloudlike factor and I'm assuming it's you're on AWS. >>We are mostly on AWS. Yes. >>And so what are you investing in that from a VC money doling out standpoint? That feels super cloudlike >>So very similar to what we just touched on a lot of developer tool experiences. We have a company that we've invested in called ops level that the service catalogs it's, it's helping, you know, understand your, where your services live and how they could be accessed and, and you know, enterprise kind of that come with that. And then we have a company called Lugo that helps you do serverless debugging container debugging, cuz it turns out debugging distributed, you know, applications is a real problem right now just you can only do so much by log tracing, right? We have a company haven't announced yet that's in the web assembly space. So we're looking at modernizing the next generation past stack and throwing everything out the window, including Java and all of the, you know, current prebuilt components because turns out 90% of enterprise workloads are actually not used. They're they're just policy code. You compiled with they're sitting there as vulnerabilities that no one's actually accessing, but you still have to compile with all of it. So we have a lot of bloatware happening in the enterprise. So we're thinking about how do you skinny that up with the next generation paths that's enterprise capable with security context and frameworks >>Super pass. >>Well, yeah, super pass. That's a kind of good way to, well, is >>It, is it a consistent developer experience across clouds? >>It is. And, and, and, and web assembly is a very raw standard if you can call it that. I mean it's, but it's supported by every modern browser, every major platform, vendor cloud, and Adobe and others, and are using it for their uses. And it's not just about your edge browser compute. It's really, you can take the same framework and compile it down to server side as well as client site, just like JavaScript was a client side tool before it became node. Right. Right. So we're looking at that as a very interesting opportunity. It's very nascent. Yeah. >>Great patterns. Yeah. Well, thanks so much for spending the time outta your busy day. Ariana. Thanks for your commentary. Appreciate your coming on the cubes first in IGUR super cloud event, pilot. Thanks for, for sharing. Thanks for having, thanks for having us. Okay. More coverage here. Super cloud 2022. I'm Jeff David Alane stay with us. We got our cloud ARA panel coming up next.