>>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.

>>Mhm Yeah, this is Dave valentin. I'd like to welcome you back to the cubes coverage of couch base connect online with the theme of this event is modernized now and one of the big announcements is Capella which of course as you all undoubtedly know is the brightest star in the constellation Auriga, which is latin for charioteer, yep, you can find that in the constellation of that constellation of the night sky in late february, early March in the northern hemisphere. So with that little tidbit, I'd like to welcome in scott Anderson to the cube, who is the senior vice president of product management and business operations. That couch base scott welcome. Good to see you. >>Thank you very much. Thanks for having me. >>That's our pleasure. So you've launched couch based cappella if I understand correctly, it's built on couch based server seven which he launched just a few months ago in the middle of the summer. Can you give us an overview of Capella? >>Yeah, absolutely. So couch based Capellas are fully managed databases. Service for enterprise applications. One of the goals of launching Capella and our databases is service offering that we just announced today is about increasing the accessibility of couch base so it's about making it easy for a developer or an enterprise to get up and running in just a few clicks in a couple of minutes Um and about making it more affordable and accessible through the development phase through the test phase, the production phase. So really it's about ease of use having the right offerings aligned to the phase of development that customers in and eventually into the production of their enterprise application leveraging capella and couch based Server seven. >>So let me ask you, I I went pretty deep with ravi on the, on the technical side and I want to understand what makes Capella different from some of the competitive offerings. Is it the sort of the fundamentals that I learned from Ravi about how you guys have have have really done an awesome focus on on on sequel but been able to maintain acid compliance deal with distributed architectural challenges and then bringing that over to database as a service. Is that the fundamental, what are some of the other differentiators? >>Yeah, that that is the fundamental, we have an amazing platform that Roddy and our core engineering team built and we've talked about that and I think Robbie mentioned that the ease of sequel and applying that to a documented oriented database, then combining some of those capabilities with the ease of use, the ability that you can get up and running, signing up for our free trial couple minutes later you've got a database endpoint that is fully managed by couch base. And so we're doing the monitoring, we're doing alerting, we have calls to action based off what events are occurring within the database environment, ensuring it's always available as well as doing kind of the mundane tasks of backup and recovery, uh scaling the environment, upgrades and so forth. So it's really about ease of use, making it um leveraging are incredibly robust, broad platform um and then making that in different consumable model for our customers and developers and getting started really easily. The other thing that we have done is really leverage the best practices over the last 10 or 11 years of some of the largest enterprises in the world using couch based for the mission critical applications. So we've codified those best practices and that's how we keep that service, high performance, always on highly available. And that's one of the core value propositions that were able to bring with Capella. It's really about management capability, global visibility of your clusters coupled with what we believe is the best no sequel database in the marketplace today. >>What about what about cost, total cost of ownership as you scale a lot of times when you scale out, you get dis economies of scale, it's kind of like, you know, you get that negative curve, uh what are you seeing? >>Yeah, we've done a third party benchmark studies which have proven out how we are able to literally scale the environment uh and continue on that curve as you add notes, you're getting that incremental performance that you would expect. The other thing that we do that's really unique within couch bases are multidimensional scaling and this allows you to place our services, things like data index, query, full text search indexes and analytics, you can co locate those on single nodes within a cluster or you can have dedicated notes for each one of those services. The reason that is important is you get work line isolation for those specific services within our cluster. The other thing that you can do is you can match the compute infrastructure to the needs of each one of those services. So some services like query are much more core, compute intensive and that allows you to have a specific instance type that is optimized for that, reducing your costs, indexes where you want very fast performance, you may want to have a higher amount of memory relative to the number of course. So that ability to mix and match the infrastructure with an existing cluster allows us to lower overall costs. That coupled with their blazing fast performance with our in memory architecture allows people to get incredible performance at scale. Um, what we've proven out in the study that I mentioned earlier is we have that linear scalability and you're able to do more for less at the end of the day, you're getting more operations per second per dollar if you want to use that as a metric. >>Got it. Thank you for that. What do customers need to think about when they want to get started with Capela? How difficult is it for people to jump in? >>It is incredibly simple. It's as simple as going to couch base dot com clicking on start your free trial, You're going to that free trial, you provide a minimal set of information for us and it's literally a few clicks and you're going to have a database endpoint within three minutes and that's really been a foundation of, of what we've been focused on over the last 6-9 months is removing any friction we can in the process because our goal is to give a tremendous user experience and get people up and running as quickly as possible. So we're really, really proud of that. And then from a paid offering perspective, we have a number of offerings which are really aligned to the needs of each customer, some individuals who want a larger cluster and they want to be able to pay for that. We've optimized service levels around that in terms of level support and the features that we think are appropriate for a dev cycle, a test cycle and then into production and lastly we will be announcing a number of promotional starter pack bundles, really trying to couple the overall service that we have with Capella with some of our expertise, so helping new users get up and running in terms of things like index definitions, what's the best way to do document design and schema within within couch base. Our end goal is to match these services and bundles with the life cycle of application development. So in my development phase what's the offering for me as I move for production readiness, what services capabilities I need and then production and the ongoing if I expand my use. So we've been really focused on, how do we get people up up and running as quickly as possible and how do we get them to production as quickly as possible at the lowest total cost? >>That's nice. That's a nice accelerant for customers. Um, so as you heard upfront, I did a little research about the name Capella. How did you choose it and why? >>Well, one thing I learned early in my career is naming is not a strong suit of mine. I leave that to John or our chief marketing officer in the overall team. Um, we all have opinions, but I trust John and we went through, I think it was over 60 names, seven rounds of debate to come up with capella, but we want to name of strength. We like the alliteration couch, basic capella together. Um, one of the little facts may have tipped it over is I believe in latin, it means little goats. So we kind of played from the barriers. Always think to jerry rice goat, greatest of all time. So that was a nice play on that also. Um, but I leave it to them and really happy with the overall name, love the liberation, Love some of the hidden meanings within that. Um, and we're really, really excited about getting going. So you wouldn't want me to pick the name. Um, I get a vote. Um, but I would say my overall influence is a little bit lower than where john's is and matt cain, who I know you spoke with previously. >>I love it, jerry rice definitely is a little go because I'm from New England. So of course tom we think tom brady is the big goat. I >>know we've, I grew up in that joe Montana era, so maybe you can take that off line after this interview. We can have our own debate, but I guess super bowl trophies or the ultimate measure at the end of the day. >>Now I've got a little stat for you. So, so Capella is also one of the 88 modern constellations as adopted by the International Astronomical Union. I. E. Not one of the ancient constellations. Pretty clever. Right. >>Exactly. >>Scott is great to have you on the cube. Thanks so much. Really, >>thank you so much. >>All right. And thank you for watching. Thank you for watching. Our pleasure. Thank you much of the cubes coverage of couch based connect 2021. Keep it right there for more great content. Mm mhm