>> Welcome back to Supercloud22, #Supercloud22. This is Dave Vellante. In 2019 Oracle and Microsoft announced a collaboration to bring interoperability between OCI, Oracle Cloud Infrastructure and Azure Clouds. It was Oracle's initial foray into so-called multi-cloud and we're joined by Karan Batta, who's the Vice President for Product Management at OCI. And Kris Rice is the Vice President of Software Development at Oracle Database. And we're going to talk about how this technology's evolving and whether it fits our view of what we call supercloud. Welcome gentlemen, thank you. >> Thanks for having us. >> So you recently just last month announced the new service. It extends on the initial partnership with Microsoft Oracle interconnect with Azure, and you refer to this as a secure private link between the two clouds, it cross 11 regions around the world, under two milliseconds data transmission sounds pretty cool. It enables customers to run Microsoft applications against data stored in Oracle databases without any loss in efficiency or presumably performance. So we use this term supercloud to describe a service or sets of services built on hyper scale infrastructure that leverages the core primitives and APIs of an individual cloud platform, but abstracts that underlying complexity to create a continuous experience across more than one cloud. Is that what you've done? >> Absolutely. I think it starts at the top layer in terms of just making things very simple for the customer, right. I think at the end of the day we want to enable true workloads running across two different clouds where you're potentially running maybe the app layer in one and the database layer or the back in another. And the integration I think starts with, you know, making it ease of use. Right. So you can start with things like, okay can you log into your second or your third cloud with the first cloud provider's credentials? Can you make calls against another cloud using another cloud's APIs? Can you peer the networks together? Can you make it seamless? I think those are all the components that are sort of, they're kind of the ingredients to making a multi-cloud or supercloud experience successful. >> Oh, thank you for that, Karan. So I guess there's a question for Chris is I'm trying to understand what you're really solving for? What specific customer problems are you focused on? What's the service optimized for presumably it's database but maybe you could double click on that. >> Sure. So, I mean, of course it's database. So it's a super fast network so that we can split the workload across two different clouds leveraging the best from both, but above the networking, what we had to do do is we had to think about what a true multi-cloud or what you're calling supercloud experience would be it's more than just making the network bites flow. So what we did is we took a look as Karan hinted at right, is where is my identity? Where is my observability? How do I connect these things across how it feels native to that other cloud? >> So what kind of engineering do you have to do to make that work? It's not just plugging stuff together. Maybe you could explain a little bit more detail, the the resources that you had to bring to bear and the technology behind the architecture. >> Sure. I think, it starts with actually, what our goal was, right? Our goal was to actually provide customers with a fully managed experience. What that means is we had to basically create a brand new service. So, we have obviously an Azure like portal and an experience that allows customers to do this but under the covers, we actually have a fully managed service that manages the networking layer, the physical infrastructure, and it actually calls APIs on both sides of the fence. It actually manages your Azure resources, creates them but it also interacts with OCI at the same time. And under the covers this service actually takes Azure primitives as inputs. And then it sort of like essentially translates them to OCI action. So, we actually truly integrated this as a service that's essentially built as a PaaS layer on top of these two clouds. >> So, the customer doesn't really care or know maybe they know cuz they might be coming through, an Azure experience, but you can run work on either Azure and or OCI. And it's a common experience across those clouds. Is that correct? >> That's correct. So like you said, the customer does know that they know there is a relationship with both clouds but thanks to all the things we built there's this thing we invented we created called a multi-cloud control plane. This control plane does operate against both clouds at the same time to make it as seamless as possible so that maybe they don't notice, you know, the power of the interconnect is extremely fast networking, as fast as what we could see inside a single cloud. If you think about how big a data center might be from edge to edge in that cloud, going across the interconnect makes it so that that workload is not important that it's spanning two clouds anymore. >> So you say extremely fast networking. I remember I used to, I wrote a piece a long time ago. Larry Ellison loves InfiniBand. I presume we've moved on from them, but maybe not. What is that interconnect? >> Yeah, so it's funny you mentioned interconnect you know, my previous history comes from Edge PC where we actually inside OCI today, we've moved from Infinite Band as is part of Exadata's core to what we call Rocky V two. So that's just another RDMA network. We actually use it very successfully, not just for Exadata but we use it for our standard computers that we provide to high performance computing customers. >> And the multi-cloud control plane runs. Where does that live? Does it live on OCI? Does it live on Azure? Yes? >> So it does it lives on our side. Our side of the house as part of our Oracle OCI control plane. And it is the veneer that makes these two clouds possible so that we can wire them together. So it knows how to take those Azure primitives and the OCI primitives and wire them at the appropriate levels together. >> Now I want to talk about this PaaS layer. Part of supercloud, we said to actually make it work you're going to have to have a super PaaS. I know we're taking this this term a little far but it's still it's instructive in that, what we surmised was you're probably not going to just use off the shelf, plain old vanilla PaaS, you're actually going to have a purpose built PaaS to solve for the specific problem. So as an example, if you're solving for ultra low latency, which I think you're doing, you're probably no offense to my friends at Red Hat but you're probably not going to develop this on OpenShift, but tell us about that PaaS layer or what we call the super PaaS layer. >> Go ahead, Chris. >> Well, so you're right. We weren't going to build it out on OpenShift. So we have Oracle OCI, you know, the standard is Terraform. So the back end of everything we do is based around Terraform. Today, what we've done is we built that control plane and it will be API drivable, it'll be drivable from the UI and it will let people operate and create primitives across both sides. So you can, you mentioned developers, developers love automation, right, because it makes our lives easy. We will be able to automate a multi-cloud workload from ground up config is code these days. So we can config an entire multi-cloud experience from one place. >> So, double click Chris on that developer experience. What is that like? They're using the same tool set irrespective of, which cloud we're running on is, and it's specific to this service or is it more generic, across other Oracle services? >> There's two parts to that. So one is the, we've only onboarded a portion. So the database portfolio and other services will be coming into this multi-cloud. For the majority of Oracle cloud, the automation, the config layer is based on Terraform. So using Terraform, anyone can configure everything from a mid-tier to an Exadata, all the way soup to nuts from smallest thing possible to the largest. What we've not done yet is integrated truly with the Azure API, from command line drivable. That is coming in the future. It is on the roadmap, it is coming. Then they could get into one tool but right now they would have half their automation for the multi-cloud config on the Azure tool set and half on the OCI tool set. >> But we're not crazy saying from a roadmap standpoint that will provide some benefit to developers and is a reasonable direction for the industry generally but Oracle and Microsoft specifically. >> Absolutely. I'm a developer at heart. And so one of the things we want to make sure is that developers' lives are as easy as possible. >> And is there a metadata management layer or intelligence that you've built in to optimize for performance or low latency or cost across the respective clouds? >> Yeah, definitely. I think, latency's going to be an important factor. The service that we've initially built isn't going to serve, the sort of the tens of microseconds but most applications that are sort of in, running on top of the enterprise applications that are running on top of the database are in the several millisecond range. And we've actually done a lot of work on the networking pairing side to make sure that when we launch these resources across the two clouds we actually picked the right trial site. We picked the right region we pick the right availability zone or domain. So we actually do the due diligence under the cover so the customer doesn't have to do the trial and error and try to find the right latency range. And this is actually one of the big reasons why we only launch the service on the interconnect regions. Even though we have close to, I think close to 40 regions at this point in OCI, this service is only built for the regions that we have an interconnect relationship with Microsoft. >> Okay, so you started with Microsoft in 2019. You're going deeper now in that relationship, is there any reason that you couldn't, I mean technically what would you have to do to go to other clouds? You talked about understanding the primitives and leveraging the primitives of Azure. Presumably if you wanted to do this with AWS or Google or Alibaba, you would have to do similar engineering work, is that correct? Or does what you've developed just kind of poured over to any cloud? >> Yeah, that's absolutely correct Dave. I think Chris talked a lot about the multi-cloud control plane, right? That's essentially the control plane that goes and does stuff on other clouds. We would have to essentially go and build that level of integration into the other clouds. And I think, as we get more popularity and as more products come online through these services I think we'll listen to what customers want. Whether it's, maybe it's the other way around too, Dave maybe it's the fact that they want to use Oracle cloud but they want to use other complimentary services within Oracle cloud. So I think it can go both ways. I think, the market and the customer base will dictate that. >> Yeah. So if I understand that correctly, somebody from another cloud Google cloud could say, Hey we actually want to run this service on OCI cuz we want to expand our market. And if TK gets together with his old friends and figures that out but then we're just, hypothesizing here. But, like you said, it can go both ways. And then, and I have another question related to that. So, multi clouds. Okay, great. Supercloud. How about the Edge? Do you ever see a day where that becomes part of the equation? Certainly the near Edge would, you know, a Home Depot or Lowe's store or a bank, but what about the far Edge, the tiny Edge. Can you talk about the Edge and where that fits in your vision? >> Yeah, absolutely. I think Edge is a interestingly, it's getting fuzzier and fuzzier day by day. I think, the term. Obviously every cloud has their own sort of philosophy in what Edge is, right. We have our own. It starts from, if you do want to do far Edge, we have devices like red devices, which is our ruggedized servers that talk back to our control plane in OCI. You could deploy those things unlike, into war zones and things like that underground. But then we also have things like clouded customer where customers can actually deploy components of our infrastructure like compute or Exadata into a facility where they only need that certain capability. And then a few years ago we launched, what's now called Dedicated Region. And that actually is a different take on Edge in some sense where you get the entire capability of our public commercial region, but within your facility. So imagine if a customer was to essentially point a finger on a commercial map and say, Hey, look, that region is just mine. Essentially that's the capability that we're providing to our customers, where if you have a white space if you have a facility, if you're exiting out of your data center space, you could essentially place an OCI region within your confines behind your firewall. And then you could interconnect that to a cloud provider if you wanted to, and get the same multi-cloud capability that you get in a commercial region. So we have all the spectrums of possibilities here. >> Guys, super interesting discussion. It's very clear to us that the next 10 years of cloud ain't going to be like the last 10. There's a whole new layer. Developing, data is a big key to that. We see industries getting involved. We obviously didn't get into the Oracle Cerner acquisitions. It's a little too early for that but we've actually predicted that companies like Cerner and you're seeing it with Goldman Sachs and Capital One they're actually building services on the cloud. So this is a really exciting new area and really appreciate you guys coming on the Supercloud22 event and sharing your insights. Thanks for your time. >> Thanks for having us. >> Okay. Keep it right there. #Supercloud22. We'll be right back with more great content right after this short break. (lighthearted marimba music)

(upbeat music) >> Welcome back to Supercloud22, #Supercloud22, this is Dave Vellante. In 2019, Oracle and Microsoft announced a collaboration to bring interoperability between OCI, Oracle Cloud Infrastructure and Azure clouds. It was Oracle's initial foray into so-called multi-cloud and we're joined by Karan Batta, who's the vice president for product management at OCI, and Kris Rice, is the vice president of software development at Oracle database. And we're going to talk about how this technology's evolving and whether it fits our view of what we call, Supercloud. Welcome, gentlemen. Thank you. >> Thanks for having us. >> Thanks for having us. >> So you recently just last month announced the new service. It extends on the initial partnership with Microsoft Oracle Interconnect with Azure, and you refer to this as a secure private link between the two clouds across 11 regions around the world. Under two milliseconds data transmission, sounds pretty cool. It enables customers to run Microsoft applications against data stored in Oracle databases without any loss in efficiency or presumably performance. So we use this term Supercloud to describe a service or sets of services built on hyperscale infrastructure that leverages the core primitives and APIs of an individual cloud platform, but abstracts that underlying complexity to create a continuous experience across more than one cloud. Is that what you've done? >> Absolutely. I think, you know, it starts at the, you know, at the top layer in terms of, you know, just making things very simple for the customer, right. I think at the end of the day we want to enable true workloads running across two different clouds, where you're potentially running maybe the app layer in one and the database layer or the back in another, and the integration I think, starts with, you know, making it ease of use. Right? So you can start with things like, okay can you log into your second or your third cloud with the first cloud provider's credentials? Can you make calls against another cloud using another cloud's APIs? Can you peer the networks together? Can you make it seamless? I think those are all the components that are sort of, they're kind of the ingredients to making a multi-cloud or Supercloud experience successful. >> Oh, thank you for that, Karan. So, I guess as a question for Kris is trying to understand what you're really solving for, what specific customer problems are you focused on? What's the service optimized for presumably its database but maybe you could double click on that. >> Sure. So, I mean, of course it's database so it's a super fast network so that we can split the workload across two different clouds leveraging the best from both, but above the networking, what we had to do is we had to think about what a true multi-cloud or what you're calling Supercloud experience would be. It's more than just making the network bytes flow. So what we did is, we took a look as Karan hinted at, right? Is where is my identity? Where is my observability? How do I connect these things across how it feels native to that other cloud? >> So what kind of engineering do you have to do to make that work? It's not just plugging stuff together. Maybe you could explain in a little bit more detail, the resources that you had to bring to bear and the technology behind the architecture? >> Sure. >> I think, you know, it starts with actually, you know, what our goal was, right? Our goal was to actually provide customers with a fully managed experience. What that means is we had to basically create a brand new service. So, you know, we have obviously an Azure like portal and an experience that allows customers to do this but under the covers, we actually have a fully managed service that manages the networking layer that the physical infrastructure, and it actually calls APIs on both sides of the fence. It actually manages your Azure resources, creates them, but it also interacts with OCI at the same time. And under the covers this service actually takes Azure primitives as inputs, and then it sort of like essentially translates them to OCI action. So, so we actually truly integrated this as a service that's essentially built as a PaaS layer on top of these two clouds. >> So, so the customer doesn't really care, or know, maybe they know, coz they might be coming through, you know, an Azure experience, but you can run work on either Azure and or OCI, and it's a common experience across those clouds, is that correct? >> That's correct. So, like you said, the customer does know that they know there is a relationship with both clouds but thanks to all the things we built there's this thing we invented, we created called a multi-cloud control plane. This control plane does operate against both clouds at the same time to make it as seamless as possible so that maybe they don't notice, you know, the power of the interconnect is extremely fast networking, as fast as what we could see inside a single cloud, if you think about how big a data center might be from edge to edge in that cloud. Going across the interconnect makes it so that that workload is not important that it's spanning two clouds anymore. >> So you say extremely fast networking. I remember I used to, I wrote a piece a long time ago. Hey, Larry Ellison loves InfiniBand. I presume we've moved on from them, but maybe not. What is that interconnect? >> Yeah, so it's funny, you mentioned interconnect, you know, my previous history comes from HPC where we actually inside inside OCI today, we've moved from, you know, InfiniBand as its part of Exadata's core, to what we call RoCEv2. So that's just another RDMA network. We actually use it very successfully, not just for Exadata but we use it for our standard computers, you know, that we provide to, you know, high performance computing customers. >> And the multi-cloud control plane, runs... Where does that live? Does it live on OCI? Does it live on Azure? Yes? >> So it does. It lives on our side. >> Yeah. >> Our side of the house, and it is part of our Oracle OCI control plane. And it is the veneer that makes these two clouds possible so that we can wire them together. So it knows how to take those Azure primitives and the OCI primitives and wire them at the appropriate levels together. >> Now I want to talk about this PaaS layer. Part of Supercloud, we said, to actually make it work you're going to have to have a super PaaS. I know, we're taking this term a little far but it's still, it's instructive in that, what we, what we surmised was, you're probably not going to just use off the shelf, plain old vanilla PaaS, you're actually going to have a purpose built PaaS to solve for the specific problem. So, as an example, if you're solving for ultra low latency, which I think you're doing, you're probably, no offense to my friends at Red Hat, but you're probably not going to develop this on OpenShift, but tell us about that, that PaaS layer or what we call the super PaaS layer. >> Go ahead, Kris. >> Well, so you're right. We weren't going to build it out on OpenShift. So we have Oracle OCI, you know, the standard is Terraform. So the back end of everything we do is based around Terraform. Today, what we've done, is we built that control plane and it will be API drivable. It'll be drivable from the UI and it will let people operate and create primitives across both sides. So you can, you, you mentioned developers developers love automation, right? Because it makes our lives easy. We will be able to automate a multi-cloud workload, from ground up, Config is code these days. So we can Config an entire multi-cloud experience from one place. >> So, double click Kris on that developer experience, you know, what is that like? They're using the same tool set irrespective of, you know, which cloud we're running on is, is it and it's specific to this service or is it more generic across other Oracle services? >> There's two parts to that. So one is the, we've only onboarded a portion. So the database portfolio and other services will be coming into this multi-cloud. For the majority of Oracle cloud the automation, the Config layer is based on Terraform. So using Terraform, anyone can configure everything from a mid tier to an Exadata, all the way soup to nuts from smallest thing possible to the largest. What we've not done yet is is integrated truly with the Azure API, from command line drivable, that is coming in the future. It will be, it is on the roadmap. It is coming, then they could get into one tool but right now they would have half their automation for the multi-cloud Config on the Azure tool set and half on the OCI tool set. >> But we're not crazy saying from a roadmap standpoint that will provide some benefit to developers and is a reasonable direction for the industry generally but Oracle and, and, and Microsoft specifically? >> Absolutely. I'm a developer at heart. And so one of the things we want to make sure is that developers' lives are as easy as possible. >> And, and is there a Metadata management layer or intelligence that you've built in to optimize for performance or low latency or cost across the, the respective clouds? >> Yeah, definitely. I think, you know, latency's going to be an important factor. You know, the, the service that we've initially built isn't going to serve, you know, the sort of the tens of microseconds but most applications that are sort of in, you know, running on top of, the enterprise applications that are running on top of the database are in the several millisecond range. And we've actually done a lot of work on the networking pairing side to make sure that when we launch, when we launch these resources across the two clouds we actually pick the right trial site, we pick the right region, we pick the right availability zone or domain. So we actually do the due diligence under the cover, so the customer doesn't have to do the trial and error and try to find the right latency range, you know, and this is actually one of the big reasons why we only launched this service on the interconnect regions. Even though we have close to, I think, close to 40 regions at this point in OCI, this, this, this service is only built for the regions that we have an interconnect relationship with with Microsoft. >> Okay. So, so you've, you started with Microsoft in 2019 you're going deeper now in that relationship, is there is there any reason that you couldn't, I mean technically what would you have to do to go to other clouds? Would you just, you talked about understanding the primitives and leveraging the primitives of Azure. Presumably if you wanted to do this with AWS or Google or Alibaba, you would have to do similar engineering work, is that correct? Or does what you've developed just kind of pour it over to any cloud? >> Yeah, that's, that's absolutely correct, Dave, I think, you know, Kris talked a lot about kind of the multi-cloud control plane, right? That's essentially the, the, the control plane that goes and does stuff on other clouds. We would have to essentially go and build that level of integration into the other clouds. And I think, you know, as we get more popularity and as as more products come online through these services I think we'll listen to what customers want, whether it's you know, maybe it's the other way around too, Dave maybe it's the fact that they want to use Oracle cloud but they want to use other complimentary services within Oracle cloud. So I think it can go both ways. I think, you know, kind of the market and the customer base will dictate that. >> Yeah. So if I understand that correctly, somebody from another cloud Google cloud could say, "Hey, we actually want to run this service on OCI coz we want to expand our market and..." >> Right. >> And if TK gets together with his old friends and figures that out but we're just, you know, hypothesizing here, but but like you said, it can, can go both ways. And then, and I have another question related to that. So you multi-clouds. Okay, great. Supercloud. How about the edge? Do you ever see a day where that becomes part of the equation? Certainly the, the near edge would, you know, a a home Depot or a Lowe's store or a bank, but what about like the far edge, the tiny edge. Do, do you, can you talk about the edge and and where that fits in your vision? >> Yeah, absolutely. I think edge is a interestingly, it's a, it's a it's getting fuzzier and fuzzier day by day. I think there's the term, you know, we, obviously every cloud has their own sort of philosophy in what edge is, right? We have our own, you know, it starts from, you know, if you if you do want to do far edge, you know, we have devices like red devices, which is our ruggedized servers that that talk back to our, our control plane in OCI you could deploy those things in like, you know, into war zones and things like that underground. But then we also have things like Cloud@Customer where customers can actually deploy components of our infrastructure, like Compute or Exadata into a facility where they only need that certain capability. And then a few years ago we launched, you know, what's now called Dedicated Region. And that actually is a, is a different take on edge in some sense where you get the entire capability of our public commercial region, but within your facility. So imagine if, if, if a customer was to essentially point to, you know, point to, point a finger on a commercial map and say, "Hey, look, that region is just mine." Essentially, that's the capability that we're providing to our customers, where if you have a white space if you have a facility if you're exiting out of your data center space you could essentially place an OCI region within your confines behind your firewall. And then you could interconnect that to a cloud provider if you wanted to. and get the same multi-cloud capability that you get in a commercial region. So we have all the spectrums of possibilities there. >> Guys, super interesting discussion. It's very clear to us that the next 10 years of cloud ain't going to be like the last 10. There's a whole new layer developing. Data is a big key to that. We see industries getting involved. We obviously didn't, didn't get into the Oracle Cerner acquisitions a little too early for that but we we've actually predicted that companies like Cerner and you've seen it with Goldman Sachs and Capital One, they're actually building services on the cloud. So this is a really exciting new area and I really appreciate you guys coming on the Supercloud22 event and sharing your insights. Thanks for your time. >> Thank very much. >> Thank very much. >> Okay. Keep it right there. #Supercloud22. We'll be right back with more great content right after this short break. (upbeat music)

>> Thinking back over the past 15 years of the modern cloud computing era we were first told that cloud was only for startups. It was for experiments, entire kickers. No IT executive would ever move production workloads or strategic data into the cloud. No financial services firm is another example would ever move anything into the cloud. Multi-cloud then emerged as a symptom of multi-vendor or of mergers and acquisitions or both. Fast forward now to 2022 and customers clearly want to take advantage of the best services that each cloud offers. For example, Azure for Microsoft apps, Amazon for IS, Google cloud for AI, Oracle for database, et cetera. However, this approach requires expertise in each cloud's primitives, tools and APIs and it puts the burden on customers to integrate apps and workloads across clouds, which increases cost, it exposes security risks and it creates time to market friction. The future of cloud is no longer just on-prem to cloud or so-called hybrid, but cloud to cloud. What many call multi-cloud and at the cube, we like to think beyond the conventional view of multi-cloud, and it's why we use the term super cloud as a metaphor for cross cloud services that are purpose built to solve a specific problem. While at the same time leveraging the best that various cloud providers have to offer. Karan Batta is the vice president of product management at OCI for Oracle and Kris Rice is the vice president of software development at Oracle database, and both are joining me in this cube conversation to discuss how Oracle and Microsoft are helping customers address cross cloud integration issues, making it possible for customers to use popular Azure based tools and Oracle databases and what the firm's claim is a simplified, secure and more facile experience, effectively making two clouds appear as one to developers and, and users. Gentlemen, welcome. Thanks for coming on the cube. >> Thanks for having me, Dave >> Karan, let's start with the news. What are you announcing? Why is it important to each company and what does it mean for your customers? >> Yeah, absolutely. Thanks for having me, Dave. I think, you know, what, what I can tell you is Microsoft and Oracle actually share a massive enterprise customer base. The same customers that are using Office 365 are also the same customer that are storing their critical, mission critical data on Oracle database. So we have thousands of customers that we share jointly and many of them use all sorts of different products from both technology companies. And, you know, multi-cloud, as you, as you sort of rightly pointed out has become the right approach for a lot of our customers to be able to run applications across different cloud providers in a very simplistic manner. You know, that's why we're, you know, with this new announcement we're reducing the complexity of connecting these things together. You know, all of the platform level capabilities, the networking capabilities, the identity management of it, you know, we're calling this new service Oracle database service for Microsoft Azure, and it really brings together a, a cohesive Azure like experience for Oracle customers. It's, you know, it's, it's going to be a new way to actually deploy multi-cloud applications. >> How is this service different from what the Oracle interconnect for Azure partnership that you announced pre pandemic? I think it was 2019. >> Right, right, right. So almost two years ago, you know, we announced this partnership with Microsoft that essentially interconnects the two data center regions from, from Azure and from Oracle. And, you know, it, it provided a great opportunity for customers to, to start their multi-cloud journey by making things like data transfer fees free, et cetera. And now we're close to 11 regions globally, you know, for those interconnected regions. The feedback that we got from customers was, you know, it was a great step in the right direction, but they needed more. And so this experience essentially builds on top of that interconnect, the physical interconnect on the data center side by giving customers an Azure like experience that allows them to basically deploy Oracle databases in a, in a very cohesive fashion with their Azure applications. It also gives them things like, you know, joint support, it gives them things like, you know, joint billing data, et cetera. But it basically allows them to get a first class experience for Oracle database services, you know, across the two clouds. >> It's interesting. I mean, I think back to the history of the industry, you know, before Oracle acquired Sun it would work with every hardware company then of course, you know, had its own hardware. And now it's working with, with Microsoft, who's in essence is a platform, you know, infrastructure company. So it's, it's quite a, quite a journey. Chris, I wonder, wonder if we could bring you into the conversation. What Oracle databases can Azure customers access now? Where, where does autonomous fit? Is that part of the package? >> Yeah, absolutely. So the, the initial offering is going to have all flavors of the Oracle database cloud. So that includes what we call now, the base database, which is database in a VM, the workhorse of the excess CS. So if you truly need the the extra horsepower of the exit data machine and of course it's going to include autonomous right out of the gate. So for customers that want to kick the tires on an Oracle database link with Azure there's no faster path than using autonomous. >> Yeah, so a lot of integration that you guys have done. Well, how does this service compare to other, you know, customers like to compare, they're always talking about their, their choices. How does it compare to others? How, what is the cost associated with this? What can you tell us? >> So from a cost stance, there there's no extra cost. So the only cost is on the base service. So if you get the autonomous, the base database, the exit data, your cost is in that base service. And we include all this plumbing that we've done to make it work best with Azure. And that includes wiring the metrics the logs, the vent home, the audit records to the Azure side of the house. >> And, and, and what what other things are like this out there? Can you share with us? What should customers, you know, compare this to? >> So the majority of what customers have done so far is it, it is DIY. So multi-cloud to date has been very DIY. Anything could be done that we've done. However, customers that have to roll up their sleeves they'd have to learn both clouds, learn the nomenclature of both clouds, they'd have to learn the networking infrastructure and they'd really have to roll their sleeves up and DIY it. What we've done is we've, we've done all that work for them. So it's as simple as a few mouse clicks and the two clouds can be talking together. >> Thank you, okay. Karan, you, you ever see the movie good morning Vietnam and they redact out all the, all the, like the words in the news that they didn't want, want read on the news. And so we hear Microsoft and Oracle, they're talking about multi-cloud, Google sort of talks about unifying cross cloud developer experiences with, with Antos. But when you go, when you go to like reinvent the word multi-cloud is redacted, like the movie. Do you anticipate customers are going to push more from multi-cloud in the future? What are you hearing? >> Yeah, absolutely. I think, I think customers are going to demand this of their cloud providers in the future. I think these are going to be table stakes moving forward. You know, as, as you rightly pointed out, Dave, I think, you know, customers and, and and actually cloud providers are focused on mostly transition from on-prem to the cloud. And I think in the future, you know, once everybody's picked their first cloud provider it's going to be, you know, the focus is going to shift from that to the interoperability across these two clouds or, or multiple clouds. You know, customers will want to have leverage against other cloud providers. Customers will want to pick the best of breed, complimentary services, et cetera, and also have, you know, decisions based on economics, right? So I think, you know, there's going to be a massive acceleration of customers want the support from, from all of their cloud providers. You know, which is why we're basically simply listening to customer feedback. And, you know, as mentioned earlier, we share so many different customers together it totally made sense for Microsoft and Oracle to start investing in it. This is not the entire answer. I think it's start of this journey in, in the future. >> Yeah, it's going to be interesting to see how this plays out. You know, I never say never with, with the hyperscalers or any large technology company. I, I wonder Karan, if we could stay with you. Can you give us some practical examples of, of what this service means for customers? How it's going to help them do something that they couldn't do before? What should we be focused on? >> Yeah, absolutely. I think, you know, I think it opens up a whole set of new possibilities. You know, I, I mentioned earlier kind of made a statement where, you know, the world's data kind of lives on Oracle databases. It's, it's the core of, of any mission critical data today. It's still the most popular database use in, in the world. And so, you know, customers want to be able to modify they want to be able to extract more information and and get more knowledge out of their data. And this opens up the possibility where you can use, you can have access to that Oracle database from Azure and you're able to connect it to all the complimentary services which allow you to extract more knowledge or, or insight out of that data. So whether you're moving it into, let's say Azure synapse analytics to do analytics workloads or whether you're moving it to the HUD cluster using Azure HD insight, or you're simply just looking at the data in different forms and factors through power BI. I think it opens up a whole new set of possibilities you just couldn't do it before. On the second hand, it also helps you modernize your existing on-premise estate of Oracle. So we have the largest backs, the largest financial services customers, the largest government customers running the largest exit data footprint on premise. It helps you modernize that into the cloud and then, and use complimentary services from Azure. >> Got it. Chris, what's the support model look like for this new service? You know, who do I, whose throat do I choke? >> I was going to say, so you brought us back to when we had multiple vendors in the vendors we've all lived through it, right. Vendors pointed fingers at each other. So, keeping that in mind, what we've done is we have a collaborative plan with Microsoft in place. So building on the, the interconnect from 2019 we have that collaborative support model. So right in this new console that we've built you can log a ticket and immediately both sides will be aware of the context and what's going on so that we can resolve those problems and avoid the finger pruning of vendor at vendor. >> Okay, great. So if somebody pick up a broom and, and start sweeping and fix the problem, I love it. To both of you guys, maybe you could kind of riff a little bit on the future. I, I mean, we use this term super cloud, which is, you know, cross multiple clouds so you're doing that. And we envision, you know, this this wonderful globally distributed system where you're not even thinking about the underlying infrastructure. Are you considering partnering with other major cloud providers to offer similar services? Or are you going to go sort of deeper with, with Azure? What's your feeling on that? >> I think, you know, I think the the capability here that we've built isn't specific to Azure, for sure. I think there's absolutely possibility of, of, you know, working with other clouds in the future. I think, you know, we'll continue to sort of listen to our feedback from the, from our largest customers. You know, and if the market demands, you know, it's, it's, it's going to be, as I said, table stakes. And, you know, as I said earlier, and and I think It'll be in the best interest of all the cloud providers to just work together in the future. >> And, and Dave, to go back on the other half of your question, are we going to go deeper? We are going to be going deeper. So today we've gone far enough that like I said, metrics logs, those things are flowing. We're also in progress of looking at the rest of the portfolio in Azure and seeing which things can and should integrate more tightly with OCI. So as Karan said broader, but also deeper at the same time. >> Great, thank you. But my last question is, you know, we, again, we use this term super cloud to, to, to me anyway and us multi-cloud has largely been running, you know, on different clouds, it's, it's sort of a symptom, just kind of the way things shook out. And maybe this, maybe super cloud is what multi-cloud should be, but, but what do you think are the key ingredients that make multi-cloud real, lots of people are talking about multi-cloud what, what makes it tangible? >> I think, you know, to, to begin with, I think it's, it's, it's removing the complexity of learning new clouds, right? I think that's the biggest challenge that customers have is you've you've already picked one cloud, you've, you've, you've trained your, your, your employees, you've trained your developers and your application, you know, engineers and learning a new cloud, onboarding a new cloud is an extensive challenge and, and, you know, requires a lot of time and effort. And I think, I think what the other cloud providers can do is actually make sure that they provide these experiences that office gate all of the guts and all of the plumbing under the covers so that the customer doesn't have to learn new things. I think they have, they can focus on their business value which is actually running the app and running the database. I think they can sort of leave the infrastructure component to the cloud providers to actually have the right interoperability, the right APIs, et cetera. So I think the experience is going to be critical moving forward. >> Kris, anything you'd add to that? Bring us home if you would. >> The things I would add is back to observability and manageability. So today a lot of customers consider themselves multi-cloud if they're leveraging two clouds. What we are truly talking about is a multi-cloud workload where a compute node on cloud A is talking to a database on Oracle, things like that. So then you get into the observability of the stack so that you can monitor and react to how the things are going. So I think it has to go a, a hair higher in that these, these layers of observing the entire multi-cloud experiences in one place. >> That's great guys. Thanks so much for coming to The Cube and, and share. Congratulations on the progress. I, I love that we have you guys back and we can see how you're moving forward, collaborating, you know, customers, it's a win-win win so appreciate your time. >> Absolutely. >> Absolutely. >> All right. And thank you for watching. This is Dave Vellante for The Cube. We'll see you next time.