>>Okay. We're here at the cube covering Couchbase connect online 2021 modernized. Now this is Dave Vellante and I'm here with Couchbase CEO, Matt Kane. We just saw them at your keynote, blending out the journey to the modern enterprise. Thanks for taking some time with us. >>Hey, thanks, Dave. Great to see you again. Hope everything's well with you. >>Good. Thank you. You know, hanging in there. So look, the big themes from my standpoint, where it's not just about what I call paving the cow path. What I mean by that is just moving old to new, you know, that's good. And it's gonna allow you to simplify and be more agile. But the point I take away is you should also build a new capabilities, maybe share some of your thoughts and add some color, please, to those takeaways. >>I think that's a great takeaway, Dave. And when we think about this, we step back and we put ourselves in the shoes of our customers and whether it's retail customers or next generation financial services or healthcare providers, or what have you each and every one of our customers around the world are thinking about how to create better experiences for their customers. And Dave, we go through this every day, whether it's on our personal lives or in our professional lives, we expect our technology to help us and create better, highly interactive, personalized experiences via the applications that we leverage throughout the day. And you and I have probably access tens if not, hundreds of applications up to this point, uh, today. And we'll, we'll do that as we continue to go forward. And so if you think about, well, what are the challenges of these enterprises to create those experiences? >>Well, at the end of the day, they're writing applications and those applications need to draw upon massive amounts of data and to provide the experiences that we're talking about today. It's not just structured information, but it's unstructured information. And how do I put that together in a seamless way that I create real-time runtime experiences? Well, at the end of the day software, um, developers can, can write code to do anything, but on the critical path of all that is a database. And if you don't have a database that can serve these applications, you're dead in the water. And so as the enterprise thinks about building applications, they're constantly thinking about new capabilities. How can I provide a recommendation engine for Dave, or how can I ensure that the promotion fits the needs of him and his family when he's booking a particular trip, but at the same time, there's legacy applications that have been built and optimized for many, many years, that that are storing critical information and algorithms that need to be combined with those new capabilities to create the experience of people are after. >>And so when you really look at it from a database perspective, you have to modernize your application stack, but you also have to combine that with new capabilities. Now that's easier said than done. The challenge is to do at a database layer are fundamentally sophisticated and some of the most advanced computer science challenges that exist in all of technology. And that is what Couchbase is about. We have carefully architected a platform that bridges some of the best of relational technology with that of modern, no SQL technology in a single integrated platform that services not only enterprise architects, but application developers to provide the very experiences that you and I have come to expect, and that we're going to expect to increase as, as we go forward. So you're absolutely right. It is about putting those two things together. So is that, >>Is that w what you just described is that what you mean by multimodal two-part question? And then the second part is, are you seeing any industry patterns where that appears to be more relevant? >>So when we, when we talk about multimodal, Dave, we're very specific in, in what that means, and, and that's essentially taking a platform approach to data management. So how do we ensure that we have multiple ways to manage data inside of our platform? Couchbase is a key value cache or a document data store. We support, uh, acid transactions, and we've also added operational analytics. And so if you think about all of those modalities, a lot of application teams would think, well, do I need disparate solutions, uh, you know, to, to solve those problems. We think it's of fundamental importance as the modern database for enterprise applications, that we put that together in a single platform, because that's how applications want to be, uh, developed on top of that. We layer on additional services that developers can take advantage of to right, you know, these really rich, personalized, uh, applications. >>And so, as we think about our path forward and some of the market dynamics, we see one of the dynamics that we think is going to play out over the next few years is enterprises. Can't continue to proliferate point solutions for all these disparate problems that they solve. They need to bet on strategic solutions that are going to be platforms to support many of these needs as these go, as they go forward, particularly as they think about long-term total cost of ownership. And when we think about the modalities we're supporting and the enterprise applications we support, we want to ensure that we are a tool that can be leveraged for the right use cases, and then make sure that we have the connection points to other solutions that were not built and optimize for, to have a complete solution for our enterprise customers. So multi-modal layer consolidation platform approach. We think this is going to be absolutely critical as we get into the next chapters of the database transition. >>Great. Thank you for that. So you just described, you know, your UVP to me anyway, your unique value proposition. And I wonder if you could, in thinking about the market big waves that are occurring now, the hybrid work, digitization, the reliance on cloud and cloud migration, how does your unique value prop tie in if you will vector in to those trends that we also often talk about? >>Yeah. Great question, Dave. I appreciate you raising that. So what, what I was articulating, um, were some really important attributes of what may Couchbase Couchbase that were multimodal. We take a platform approach under the hood. Dave, we take great pride in the architectural approach that we have, um, up to this point in building that platform, uh, we're an in-memory shared nothing scale out cloud native architecture that has been designed for today and the future scale and performance. We've architected our platform to run anywhere. So enterprises enjoy the benefits of running in all major public clouds. They can run in private data centers and they can run all the way out to the edge in a single integrated platform with continuity between any point of that network. Topology, if I'm an active, active, active, fail over active, active, passive, any one of those configurations, that is the dependency of distributed applications. >>And we as users want the application to be up and running with the appropriate amount of data wherever. And whenever we are Couchbase has been built for the highest scale and performance to run in that distributed environment. With those modalities that I talked about now to increase, uh, our relevance in the enterprise. There are two personas that we think about a lot. One of them are the architects who are responsible for ensuring that things run in public clouds, that they scale and perform that they meet the SLS of the businesses they serve. But critically important. As you know, Dave is the role of application developers. They got to write killer apps. And so if you think about the needs of enterprise architects, scale performance, reliability, GDPR, CCPA security, those are really, really important. Developers are focused on flexibility, ease of use agility also really, really important, putting those together in an integrated platform. That's what makes Couchbase Couchbase. And there is no other vendor that can bring those capabilities tied to the themes of data, explosion, everything happening at the edge, a single platform that can leverage structured and unstructured information. When we talk about being ready for this moment and why we're so excited about our future and why you're hearing customers say the amazing things they are at our show, it's because of that unique architecture and, and the fact that Couchbase is truly differentiated as a modern database for enterprise applications for the future. >>You know, sometimes those things are counter poised, right? The architectural Providence, and the need for developer agility. That is a nontrivial challenge. Um, in, in one the computer science challenge that obviously you're focused on your big news here, uh, at the show is Couchbase Capella, Capella, by the way, as the brightest star in the constellation, or I go for those of you space nuts. Well, what are the critical aspects of Capella related to Couchbase's cloud strategy? And what does this announcement mean for your customers, Matt? Yeah, >>We couldn't be more excited about a Capella and I'd like to take a moment to congratulate the teams that have been working so hard at Couchbase to, to get to this moment. Um, also want to thank our customers for all the input, uh, that, that we take very seriously. And in thinking through our innovation, um, is we think about all the things we've talked about up to this point. Those are fundamentally important. And we think about the capability of a database that enterprises need. What we also spend a lot of time thinking about is how do customers consume all of that capability, right? And, and enterprises want freedom of choice on how they consume deploy, run, and manage their database for a lot of our customers, they're very happy leveraging our platform and managing that. And they're very diverse, very customized, specific environments, but there are a lot of customers that want us to take over the management and the operation of the database. >>They want the fastest path to D developer, agility and productivity, uh, and they want the best TCO relative to other databases of service offerings. And that is exactly what we have provided with Couchbase Capella. So customers can now come to us, they're up and running with the best database in the industry. Self-serve easy to use up and going, you know, the, the, the most simple experience and the fastest path to value, but that TCO point is fundamentally important. And what's interesting the way we've architected this, the more you scale with Couchbase Capella, the better the TCO gets. And I think that demonstrates our focus on enterprise, the mission critical nature of, of the applications that we support. Um, but you know, we're, we're really excited about Capella. We think it's going to be a great experience for our existing customers, our new customers, um, along with the announcement of the product today, you've heard some things about some of the packaging and ways in which developers can try out the solution in a really unique and cool way. We're providing other great experiences for developers on technical integrations and ideas from other customers on how to take advantage of the Couchbase platform. So we're thinking pretty holistically about consumption, uh, experience. Uh, and again, the fact that it's built on a kind of the foundation of, of Couchbase server seven oh, and, and our, our core platform with all the advantages that that brings with it. Uh, we're, we're pretty excited about the, uh, the announcement and all that that has for, for the company in front of us. So let's on >>For a minute and I want to double click on the, how you see the uniqueness of Capella. So when I think about Couchbase's heritage, the idea of next-generation not, not only SQL database, the acid properties that you talked about, the scale and the performance required for mission critical workloads and your focus on sequel fluency, these tenants of differentiated Couchbase, is it sort of the same kind of approach for Capella and what specifically differentiates Capella in your mind from the spate of other database databases, a service offerings that are out there in the marketplace? >>Well, look at it. When, when enterprises are thinking about applications, particularly the applications that they're running their business on, I like to say the good enough is not a viable strategy for the database. And what that means is you've got to have high performance, you've got to have scale, you've got to have, you know, distributed, uh, attributes. We believe fundamentally that you need to go cloud to edge. Um, that's going to be paramount and we're going to continue to innovate on our core database. So to take all of that power and then put it in a consumption model, as easy as Capella, I mean, Dave, we now have people being able to get up and running in a matter of minutes and, and they're writing applications, uh, on Capella leveraging the full power and breadth of all the capabilities, uh, in, in Couchbase. And going back to something that we talked about earlier dynamics in, in the industry will enterprise is really need to think about total cost of ownership. >>So how am I innovating and solving some of my most fundamental application challenges, but mindful of, you know, the cost and the return of that over time for us to come out with the highest performing database at the lowest TCO for those applications. I mean that that's pretty radical innovation and, and pretty true differentiation that our enterprise and other customer segments are really looking forward to. And then you layer in the fact that we're doing all of this in the de facto language that everybody in the world, the database speaks, which is cul you know, we like to say, it's easy SQL you get up and running, you're going, we speak your dialect. And we give you all of the benefits of this modern platform that are gonna make your job easier. Uh, you know, I think there's a reason why it's the brightest star in, uh, in, in the hemisphere. >>You know, it's funny, you, you, you, you used to talk about your, your S your SQL prowess. And, and that was that, that was the epiphany to me in the early days of big data. It was like the killer app for big data was SQL. And that changed. Everybody's thinking, let's talk about what's next for Couchbase you're a public company now, what are your priorities? How are you spending your time met? >>Well, look, Dave, we're, we're, uh, we're, we're gonna main remain maniacally focused on ensuring that we continue to innovate and solve the biggest problems, the biggest database challenges for enterprise customers. Um, we believe deeply in architecting differentiation that can be sustained over time. Uh, we've done that up to this point and we're going to remain steadfast in that mission. Uh, at the same time, we are entirely focused on satisfying our customers and, uh, demonstrating that we're a business partner, not just, just a vendor. So, you know, building partnerships, making sure we have the appropriate technical integration, supporting customers on their digital transformation strategies, continuing to invest in those capabilities to support customer journeys and make sure they're successful through that through their transformation. I mean, we're investing across all aspects of the business, across all aspects of the world. Uh, we're going to continue to be extremely proud of not just what we do, but how we do it. >>We are a values based organization. We have an incredible world-class team that we continue to grow on on a daily basis. And I'm going to make sure that we're spending time on each one of those and those things are in harmony. So we can continue to build a very vibrant, uh, company that's going to be around for a long, long time and continue to do great things for our customers. When we think about next generation technology, we are in the early innings of what we believe to be truly a generational market transition and the demands of applications and all things digital and combining, you know, technology that goes truly out to the edge and redefining what the edge is even, uh, and, and really thinking through how a platform needs to go, where the data resides to provide people, the experience and machines, the experiences that they need, uh, to, uh, complete their mission of digital transformation. Uh, there's some really mind-bending stuff that we're thinking through as we get, as we get way out there. Uh, but we're gonna continue to do it through the lens of solving big customer problems, making sure they're successful and then continuing to innovate as we go forward. >>Well, we're really excited to follow you guys report on this. And the database is no longer just kind of a bespoke bucket. It's a fundamental component of, of a digital fabric that's growing and becoming ubiquitous as part of a new data era. So we want to thank everybody for watching this keynote summary with Matt Kane, CEO of Couchbase Matt. We wish you all the best in the years ahead, and we look forward to seeing you in person, hopefully in the near future. >>Thanks a lot. See you soon, Dave. Appreciate >>It. All right. Thank you for watching our coverage at Couchbase connect 2021 modernized. Now keep it right there for more coverage that educates and inspires. You're watching the cube.

>> Welcome to the Cubes coverage of Couchbase connect online 2021. I'm Lisa Martin. I have a first timer here on the cube Priya Rajgopal, the director of product management from Couchbase joins me next. Priya, welcome to the program. >> Thank you, Lisa. Thanks for having me here and glad to be here. First timer. So really excited. >> Yeah. Well, we'll make sure that you're going to have fun. We're going to talk about edge computing and what I'd love to get is your perspectives on what's going on and the evolution in the last 18 months. I'm sure so much has changed, but talk to me about edge computing what's going on >> Sure. >> Sure. there's 6 lot of literature on there and different there's a lot of literature on there and different interpretations and the way we see it at Couchbase, it's a distributed computing paradigm, that brings compute and storage to the edge. And what is the edge? The edge is the location where data is generated or consumed. And so the edge, again, the taxonomy is varied, but it's really a continuum. So it's not a thing, right? So it's a location. So it could be a single device or it could actually be a data center. And so it's getting a lot of traction with the proliferation of a lot of applications around AR, VR, IOT, and mobile devices and mobile applications. Because it delivers on the promise of ultra low latency access to data because you know, the edges where the data is generated and consumed, data privacy, governance, residency to network disruptions, low bandwidth usage. So to your question on how does mobile fit into the space of edge computing? In my view, mobile application, mobile devices are a classic example of edge computing because think about mobile devices, right, they're generating data, they're processing data, applications are processing data right there on the devices. You can store data in offline mode on those devices. So it is a classic edge device. And of course, the data doesn't have to be generated on the device itself. There's mobile applications could sort of be gateways to other external like variables for instance, and other IOT devices, which can connect to these mobile applications. And these mobile applications could process that data. >> Got it. So thank you for sharing Couchbase's definition. And it's a good point to do that as so many times, there's so many different terms and solutions and technologies that can be interpreted and explained many different ways. Let's now go through Couchbase's role in edge computing. Help the audience understand where you fit into that. >> Sure. So if you recap the definition, right? edge computing is all about storage and compute to the edge. So clearly a database has a key role to play in this model, Right? Or in this paradigm, because when you think about it, a classic application architecture, you've got three tiers, you've got an application tier, it includes your business logic, some of the UI elements, that's optional. You've got your database tier, which drives the application, Does the obligation needs data? It's driven by the database tier. And then you've got the infrastructure tier, that includes your network storage compute. Now, when you're talking about an edge computing architecture, you're talking about distributing all these three tiers. Your application tier, a database tier, as well as your infrastructure tier and a Couchbase is a fully distributed, no sequel database solution. So it fits in right into this paradigm of edge computing. Now, when we are talking about distributing our storage, that's just one aspect of it, right? You have to distribute it to these edge devices. You may have to distribute it to edge data centers, You need to be able to sync or move data between these You need to be able to sync or move data between these distributed cloud environments, right? So data synchronization is a key component of the tier of of edge computing architectures. And then finally, there's data management. That's all about enforcement of policies, when it comes to data privacy, you know what, data needs to be resident at the edge, what data needs to be filtered, what needs to be aggregated? what data needs to be filtered, what needs to be aggregated? So you need a solution that can provide those hooks that allows you to enforce those policies. So, a database like Couchbase has a critical role to play solution that can be deployed in the cloud, or it can be deployed at the edge. And again, or it can be deployed at the edge. And again, the edge could be a data center or it could be a device. So what about device? We have an embedded database solution for mobile desktop and embedded platforms. And then of course, data movement, comprehensive data synchronization technology. comprehensive data synchronization technology. >> Let's go through specifically some of the database capabilities that are required for businesses in any industry to be successful in edge computing. >> Sure, absolutely. Right. to do sort of reiterate or reinforce the three concepts, right? Data storage, data movement, data management, right? And Couchbase technology because that the stack consists of couchbase server, our flagship fully distributed, no sequel data platform. It can be containerized. It can be deployed in any public or private cloud. It could be deployed at the edge cloud. And then you've a Couchbase lite. Again, no sequel embedded database full featured, right? Anything that you can do with a standalone database, you can do it with the embedded database. Now you can embed that within your mobile applications, within your other embedded applications or desktop applications. And that's great, right? That's the data storage part of it. And, and that's one part of it, but what about the data movement? And that's where you got a data synchronization technology where we facilitate a high throughput, high performance, highly scalable data synchronization, between the edge and the cloud. And of course, as I mentioned, data management is a critical aspect of all this, right? And so the synchronization technology has got components that allow you to set filters, access control policies. And there's a lot of hooks when it comes to data governance. So for instance, if an edge goes out of commission, or if there's a security breach, for instance, you want to isolate the edge, you can do that. The data that was previously synchronized to that edge, you want to be able to poach that data. So we have options the automatically poach the data, if the device is no longer in the hands of the right recipient for instance. those are the critical aspects. Of course, the overarching theme is security, right? And, that goes hand-in-hand with encryption of the data at rest, encryption of the data in motion, then authentication, authorization, access control. >> Security is even more important in given the events of the last 18 months where we've seen a massive rise in ransom, where we've seen a huge rise in DDoS attacks. Let's, double-click more on the security aspect of what Couchbase is delivering. >> Sure, absolutely. So when it comes to security of data at rest, right, even when the Couchbase lite, which is our embedded device, your entire database is encrypted AES-256 data encryption, and then data, when it leaves the device through our data synchronization protocol, everything is encrypted. And of course, when it goes to a sync gateway, the sync gateway is sort of, as I mentioned, the middle tier component, that is responsible for data synchronization between the embedded devices and Couchbase server. That entity is responsible for enforcement of access control policies. So you are guaranteed that only users who should have access to those documents or data are granted access to that. And in fact, we are NoSQL Json database. So which means, everything is modeled in the form of documents, Json documents. And so when we're talking about read, write access control, read access is at the granularity of a document, and write access can be enforced at the granularity of a property within the document. So you may have access to an entire document, but you may only be allowed to update a certain property within the document. So, as I mentioned, when it comes to distributed computing architectures like edge computing, security is even more paramount, right? You have devices going offline, coming back online and, you might have a breach point at one edge environment, whether it is a data center or an edge device, you need to be able to ensure that you have isolated all the other edge components from that breach. And as I mentioned, when it comes to data governance and so on, data retention, for instance, even if it is not a security breach, let's say you do have, for some reason, the owner of a device should no longer have access to that content. You know, their role has changed, they have transitioned to a different company for instance. Then you will have a way of automatically purging all that data that was previously synchronized to the user's device. >> Got it. Okay. Let's continue talking about the events of the last year and a half. Because we saw this massive scatter, 18 months ago of an explosion at the edge when a lot of people went from the office to this work from home, work from any anywhere environment in which we're still in. So how has the pandemic and the events that related to it changed mobile apps and edge computing and what are some of the new requirements that customers have? >> Sure. Well, as you rightly said, right? In fact, if anything, the relevance of mobile devices and applications has just grown in significance through the pandemic. And it's kind of interesting, there are some surveys that have suggested that through the pandemic people have been using their mobile devices as their primary communication device for accessing the internet. And it's kind of interesting because you think, well, everyone is cooped up in their homes. They probably will have access to other forms of data consumption, but no, it's mobile devices. That's what they have primarily been using. So with that, there is also a new range of use cases and applications, which are driven in large part by the events of the pandemic. But I think that's just made things much more efficient. Customer satisfaction, user experience is paramount, is number one. And I think a lot of that is here to stay even following or post pandemic because it's just made things a lot more efficient. And we've seen that through different industries, right? Healthcare, there was always telemedicine medicine, but now for non-essential care, it's always telemedicine, Of course, specific to the pandemic. there was the, tracking, the contact tracing application, right? That's enabled through technologies like Bluetooth and GPS, so they track the whereabouts of infected persons. But then even if you arrive at your doctor's office, right, you wait in your car and you get notified when the doctor's ready to check you in. And then retail sector, E-commerce right? Of course everything was going online, but everything is overwhelming People are shopping online through their mobile devices, than the traditional web based applications. And you order on your phone, you pick up at the store, right? So curbside pickup, you pull into the store, the store clerk is notified of your arrival. They come out to the curb with your order. And here's the interesting bit, you know, it's kind of intuitive that it's going to be e-commerce applications. They got a huge boost through the pandemic. But interestingly, even the experience when it comes to retail in store, that's undergone a transformation because it was all about how do we make the process very efficient. So customers are in and out of the store really quick, right? there was the reason for that. But now we can translate to making the whole shopping experience much more easy. So you walk into the store, you meet a sales associate who can bring up information about the catalog inventory right there on the iPad. And so if you have any questions, whether it's something is available in the store or an access for you're looking for, they can give answers to you immediately. Right? And of course there are companies like Walmart, they have been rolling out applications. Mobile scan and go sort of applications, which is all about, you know, you scan items as you walk through the aisle, do a self checkout, totally contact-less experience. And, the list goes on, right? We talked about healthcare retail, same thing in, in a restaurant, right? A curbside that delivery and pickup, you can now track your delivery order because now it's just a huge surge in order deliveries. And then the same pickup concept, curbside pickup concept, you arrive in your car, the kitchen is notified of your arrival and they come out with your order, very streamlined drive-through. You've got people now coming to your car, taking the order, right there from the car on their tablets, that synced in real time to the backend kitchen, your order. And you get notified when your order is ready. So I think all this is about making things a lot more efficient. It's about customer experience, and edge computing has a big role to play in that. And so I think, if anything is just propelled the growth of mobile applications and use cases. >> Yeah. That that propulsion is something that we've been hearing a lot about the acceleration in the last year and a half. You did a great job there of painting a picture of some of the positives that come out of this accelerating the efficiencies that we all as consumers and in our business life expect to have. And this explosion at the edge that's really become even more of a lifeline for millions and millions and billions of people globally. I got to ask you that from a connectivity perspective, that's another area where we had this expectation as again, consumers or in our business lives we have connectivity. Where does all that talk about 5G; What does 5G fit into edge computing? >> Sure. That's a good question. Because 5G and edge computing sort of go hand in hand so much so that they are being used synonymously in some cases and that's inaccurate. Okay? So because every time people talk about edge computing, there are folks talking about 5G in the same breath, right? But really 5G, as we all know, is a cellular next generation cellular technology, promises, ultra low latency, very high bandwidth. Now we talked about this huge surge, right in mobile applications and new sort of use cases where a lot of the data is generated at the edge. IOT applications are just data intensive applications, right gaming apps and so on. And all of these applications, they demand ultra low latency, right? And they're generating a lot of this data and all that data needs to be processed in real time. So if you have to send all of that data back to the cloud, and then you get the responses, that's a really bad experience. So that's what 5G is here to solve, right? I mean, it's like low latency, high bandwidth, high concurrency. Now that's all great. But then the coverage of 5G, it terminates at the edge of the mobile operator network. So you have all these massive influx of devices generating all that data. And all that stuff is transmitted under a very low latency conditions over a 5G network. But then if all that data from the mobile operator network has to be back hauled to the internet, to the backend servers, then you kind of defeat the whole purpose of ultra low latency applications. So that's where edge computing comes into play because edge computing is really an architecture, right? It's a distributed architecture. So now what mobile operators are doing is deploying what they refer to as NDCs, but it's effectively micro data centers at the edge of the mobile operator network. So you have all this data coming in over the 5G network. Great. They get analyzed, they get processed locally at the edge of the mobile operator network and you get real-time responses. And of course, as needed that data in aggregated or filter form goes back to the cloud. And so that's where the two relate. So in my view, I think edge computing architectures are important to deliver on the promise of 5G, but 5G has propelled the relevance or importance of edge computing as a solution, as a deployment architecture. So very interrelated. >> Very interrelated, very symbiotic. And of course the need for real time data real-time analytics in every industry became very prominent in the last year and a half. We had this expectation that we're going to be able to understand things in real time. And that's often a huge differentiator for businesses. We're out of time, but I want to ask you one more question Priya, and that is where can customers go to get started with Couchbase? >> Oh, absolutely. So Couchbase servers and gateway, you can deploy that, it's available as software. You can download it from our website. Couchbased lite is available for all your mobile applications. So it is available as a download, but you also have the classic package management systems through which you can download Couchbase Lite. And then of course, as I said, you can deploy this standalone, but you can also deploy it in the cloud. So we have marketplace offerings for both Couchbase server and sync gateway. So if you want to deploy it on AWS, as your Google, you can do that as well. >> Excellent. Priya, thank you so much for joining me on the program, talking about Couchbase the evolution, the changes, the opportunities with edge computing and mobile and how Couchbase is involved. I appreciate your time. >> Thank you very much. And thanks for having me. >> For Priya Rajgopal, I'm Lisa Martin. You're watching the Cubes coverage of Couchbase connect, online 2021.

>>Welcome back to the cubes coverage of Couchbase connect online, where the theme of the event is, or is modernized now. Yes, let's talk about that. And with me is Ravi, who's the senior vice president of engineering and the CTO at Couchbase Ravi. Welcome. Great to see you. >>Thank you so much. I'm so glad to be here with you. >>I asked you what the new requirements are around modern applications. I've seen some, you know, some of your comments, you gotta be flexible, distributed, multimodal, mobile edge. It, that those are all the very cool sort of buzz words, smart applications. What does that all mean? And how do you put that into a product and make it real? >>Yeah, I think what has basically happened is that, uh, so far, uh, it's been a transition of sorts. And now we are come to a point where, uh, the tipping point and the tipping point has been, uh, uh, more because of COVID and there COVID has pushed us to a world where we are living, uh, in a sort of, uh, occasionally connected manner where our digital, uh, interactions, precede our physical interactions in one sense. So it's a world where we do a lot more stuff that's less than, uh, in a digital manner, as opposed to sort of making a more specific human contact that has really been the, uh, sort of accelerant to this modernized. Now, as a team in this process, what has happened is that so far all the databases and all the data infrastructure that we have built historically, are all very centralized. >>They're all sitting behind. Uh, they used to be in mainframes from where they came to like your own data centers, where we used to run hundreds of servers to where they're going now, which is the computing marvelous change to consumption-based computing, which is all cloud oriented now. And so, uh, but they are all centralized still. Uh, but where our engagement happens with the data is, uh, at the edge, uh, at your point of convenience at your point of consumption, not where the data is actually sitting. So this has led to, uh, you know, all those buzzwords, as you said, which is like, oh, well we need a distributed data infrastructure, where is the edge? Uh, but it just basically comes down to the fact that the data needs to be where you are engaging with it. And that means if you are doing it on your mobile phone, or if you are sitting, uh, doing something in your body or traveling, or whether you are in a subway, whether you're in a plane or a ship, wherever the data needs to come to you, uh, and be available as opposed to every time you going to the data, which is centrally sitting in some place. >>And that is the fundamental shift in terms of how the modern architecture needs to think, uh, when they, when it comes to digital transformation and, uh, transitioning their old applications to, uh, the, the modern infrastructure, because that's, what's going to define your customer experiences and your personalized experiences. Uh, otherwise people are basically waiting for that circle of death that we all know, uh, and blaming the networks and other pieces. The problem is actually, the data is not where you are engaging with. It has got to be fetched, you know, seven seas away. Um, and that is the problem that we are basically solving in this modern modernization of that data, data infrastructure. >>I love this conversation and I love the fact that there's a technical person that can kind of educate us on, on this, because date data by its very nature is distributed. It's always been distributed, but w w but distributed database has always been incredibly challenging, whether it was a global SIS Plex or an eventual consistency of getting recovery for a distributed architecture has been extremely difficult. You know, I hate that this is a terrible term, lots of ways to skin a cat, but, but you've been the visionary behind this notion of optionality, how to solve technical problems in different ways. So how do you solve that, that problem of, of, of, uh, of, uh, of a super rock solid database that can handle, you know, distributed data? Yes. >>So there are two issues that you're a little too over there with Forrest is the optionality piece of it, which is that same data that you have that requires different types of processing on it. It's almost like fractional distillation. It is, uh, like your crude flowing through the system. You start all over from petrol and you can end up with Vaseline and rayon on the other end, but the raw material, that's our data in one sense. So far, we never treated the data that way. That's part of the problem. It has always been very purpose built and cast first problem. And so you just basically have to recast it every time we want to look at the data. The first thing that we have done is make data that fluid. So when you're actually, uh, when you have the data, you can first look at it to perform. >>Let's say a simple operation that we call as a key value store operation. Given my ID, give him a password kind of scenarios, which is like, you know, there are customers of ours who have billions of user IDs in their management. So things get slower. How do you make it fast and easily available? Log-in should not take more than five minutes. Again, this is a, there's a class of problem that we solve that same data. Now, eventually, without you ever having to, uh, sort of do a casting it to a different database, you can now do a solid, uh, acquire. These are classic sequel queries, which is our next magic. We are a no SQL database, but we have a full functional sequel. The sequel has been the language that has talked to data for 40 odd years successfully. Every other database has come and try to implement their own QL query language, but they've all failed only sequel as which stood the test of time of 40 odd years. >>Why? Because there's a solid mathematics behind it. It's called a relational calculus. And what that helps you is, is, uh, basically, uh, look at the data and any common tutorial, uh, any, uh, any which way you look at the data. All it will come, uh, the data in a format that you can consume. That's the guarantee sort of gives you in one sense. And because of that, you can now do some really complex in the database signs, what we call us, predicate logic on top of that. And that gives you the ability to do the classic relational type queries, select star from where Canada stuff, because it's at an English level, it becomes easy to, so the same data, you didn't have to go move it to another database, do your, uh, sort of transformation of the data and all this stuff. Same day that you do this. >>Now, that's where the optionality comes in. Now you can do another piece of logic on top of this, which we call search. This is built on this concept of inverted index and TF IDF, the classic Google in a very simple terms, but Google tokenized search, you can do that in the same data without you ever having to move the data to a different format. And then on top of it, they can do what is known as a eventing or your own custom logic, which we all which we do on a, on programming language called Java script. And finally analytics and analytics is the ability to query the operational data in a different way. I'll talk budding. What was my sales of this widget year over year on December 1st week, that's a very complex question to ask, and it takes a lot of different types of processing. >>So these are different types of that's optionality with different types of processing on the same data without you having to go to five different systems without you having to recast the data in five different ways and find different application logic. So you put them in one place. Now is your second question. Now this has got to be distributed and made available in multiple cloud in your data center, all the way to the edge, which is the operational side of the, uh, the database management system. And that's where the distributed, uh, platform that we have built enables us to get it to where you need the data to be, you know, in a classic way, we call it CDN in the data as in like content delivery networks. So far do static, uh, uh, sort of moving of static content to the edges. Now we can actually dynamically move the data. Now imagine the richness of applications you can develop. >>The first part of the, the answer to my question, are you saying you could do this without skiing with a no schema on, right? And then you can apply those techniques. >>Uh, fantastic question. Yes. That's the brilliance of this database is that so far classically databases have always demanded that you first define a schema before you can write a single byte of data. Couchbase is one of the rare databases. I, for one don't know any other one, but there could be, let's give the benefit of doubt. It's a database which writes data first and then late binds to schema as we call it. It's a schema on read things. So because there is no schema, it is just a on document that is sitting inside. And Jason is the lingua franca of the web, as you very well know by now. So it just Jason that we manage, you can do key lookups of the Jason. You can do full credit capability, like a classic relational database. We even have cost-based optimizers and the other sophisticated pieces of technology behind it. >>You can do searching on it, using the, um, the full textual analysis pipeline. You can do ad hoc wedding on the analytic side, and you can write your own custom logic on it using our eventing capabilities. So that's, that's what it allows because we keep the data in the native form of Jason. It's not a data structure or a data schema imposed by a database. It is how the data is produced. And on top of it, we bring different types of logic, five different types of it's like the philosophy is bringing logic to data as opposed to moving data to logic. This is what we have been doing, uh, in the last 40 years because we developed various, uh, database systems and data processing systems of various points. In time in our history, we had key value stores. We had relational systems, we had search systems, we had analytical systems. >>We had queuing systems, all the systems, if you want to use any one of them, our answer has always been, just move the data to that system. Versus we are saying that do not move the data as we get bigger and bigger and data just moving this data is going to be a humongous problem. If you're going to be moving petabytes of data for this is not one to fly instead, bring the logic to the data. So you can now apply different types of logic to the data. I think that's what, in one sense, the optionality piece of this, >>As you know, there's plenty of schema-less data stores. They're just, they're called data swamps. I mean, that's what they, that's what they became, right? I mean, so this is some, some interesting magic that you're applying here. >>Yes. I mean, the one problem with the data swamps as you call them is that that was a little too open-ended because the data format itself could change. And then you do your, then everything became like a game data casting because it required you to have it in seven schema in one sense at the end of the day, for certain types of processing. So in that where a lot of gaps it's probably flooded, but it not really, uh, how do you say, um, keep to the promise that it actually meant to be? So that's why it was a swamp I need, because it was fundamentally not managing the data. The data was sitting in some file system, and then you are doing something, this is a classic database where the data is managed and you create indexes to manage it, and you create different types of indexes to manage it. You distribute the index, you distribute the data you have, um, like we were discussing, you have acid semantics on top of, and when you, when you put all these things together, uh, it's, it's, it's a tough proposition, but they have solved some really tough problems, which are good computer science stuff, computer science problems that we have to solve to bring this, to bring this, to bear, to bring this to the market. >>So you predicted the trend around multimodal and converged, uh, databases. Um, you kind of led Couchbase through that. I want to, I always ask this question because it's clearly a trend in the industry and it, it definitely makes sense from a simplification standpoint. And, and, and so that I don't have to keep switching databases or the flip side of that though, Ravi. And I wonder if you could give me your opinion on this is kind of the right tool for the right job. So I often say isn't that the Swiss army knife approach, we have a little teeny scissors and a knife. That's not that sharp. How do you respond to that? Uh, >>A great one. Um, my answer is always, I use another analogy to tackle that, but is that, have you ever accused a smartphone of being a Swiss army knife? No. No. Nobody does that because it's actually 40 functions in one is what a smartphone becomes. You never call your iPhone or your Android phone, a Swiss army knife, because here's the reason is that you can use that same device in the full capacity. That's what optionality is. It's not, I'm not, it's not like your good old one where there's a keyboard hiding half the screen, and you can do everything only through the keyboard without touching and stuff like that. That's not the whole devices available to you to do one type of processing when you want it. When you're done with that, it can do another completely different types of processing. Like as in a moment, it could be a Tom, Tom telling you all the directions, the next one, it's your PDA. >>Third one, it's a fantastic phone. Uh, four, it's a beautiful camera, which can do your f-stop management and give you a nice SLR quality picture. Right? So next moment is a video camera. People are shooting movies with this thing in Hollywood, these days for God's sake. So it gives you the full power of what you want to do when you want it. And now, if you just taught that iPhone is a great device or any smartphone is a great device, because you can do five things in one or 50 things in one, and at a certain level, they missed the point because what that device really enabled is not just these five things in one place. It becomes easy to consume and easy to operate. It actually started the app is the economy. That's the brilliance of bringing so many things in one place, because in the morning, you know, I get the alert saying that today you got to leave home at eight 15 for your nine o'clock meeting. >>And the next day it might actually say 8 45 is good enough because it knows where the phone is sitting. The geo position of it. It knows from my calendar where the meeting is actually happening. It can do a traffic calculation because it's got my map and all of the routes. And then it's gone there's notification system, which eventually pops up on my phone to say, Hey, you got to leave at this time. Now five different systems have to come together and they can because the data is in one place without that, you couldn't even do this simple function, uh, in a, in a sort of predictable manner in a, in a, in a manner that's useful to you. So I believe a database which gives you this optionality of doing multiple data processing on the same set of data allows you will allow you to build a class of products, which you are so far been able to struggling to build, because half the time you're running sideline to sideline, just, you know, um, integrating data from one system to the other. >>So I love the analogy with the smartphone. I w I want to, I want to continue it and double click on it. So I use this camera. I used to, you know, my kid had a game. I would bring the, the, the big camera, the 35 millimeter. So I don't use that anymore no way, but my wife does, she still uses the DSLR. So is, is there a similar analogy here? That those, and by the way, the camera, the camera shop in my town went out of business, you know? And so, so, but, but is there, is that a fair, where, in other words, those specialized databases, they say there still is a place for them, but they're getting >>Absolutely, absolutely great analogy and a great extension to the question. That's, that's the contrarian side of it in one sense is that, Hey, if everything can just be done in one, do you have a need for the other things? I mean, you gave a camera example where it is sort of, it's a, it's a slippery slope. Let me give you another one, which is actually less straight to the point better. I've been just because my, I, I listened to half of the music on the iPhone. Doesn't stop me from having my full digital receiver. And, you know, my Harman Kardon speakers at home because they haven't, they produce a kind of sounded immersive experience. This teeny little speaker has never in its lifetime intended to produce, right? It's the convenience. Yes. It's the convenience of convergence that I can put my earphones on and listen to all the great music. >>Yes, it's 90% there or 80% there. It depends on your audio file mess of your, uh, I mean, you don't experience the super specialized ones do not go away. You know, there are, there are places where, uh, the specialized use cases will demand a separate system to exist, but even there that has got to be very closed. Um, how do you say close, binding or late binding? I should be able to stream that song from my phone to that receiver so I can get it from those speakers. You can say that, oh, there's a digital divide between these two things done, and I can only play CDs on that one. That's not how it's going to work going forward. It's going to be, this is the connected world, right? As in, if I'm listening to the song in my car and then step off the car and walk into my living room, that's same songs should continue and play in my living room speakers. Then it's a world because it knows my preference and what I'm doing that all happened only because of this data flowing between all these systems. >>I love, I love that example too. When I was a kid, we used to go to Twitter, et cetera. And we'd to play around with, we take off the big four foot speakers. Those stores are out of business too. Absolutely. Um, now we just plug into Sonos. So that is the debate between relational and non-relational databases over Ravi. >>I believe so. Uh, because I think, uh, what had happened was the relational systems. Uh, I've been where the norm, they rule the roost, if you will, for the last 40 odd years, and then gain this no sequel movement, which was almost as though a rebellion from the relational world, we all inhibited, uh, uh, because we, it was very restrictive. It, it had the schema definition and the schema evolution as we call it, all those things, they were like, they required a committee, they required your DBA and your data architect. And you have to call them just to add one column and stuff like that. And the world had moved on. This was the world of blogs and tweets and, uh, you know, um, mashups and, um, uh, uh, a different generation of digital behavior, digital, native people now, um, who are operating in these and the, the applications, the, the consumer facing applications. >>We are living in this world. And yet the enterprise ones were still living in the, um, in the other, the other side of the divide. So all came this solution to say that we don't need SQL. Actually, the problem was never sequel. No sequel was, you know, best approximation, good marketing name, but from a technologist perspective, the problem was never the query language, no SQL was not the problem, the schema limitations, and the inability for these, the system to scale, the relational systems were built like, uh, airplanes, which is that if, uh, San Francisco Boston, there is a flight route, it's so popular that if you want to add 50 more seats to it, the only way you can do that is to go back to Boeing and ask them to get you a set in from 7 3 7 2 7 7 7, or whatever it is. And they'll stick you with a billion dollar bill on the alarm to somehow pay that by, you know, either flying more people or raising the rates or whatever you have to do. >>These are called vertically scaling systems. So relational systems are vertically scaling. They are expensive. Versus what we have done in this modern world, uh, is make the system how it is only scaling, which is more like the same thing. If it's a train that is going from San Francisco to Boston, you need 50 more people be my guests. I'll add one more coach to it, one more car to it. And the better part of the way we have done this year is that, and we have super specialized on that. This route actually requires three, three dining cars and only 10 sort of sleeper cars or whatever. Then just pick those and attach the next route. You can choose to have ID only one dining car. That's good enough. So the way you scale the plane is also can be customized based on the route along the route, more, more dining capabilities, shorter route, not an abandoned capability. >>You can attach the kind of coaches we call this multi-dimensional scaling. Not only do we scale horizontally, we can scale to different types of workloads by adding different types of coaches to it quite. So that's the beauty of this architecture. Now, why is that important? Is that where we land eventually is the ability to do operational and analytical in the same place. This is another thing which doesn't happen in the past, because you would say that I cannot run this analytical Barre because then my operational workload will suffer. Then my friend, then we'll slow down millions of customers that impacted that problem. We will solve the same data in which you can do analytical buddy, an operational query because they're separated by these cars, right? As in like we, we fence the, the, the resources, so that one doesn't impede the other. So you can, at the same time, have a microsecond 10 million ops per second, happening of a key value or equity. >>And then yet you can run this analytical body, which will take a couple of minutes to run one, not impeding the other. So that's in one sense, sort of the, part of the, um, uh, problems that we have solved here is that relational versus, uh, uh, the no SQL portion of it. These are the kinds of problems we have to solve. We solve those. And then we yet put back the same quality language on top. Y it's like Tesla in one sense, right underneath the surface is where all the stuff that had to be changed had to change, which is like the gasoline, uh, the internal combustion engine, uh, I think gas, uh, you says, these are the issues we really wanted to solve. Um, so solve that, change the engine out, you don't need to change the steering wheel or the gas pedal or the, you know, the battle shifters or whatever else you need, or that are for your shifters. >>Those need to remain in the same place. Otherwise people won't buy it. Otherwise it does not even look like a car to people. So, uh, even when you feed people the most advanced technology, it's got to be accessible to them in the manner that people can consume. Only in software, we forget this first design principle, and we go and say that, well, I got a car here, you got the blue harder to go fast and lean back for, for it to, you know, uh, to apply a break that's, that's how we seem to define, uh, design software. Instead, we should be designing them in a manner that it is easiest for our audience, which is developers to consume. And they've been using SQL for 40 years or 30 years. And so we give them the steering wheel on the, uh, and the gas bottle and the, um, and the gear shifter is by putting cul back on underneath the surface, we have completely solved, uh, the relational, uh, uh, limitations of schema, as well as scalability. >>So in, in, in that way, and by bringing back the classic acid capabilities, which is what relational systems, uh, we accounted on and being able to do that with the sequel programming language, we call it like multi-state SQL transaction. So to say, which is what a classic way all the enterprise software was built by putting that back. Now, I can say that that debate between relational and non-relational is over because this has truly extended the database to solve the problems that the relational systems had to grow up the salt in the modern times, but rather than get, um, sort of pedantic about whether it's, we have no SQL or sequel or new sequel, or, uh, you know, any of that sort of, uh, jargon, oriented debate, uh, this, these are the debates of computer science that they are actually, uh, and they were the solve and they have solved them with, uh, the latest release of $7, which we released a few months ago. >>Right, right. Last July, Ravi, we got to leave it there. I, I love the examples and the analogies. I can't wait to be face to face with you. I want to hang with you at the cocktail party because I've learned so much and really appreciate your time. Thanks for coming to the cube. >>Fantastic. Thanks for the time. And the Aboriginal Dan was, I mean, very insightful questions really appreciate it. Thank you. >>Okay. This is Dave Volante. We're covering Couchbase connect online, keep it right there for more great content on the cube.

>>Welcome back to Couchbase connect. My name is Dave Vellante and we're going to dig into a customer case study of sorts with two software engineers from a company called trendy all the largest e-commerce platform in Turkey. And with me are in MRA, tan Rivera, both software engineers at trendy. All welcome. Good to see you guys. Hey, before we get into the story, maybe you can tell us a little bit about trendy all. >>Let me answer that question first. Um, tri-annual uh, today is, um, 10 years old. Uh, actually, uh, it starts with them, um, e-commerce company, uh, Jen, uh, especially, uh, for clothing, uh, today, uh, it's serves several, uh, services, uh, mainly still e-commerce right. Um, we, uh, we do our business mainly on technology and we even have a say in technology, uh, technology is our main concern actually. Um, just like that actually now, >>So thank you for that. I mean, you started, I think, I think the company was founded in 2009, 2010. So you weren't, you were just, you know, kind of which we would consider the, sort of the modern era at the same time. When you look back 10 years, you know, major challenges, major advancements from a technology standpoint. So you at, at the time you had a, uh, a legacy database and you, you had a migraine, maybe you could describe the business conditions that drove you to think about actually making a change. What was the before, and then we can get into the after and what was driving that change? >>Um, maybe I could start it a bit. Well, uh, we have a recommendation domain and try new. It's like when you, when you look at a certain product, like for example, you look at a pencil, it it's commanding you, uh, any razor, uh, if you are going to buy a pink dress, it's going to recommend you a yellow dress. So if you're going to maybe buy pants, it will show you some t-shirts according to it. So, uh, since the recommendations, domain group larger, uh, we, we have struggled, uh, to keep it high scale, and it wasn't a relational DB at first, but that's even as product count increased and, uh, our right frequency increased day by day, uh, and our reef performance was affected very dramatically. Uh, I believe. Yeah. >>So you were using a traditional RDBMS, uh, and then, and, and the issue was you quite, you couldn't make the recommendations fast enough. And, you know, we always say what's real time. Real time is before you lose the customer. So you, you have to make those recommendations in time for the customer to act otherwise, you know, what do you do? Send an email after the fact, Hey, you bought this, nobody's going to pay attention to that. Right? You want to catch them in the moment. Um, and so, so what was it that, that led you to, to Couchbase and w and what was the experience of that? You know, whether it was onboarding, you know, the technology, you know, how difficult was it to get up and running to where you are today? >>Um, we were using ch Couchbase in, uh, in inter-annual, um, for several years, and we had experienced on that. Uh, and, uh, we actually, we need performance as described. So, uh, we convert our data structure to, from relational DB to, um, noise, Carol Levy, um, them actually on our recommendation, uh, platform, the main problem was, uh, invalidation process. You know, um, we are selling things and, um, in seconds they can be sold out and we, we shouldn't be recommend them anymore. And we are, we are keeping track of this by invalidation process and relational DB writing those data to our relationship Libby was, uh, was taking two, two minutes too much time. And, um, by changing this structure to, uh, pathways, we, we, we see that benefits, uh, and it takes so, so, uh, uh, short time, actually, >>I'm so sorry if, if I can just clarify w what was taking a long time, the, the updating the actual records, so that you could actually inform a customer that it was out of stock, or was it the coding that was too complicated? >>Well, it was, it was not because, um, there are millions of products intangible, and, uh, those issues are coming huge, actually. So we are keeping track of time if it's sold out or it's, it can be sellable, uh, when, when a product, uh, detail is seen by the customers, we are recommending some other products too, but those other products must be sellable too. So the main, the main problem was that, and, uh, we are writing them in our relational DB. There is a huge rights law actually. So it was not coding. It was the amount of data actually. >>Okay. And so it was the update intensity, um, within the database and the ability of the database to actually return accurate results quickly. So what was the after, like, uh, can you talk about sort of the, the business impact? What were the, the improvements that you've experienced? >>Yeah. Maybe I can ask her that, uh, like parties said that the main reason we switched is because that, uh, there are so many products coming near in trend, and many of them are being stopped being sold out and the updates to it, it was on a relational, the vendor rights, or too much that you couldn't, uh, dur customers that fast reply because the database was getting effected by the amount of high rights. Because when you think about it, there are millions of products coming, and there are millions of rights, uh, operations on the database. So those affecting the reach performance. So, uh, it, it could occur to you that when you click on a product, you would see maybe as took out product as a recommendation, or maybe a product that is not in the website anymore. So, uh, when we switched to, uh, Couchbase that, uh, we saw that, uh, it's using less resources, which, uh, using less posts, active, alive, and it's also, uh, giving responses faster. >>The main reason, uh, we were using relational DB at first was the invalidation process like five. He said, because it was, we had a consumer that was listening to messages, uh, the innovation messages, and then, uh, and then the writing them into database. But, uh, in the part, uh, it meant that actively writing to database that for every product document that you would need to update the document, but for, uh, for, for, uh, for relational DB, it would be vetoed easier to just make this product, uh, every available, false, or true. So that's why we were sticking with relationship with DB at first. And that's why we made it that first as a relational DB, but as time increased and our product count, and our sellers increased, we realized that, uh, we should find another solution to the invalidation process, and we should, uh, switch because, uh, I mean, it CA it has come to a point at one point that it would just maybe, uh, take a solid, so much time that, uh, we were scaling our consumers at nighttime to just not affect daily users anymore. >>Uh, so that's why that's the main reason we switched. And, uh, after switching, we had in, uh, like I said, the response time and high write throughput, and also one of the reasons is also because that the, uh, the application that was with the use of Couchbase because, uh, since strangled is growing larger than our main data centers. And, uh, like we can see that every day, sometimes we deploy our, uh, apps to yet another cluster. And we, that's why we sometimes need to have backups or different data centers, and Couchbase was providing very good relations, very good solutions to this, which is. Yeah. That's why we switched actually. So we asked >>Couchbase running it's if I understand it, it's running the recommendation engine. And do you still use a traditional RDBMS for the transaction system or is Couchbase doing both? >>Yeah, okay. Uh, we are, uh, actually inter-annual, we are in discovery a team, actually, we call it tribe and in discovery, tribe, uh, relational DB, I think, uh, now, uh, very small, uh, small, uh, teams are using it. Um, it's personally just very low actually. Uh, but, uh, other other tribes, for example, orders, checkout, and maybe, uh, uh, promotions, uh, something like other teams are still using RDBMS, but in discovery team, it's very important to serve customers very fast. We need to show them the products immediately. We need to personalize them. Uh, we sh we should, uh, show them, uh, related products in the meantime, in real time, actually. So in this current Stripe, we are, um, barely using it, uh, RDBMS systems, actually. >>How hard was it to migrate from the RDBMS? Because you hear a lot of stories about how difficult that is to do. You've got to freeze the code, you bringing up new code, you've got to synchronize the functionality. How did you manage that? >>Well, to be honest with you, just ask the data science team to just send the products. Uh, at the same time, we were like, we were keeping the legacy API open that the clients were still coming there. And, um, to be honest, there were lots of legs on that, too. So even if, uh, the, the newer products came a bit later, uh, it shouldn't be seen because it was always coming late. So, uh, we had, we made a new API that is connecting to Couchbase and we wanted the data science team to start feeding it, but we asked the clients to switch it by time. I mean, we were still supporting the old one, but, uh, when we, when we asked the clients to switch to the new API, we just closed the last one. So we didn't really migrate any data to be honest. Like we, we, it was from scratch. And since it's a, it's a recommendation domain, uh, we believe it's better to, uh, add data's from scratch because in our new domains, we are storing them in documents. They are always sending a new list to us. So that's how it gets updated all the time. So since it's not a user related data, it wasn't really like a migration process. >>Is this is part of the secret sauce that you're doing. Schema lists, no schema on, right to Couchbase. And is that correct? And how are you handling it? I'm like, how are you getting that awesome write performance? >>Well, the main reason we believe is that, uh, before, when it was relational DB, like for example, loan product to one product and a second product to first product, third product, first of all, that like you were duplicating the records so that when the product gets removed, uh, from, from a product recommendation, or maybe one of, if a product is getting invisible, for any reason, it should be removed, or maybe it could be a stockout that it means it's not that for every record, you are sending your records for invalidation, but in our new system, it means that this, uh, for this content, there are 24 contents let's say, and like four of them that's finished. It's not there. It's okay. You're just replacing the whole list so that you are not duplicating the records. I mean, this is not like first product first and first, the second, and first to third, and first changes you are replicating this, this change three times, like a delete, uh, product one from three, three product, one from two, and you are deprecating the deletion record, but now we are just replacing the list. So you are doing that all of the operation in 1, 1, 1, uh, Kafka queue message. If I should be able, if I was able to, uh, tell about it. So it's a bit hard to explain it in, uh, in speech, but, uh, we have a nice graphic that's showing how we are doing it now. >>That makes sense. Okay. Thank you for that. And so, as you think about, you're modernizing your application infrastructure, where are you at today? How do you see this modernization effort going forward >>Actually, um, today, uh, we are mainly looking for, um, cross cluster replication. Uh, all our products are, uh, uh, deployed, uh, different clusters and different geographical locations. Uh, we, we always using ch um, we try to always use, um, modern products and, uh, uh, try to avoid, uh, old relational databases, especially for our discovery. Right. And, uh, my mandala is modernizing it, uh, all, uh, engineer's keeping up to date with recent technologies and, uh, our customers are happier. They are not seeing some glitches, some, uh, rates, uh, or while they're using our products. >>Okay. So maybe I could double click on that. So, cause you mentioned the impact of customers and I'm interested in your organizational impact and what it means for you internally, but, but when you talk about cross cluster replication, is that to scale, uh, is that a performance impact? Is that for availability? What's the impact of that effort? That modernization effort? >>Uh, I believe it's, it's all, uh, main reason is availability. I believe. Uh, like we can't know when a cluster can go down, we can't be sure about it, uh, in a, in a system we can, but that we should be up and running all the time. And, uh, there should be some, uh, some backups that, uh, that can switch when a cluster goes down. But also the main reason, uh, well, one of the main reasons is to be able to scale because, uh, the, the clusters that we had wasn't enough, uh, considering our user base. So, uh, let's say you want to even extend your user base, but, uh, like the cluster is being a bottleneck to you because you can't get that much users, but, uh, when you do post cluster that you have backup and you have scalability and it's, uh, considering how new considering if the machines are newer, maybe faster response times. I don't know, uh, maybe, uh, network part would know that better, but, uh, yeah, but all of them, I will leave. >>Great guys. Well, thank you so much for sharing your story, uh, uh, MRA and Fati. Uh, appreciate you guys coming on the cube. >>Thanks a lot. Yeah. Thanks. Thanks. Thank you for, uh, hosting. >>Yeah, it's our pleasure. And thank you for watching. Couchbase connect online on the cube, keep it right there for more great content from the event.

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

(upbeat music playing) >> Welcome to theCUBE's coverage of Couchbase ConnectONLINE Mary Roth, VP of Engineering Operations with Couchbase is here for Couchbase ConnectONLINE. Mary. Great to see you. Thanks for coming on remotely for this segment. >> Thank you very much. It's great to be here. >> Love the fire in the background, a little fireside chat here, kind of happening, but I want to get into it because, Engineering and Operations with the pandemic has really kind of shown that, engineers and developers have been good, working remotely for a while, but for the most part it's impacted companies in general, across the organizations. How did the Couchbase engineering team adapt to the remote work? >> Great question. And I actually think the Couchbase team responded very well to this new model of working imposed by the pandemic. And I have a unique perspective on the Couchbase journey. I joined in February, 2020 after 20 plus years at IBM, which had embraced a hybrid, in-office remote work model many years earlier. So in my IBM career, I live four minutes away from my research lab in Almaden Valley, but IBM is a global company with headquarters on the East Coast, and so throughout my career, I often found myself on phone calls with people around the globe at 5:00 AM in the morning, I quickly learned and quickly adapted to a hybrid model. I'd go into the office to collaborate and have in-person meetings when needed. But if I was on the phone at 5:00 AM in the morning, I didn't feel the need to get up at 4:30 AM to go in. I just worked from home and I discovered I could be more productive there, doing think time work, and I really only needed the in-person time for collaboration. This hybrid model allowed me to have a great career at IBM and raise my two daughters at the same time. So when I joined Couchbase, I joined a company that was all about being in-person and instead of a four minute commute, it was going to be an hour or more commute for me each way. This was going to be a really big transition for me, but I was excited enough by Couchbase and what it offered, that I decided to give it a try. Well, that was February, 2020. I showed up early in the morning on March 10th, 2020 for an early morning meeting in-person only to learn that I was one of the only few people that didn't get the memo. We were switching to a remote working model. And so over the last year, I have had the ability to watch Couchbase and other companies pivot to make this remote working model possible and not only possible, but effective. And I'm really happy to see the results. A remote work model does have its challenges, that's for sure, but it also has its benefits, better work-life balance and more time to interact with family members during the day and more quiet time just to think. We just did a retrospective on a major product release, Couchbase server 7.0, that we did over the past 18 months. And one of the major insights by the leadership team is that working from home actually made people more effective. I don't think a full remote model is the right approach going forward, but a hybrid model that IBM adopted many years ago and that I was able to participate in for most of my career, I believe is a healthier and more productive approach. >> Well, great story. I love the come back and now you take leverage of all the best practices from the IBM days, but how did they, your team and the Couchbase engineering team react? And were there any best practices or key learnings that you guys pulled out of that? >> The initial reaction was not good. I mean, as I mentioned, it was a culture based on in-person, people had to be in in-person meetings. So it took a while to get used to it, but there was a forcing function, right? We had to work remotely. That was the only option. And so people made it work. I think the advancement of virtual meeting technology really helps a lot. Over earlier days in my career where I had just bad phone connections, that was very difficult. But with the virtual meetings that you have, where you can actually see people and interact, I think is really quite helpful. And probably the key. >> What's the DNA of the company there? I mean, every company's got the DNA, Intel's Moore's Law, and what's the engineering culture at Couchbase like, if you could describe it. >> The engineering culture at Couchbase is very familiar to me. We are at our heart, a database company, and I grew up in the database world, which has a very unique culture based on two values, merit and mentorship. And we also focus on something that I like to call growing the next generation. Now database technology started in the late sixties, early seventies, with a few key players and institutions. These key players were extremely bright and they tackled and solved really hard problems with elegant solutions, long before anybody knew they were going to be necessary. Now, those original key players, people like Jim Gray, Bruce Lindsay, Don Chamberlin, Pat Selinger, David Dewitt, Michael Stonebraker. They just love solving hard problems. And they wanted to share that elegance with a new generation. And so they really focused on growing the next generation of leaders, which became the Mike Carey's and the Mohan's and the Lagerhaus's of the world. And that culture grew over multiple generations with the previous generation cultivating, challenging, and advocating for the next, I was really lucky to grow up in that culture. And I've advanced my career as a result, as being part of it. The reason I joined Couchbase is because I see that culture alive and well here. Our two fundamental values on the engineering side, are merit and mentorship. >> One of the things I want to get your thoughts on, on the database questions. I remember, back in the old glory days, you mentioned some of those luminaries, you know, there wasn't many database geeks out there, there was kind of a small community, now, as databases are everywhere. So you see, there's no one database that has rule in the world, but you starting to see a pattern of database, kinds of things are emerging, more databases than ever before, they are on the internet, they are on the cloud, there are none the edge. It's essentially, we're living in a large distributed computing environment. So now it's cool to be in databases because they're everywhere. (laughing) So, I mean, this is kind of where we are at. What's your reaction to that? >> You're absolutely right. There used to be a few small vendors and a few key technologies and it's grown over the years, but the fundamental problems are the same, data integrity, performance and scalability in the face of distributed systems. Those were all the hard problems that those key leaders solved back in the sixties and seventies. They're not new problems. They're still there. And they did a lot of the fundamental work that you can apply and reapply in different scenarios and situations. >> That's pretty exciting. I love that. I love the different architectures that are emerging and allows for more creativity for application developers. And this becomes like the key thing we're seeing right now, driving the business and a big conversation here at the, at the event is the powering of these modern applications that need low latency. There's no more, not many spinning disks anymore. It's all in RAM, all these kinds of different memory, you got centralization, you got all kinds of new constructs. How do you make sense of it all? How do you talk to customers? What's the main core thing happening right now? If you had to describe it. >> Yeah, it depends on the type of customer you're talking to. We have focused primarily on the enterprise market and in that market, there are really fundamental issues. Information for these enterprises is key. It's their core asset that they have and they understand very well that they need to protect it and make it available more quickly. I started as a DBA at Morgan Stanley, back, right out of college. And at the time I think it was, it probably still is, but at the time it was the best run IT shop that I'd ever seen in my life. The fundamental problems that we had to solve to get information from one stock exchange to another, to get it to the SEC are the same problems that we're solving today. Back then we were working on mainframes and over high-speed Datacom links. Today, it's the same kind of problem. It's just the underlying infrastructure has changed. >> Yeah, the key, there has been a big supporter of women in tech. We've done thousands of interviews and why I got you. I want to ask you if you don't mind, career advice that you give women who are starting out in the field of engineering, computer science. What do you wish you knew when you started your career? And if you could be that person now, what would you say? >> Yeah, well, a lot of things I wish I knew then that I know now, but I think there are two key aspects to a successful career in engineering. I actually got started as a math major and the reason I became a math major is a little convoluted. As a girl, I was told we were bad at math. And so for some reason I decided that I had to major in it. That's actually how I got my start, but I've had a great career. And I think there are really two key aspects. First, is that it is a discipline in which respect is gained through merit. As I had mentioned earlier, engineers are notoriously detail-oriented and most are, perfectionists. They love elegant, well thought-out solutions and give respect when they see one. So understanding this can be a very important advantage if you're always prepared and you always bring your A-game to every debate, every presentation, every conversation, you have build up respect among your team, simply through merit. While that may mean that you need to be prepared to defend every point early on, say, in your graduate career or when you're starting, over time others will learn to trust your judgment and begin to intuitively follow your lead just by reputation. The reverse is also true. If you don't bring your A-game and you don't come prepared to debate, you will quickly lose respect. And that's particularly true if you're a woman. So if you don't know your stuff, don't engage in the debate until you do. >> That's awesome advice. >> That's... >> All right, continue. >> Thank you. So my second piece of advice that I wish I could give my younger self is to understand the roles of leaders and influencers in your career and the importance of choosing and purposely working with each. I like to break it down into three types of influencers, managers, mentors, and advocates. So that first group are the people in your management chain. It's your first line manager, your director, your VP, et cetera. Their role in your career is to help you measure short-term success. And particularly with how that success aligns with their goals and the company's goals. But it's important to understand that they are not your mentors and they may not have a direct interest in your long-term career success. I like to think of them as, say, you're sixth grade math teacher. You know, you getting an A in the class and advancing to seventh grade. They own you for that. But whether you get that basketball scholarship to college or getting to Harvard or become a CEO, they have very little influence over that. So a mentor is someone who does have a shared interest in your long-term success, maybe by your relationship with him or her, or because by helping you shape your career and achieve your own success, you help advance their goals. Whether it be the company success or helping more women achieve leadership positions or getting more kids into college on a basketball scholarship, whatever it is, they have some long-term goal that aligns with helping you with your career. And they give great advice. But that mentor is not enough because they're often outside the sphere of influence in your current position. And while they can offer great advice and coaching, they may not be able to help you directly advance. That's the role of the third type of influencer. Somebody that I call an advocate. An advocate is someone that's in a position to directly influence your advancement and champion you and your capabilities to others. They are in influential positions and others place great value in their opinions. Advocates stay with you throughout your career, and they'll continue to support you and promote you wherever you are and wherever they are, whether that's the same organization or not. They're the ones who, when a leadership position opens up will say, I think Mary's the right person to take on that challenge, or we need to move in a new direction, I think Mary's the right person to lead that effort. Now advocates are the most important people to identify early on and often in your career. And they're often the most overlooked. People early on often pay too much attention and rely on their management chain for advancement. Managers change on a dime, but mentors and advocates are there for you for the long haul. And that's one of the unique things about the database culture. Those set of advocates were just there already because they had focused on building the next generation. So I consider, you know, Mike Carey as my father and Mike Stonebraker as my grandfather, and Jim Gray as my great-grandfather and they're always there to advocate for me. >> That's like a schema and a database. You got to have it all right there, kind of teed up. Beautiful. (laughing) Great advice. >> Exactly. >> Thank you for that. That was really a masterclass. And that's going to be great advice for folks, really trying to figure out how to play the cards they have and the situation, and to double down or move and find other opportunities. So great stuff there. I do have to ask you Mary, thanks for coming on the technical side and the product side. Couchbase Capella was launched in conjunction with the event. What is the bottom line for that as, as an Operations and Engineering, built the products and rolled it out. What's the main top line message for about that product? >> Yeah. Well, we're very excited about the release of Capella and what it brings to the table is that it's a fully managed and automated database cloud offering so that customers can focus on development and building and improving their applications and reducing the time to market without having to worry about the hard problems underneath, and the operational database management efforts that come with it. As I mentioned earlier, I started my career as a DBA and it was one of the most sought after and highly paid positions in IT because operating a database required so much work. So with Capella, what we're seeing is, taking that job away from me. I'm not going to be able to apply for a DBA tomorrow. >> That's great stuff. Well, great. Thanks for coming. I really appreciate it. Congratulations on the company and the public offering this past summer in July and thanks for that great commentary and insight on theCUBE here. Thank you. >> Thank you very much. >> Okay. Mary Roth, VP of Engineering Operations at Couchbase part of Couchbase ConnectONLINE. I'm John Furrier, host of theCUBE. Thanks for watching. (upbeat music playing)

>> I've got Madhav Mekala here with me, commerce architect at PepsiCo Madhav welcome to the program. >> Thank you Lisa. >> So we're going to be talking about the solution that you implemented that helped with the global supply chain. So let's talk first about your role, commerce architect. Help me understand that a little bit better. >> So Frito-Lay PepsiCo is pretty big. It's a conglomerate of multiple product lines. So I worked for Frito-Lay, which is basically all the salty snacks and then we have a Quaker products as well in our portfolio. So I oversee all the architecture for all the commercial IoT solutions in the FNA portfolio. >> Got it all the commercial lines. So we all know the last 18 months major challenges with the global supply chain component shortages, we've seen a huge increase in the cost of raw materials, limited labor, but you guys actually started to tackle this challenge before the pandemic happened. So talk to me about the catalyst that PepsiCo, what you saw to modernize field service and supply chain application. >> Yeah, so we have a pretty old system that our field force, our frontline users are using. So we have a world-class supply chain system where we go into the stores and place orders and deliver products throughout the U.S. And then we penetrate, I think, more than 95% of the households with our products. So we need to have a robust supply chain as well as a good frontline sales application, to be able to manage the orders, and be able to deliver the products, right? So the system that we have is almost 20 year old system running on a very outdated technology. We've been trying to replace that for a while now. And finally, we started this early last year to completely replace the solution with a brand new IPhone based app. And then that gives our frontline the ability to go place orders, do deliveries to retail execution in the store like check-in check-out, bill displays. There are so much functionality that our RSRs or frontline users do in the stores and this app enables them to do much more efficiently. >> And we're going to break into that, but you mentioned you had a 20 year old technology. Talk to me about some of the challenges that that likely presented to those frontline workers. >> Yeah. I mean, there are multiple challenges for one, we cannot enable new business models. So business wants to come up with new ideas for, to be able to implement in the field, but with our system being so old, it's so hard to implement anything on that one. And then even the physical device is not scaling. We had a lot of memory issues, so it's time for it to kind of retire, but also the technology we use the 3G technology is retiring pretty soon at the next year. So we were definitely need to move to a new solution. And this is one of the must things we have to do right away. So that's where we started the project and we are in pilot phase right now. >> What would have been some of those negative consequences, had you not undertaken the effort? I imagine from a competitive perspective, knowing how much competition is out there, what would some of those challenges have been if this had persisted? >> Yeah, so one is the stability of the application, right? So the frontline users have to spend more time because the app is not stable, the current one. So that reduces the efficiency of our Salesforce. Right? And then on the other hand, we also not able to put new features or new business models enable new business models on top of the existing ones. So we are losing out on some of them because of our outdated system. So that's one thing we want to solve with the new one. >> So this is really critical to really evolve PepsiCo's business at, at its baseline, right? >> That's true. Yeah. It is very critical application that we are building and this will enable us to do a lot more things in future. And we can come up with new ideas, including like virtual reality or connecting to multiple systems. There are so many new ideas that we want to enable once we have this in place. >> Awesome. Talk to me about why Couchbase and then tell us more about, you started to talk a little bit about the solution, but let's go ahead and dig in and unpack the actual solution that you implemented. >> Yeah. So this is, eh, we call it an ERP and a mobile device because it has so much functionality as a company Frito-Lay, we have been over a hundred years in this business, right? We have so many optimized process that we have that kind of led to some digility in the system because we want to do in a particular way, because that's the best way to do it as part of our business process. So what we're trying to do here is take that business process and also provide an app that will enhance it and then connect to more, more systems. So that's what we are trying to do here. And then on top of that one, we will replace all the existing peripherals that we use with the new technology, like Bluetooth and all so that, they are much more faster and they slot more productive for our frontline force. >> Sounds like a lot of sales folks are going to to be a lot more productive. Talk to me about where Couchbase is as an integral component to this new system. >> Yeah. So one of the key requirements for this app is offline mode. What that means is one of our other salesforce who go from our system from our DC to other stores, should be able to run the whole day without any major disruption, even if they're not connected, let's say because when they go into big stores, typically there's no connection there all metal boxes. So the cellular reception is not there, but most of our work that we do from our frontline is within the store. So it has to be a full offline where we have to have all the data within the device and we should be able to place orders, create inventory that records or adjust inventory, and then create invoices. All the majority of the things that we do are in the store and they should be able to do without the connection. So that's where we explored multiple options and kind of zeroed in on Couchbase where we bring all the data into Couchbase database on the device and then sync it when there is connection, but there's no connection, we still have all the data on the device and we can go do all of our duties in the stores without any issues, even if it is not connected. >> So the sales folks can be in the stores with their mobile device, doing all the transactions that they need to do with the stores, regardless of if there's connectivity. Talk to me about what happens when they get back to connectivity in that and the Couchbase database sync. >> Yeah. And the other big thing we want is instant connect. I mean, when there's connectivity, we want instant sync with the backend, right? If there's new data that comes, we need that in the device. At the same time, if I place an order, I want to send it back immediately to our backend systems so that our fulfillment starts for those. So that's very critical when we have a lot of cutoff times for our orders. So we need order as soon as we've placed to be going into the backend systems. So what happens when it gets connected, as soon as the sales folks come out of the store or when, within the story they could connectivity the Couchbased technology that we are using using the sync gateway immediately syncs the data back and forth if there's any new data that's available. So that is key for us in this particular app. >> So our transactions happening in real time or near real time. >> Yeah. So the data flow happens in real time when there's connectivity, but when it is not connected still, it doesn't have any issue with the actual transactions with the RSR that can go complete anything that. >> Got it. Okay. So there's no impediment there. In fact, it's a productivity enhancer. It sounds like for all of those sales folks out on the frontline. Tell us so millions of documents go through the system, tens of billions of dollars. Talk to me about the volume of data and the actual monetary value that's traversing the system. >> Yeah. It's huge, again, this is kind of the lifeline of the company. The sales are always the life of any company, right? So most of the sales for Frito-Lay goes through our system and we're talking anywhere between hundreds of thousands of documents that flow through back and forth between the Couch between the device and the server. So there's a lot of master data that comes like products price from customers, all that information that comes from the backend to the device and all the orders inventory and everything that gets created on the device gets flown sync back to the server. So yeah, I mean, it's, it's a very complex system. And also from the volume perspective, it's huge. So we had to build a massive infrastructure on the backend to be able to handle all this. One of the key feature is again, we have this massive data that we need to sync to the devices, but each device should only get the portion of the data that they want because a particular Salesforce only goes to a small set of 20 stores, let's say. So the data that we sync to that device is only for those 20 stores. So that's the key here. So Couchbase allows us to do that. The Couchbase sync, where we can subset the data into different portions and only send the data that is relevant for a particular device. >> So then from a, from a latency perspective, it must be pretty low latency, pretty fast to be able to get this data back to the device and to the sales person that is in the middle of a transaction. >> Yes. I mean, it's pretty, the sink is very fast. The Couchbase sync, especially user's web sockets. And we do continuous replicators where if I complete an order, the next instant it's on the server. So it's, it's we observed the speeds improved a lot. So the technology that we are using uses syncs for a long, long time compared to Couchbase, and that's another productivity gain for our Salesforce. >> What were some of the differentials? You mentioned some of the technology requirements that PepsiCo had in rearchitecting, the infrastructure, but what were some of the key technology differentiators that really made Couchbase stand out as the obvious choice? >> Yeah, so we, when we started this project, we all know the sink is the key for this whole project, because we thought the data going back and forth, we cannot really build a robust offline app. So we looked at multiple options, other providers that are doing the sync. And we also looked at building our own sink, in-house using APIs, but then we did lots of performance testing across all the options that we had at that time. And then Couchbase came above all of them pretty handily. So obviously we can coach base takes care of the sync, and then we can focus on our business process. So we can go build all the business process and not worry about how to build the syncing engine. And then that is itself a big effort. So that's what Couchbase provided us saying a instant sync engine. And then we were able to focus more on our, the app applicants, the frontline application, the sensor application. >> And those business processes. Let's talk about some of the business outcomes. We've mentioned a few already in our conversation, increased in productivity, the sales forces increased in that as well. But I imagine there's a lot of benefits for the end-user customer in terms of being able to get the transactions completed faster. What are some of those positive business outcomes that PepsiCo is seeing as a result of implementing Couchbase? >> Yeah. So you hit on a couple of them that the sync times are definitely a big factor where that will directly give more time for the sales folks to go either go to most stores, or even if they go to the existing stores, they can do more, spend more time with the customer merchandising and making sure everything is correct. So that's one, also the new app users connect with a lot of new peripherals that are not available on the previous platform. Also, the, our folks are very enthusiastic about using a new app, right? So it's like coming into the 21st century for them using such an old lab for a long time. So a lot of things that they see, they can see the images of the bags while ordering, which was not a feature earlier. Some of them are small, but they make a huge impact on our users. So, yeah, I mean, and then this is just a start that we are doing. And then once we are able to completely implement this one, we have a lot more going into, in future. I was just talking about, we can do virtual reality or show them how to sell using virtual reality. We can show a display to a store manager saying, 'Hey, I want to put a display here. And this is how it looks,' they can show it on the phone directly, than just explaining and showing some paper images. So there's a lot of possibilities. >> A lot of improvements to the customer experience. It sounds like, it sounds like adoption is quite high for your folks who are used to 20 year old technology, probably being very excited that they have a modern app. But talk to me a little bit about the appetite of the organization to continue modernizing the application infrastructure and presuming going from older technology to that 21st century, like you talked about. >> Yeah. So in other parts, we are already modernized some of these. So we have been on the journey for the last four, five years building multiple digital platforms. So one of the examples I can give is when COVID hit, there's a lot of disruption for everybody, for the consumers, so they are not able to find the products in the stores, a lot people are afraid to go to the stores to even buy products. So we reacted very quickly and opened a consumer website called snacks.com, which Pepsi never sold it to consumer directly. We always go through our stores, but the first time we open the consumer channel and Couchbase powered some of it for the backend purpose. So this is not a mobile app, it's just a desktop app, but we already have been on the digital transmission journey, even before we quickly turn into COVID for the snacks.com. And similarly, we are, doing this for our retail execution, portion of it using this project. So, and then we'll be continuing to do this going forward to enable a lot of functionality for I mean, for all of our sales, as well as supply chain and other systems, so that we can be more efficient. We can be more elastic saying if there is more demand, our backend should be able to handle all that, which was not the case before. So now we've built a state of the art backend system on cloud. So there's a lot of transmission, digital transmission going on within PepsiCo. And I'm really proud to be part of this project so that we took this to the next level. And then this is just a start. We can do a lot more. >> Right? This is just the beginning. That sounds like a great transformation for a historied company that we all, everybody knows PepsiCo and all of its products. But it sounds like when the pandemic hit, you had the infrastructure in place to be able to pivot quickly to launch that direct to consumer, which of course consumers, patience has been quite thin in the last year and a half. Talk to me a little bit about the impact to the overall organization as a result of being able to, to get more direct with those consumers. >> Yeah. So till now, again, we are the business model is we sell to the stores and then go customer. So we'd never get a direct sense of what consumer liking is. I mean, we get through some surveys and stuff, but we don't have a direct channel to the consumer, which this particular project enabled us snacks.com. So we know the consumer behavior, how they buying patterns, browsing patterns, which ones they like and including with geography and all so we learned a lot from the consumer behavior point of view for the project. And then we kept on enhancing. So one new thing we introduced was called Multipack where the consumers can come and pick, make their own Multipacks basically. They can say, okay, I need these many of this particular product, this particular product and make their Multipack and we ship them the customized Multipack. And it was, such a huge hit that we are not able to even fulfill them so much demand was there for that one, so we had to revamp and then get back. And now it's a huge thing on all the snacks.com platform. So all of this is possible because we had a digital platform underneath that supports this kind of innovation. So the new business models are just coming to life in within weeks or even few months and that's what we will be trying to do with the new platform that we're building for this app as well, where we'll bring in lot of new business models on top of we have already. >> Excellent, a lot of transformation it sounds like at PepsiCo in the last couple of years, I love the customization, that personalization route that you're going and I think that's going to be a huge hit for consumers. And as you said, there's a lot of demand , Madhav thank you for joining me today, talking about how you are modernizing the field service and supply chain application, the impact it's making for end users for your customers and for the sales folks. We appreciate your time. >> Thank you so much Lisa. >> From McCalla. I'm Lisa Martin. You're watching this Cube conversation.

>>And welcome to the cubes coverage of Couchbase connect online, Mary Roth, VP of engineering operations with couch basis here for Couchbase connect online. Mary. Great to see you. Thanks for coming on remotely for this segment. >>Thank you very much. It's great to be here. >>Love the fire in the background, a little fireside chat here, kind of happening, but I want to get into shooting, you know, engineering and operations with the pandemic has really kind of shown that, you know, engineers and developers have been good working remotely for a while, but for the most part it's impacted companies in general, across the organizations. How did the Couchbase engineering team adapt to the remote work? >>Uh, great question. Um, and I actually think the Couchbase team responded very well to this new model of working imposed by the pandemic. And I have a unique perspective on the couch space journey. I joined in February, 2020 after 20 plus years at IBM, which had embraced a hybrid in-office rewrote remote work model many years earlier. So in my IBM career, I live four minutes away from my research lab in almond and valley, but IBM is a global company with headquarters on the east coast and SU. So throughout my career, I often found myself on phone calls with people around the globe at 5:00 AM in the morning, I quickly learned and quickly adopted to a hybrid model. I'd go into the office to collaborate and have in-person meetings when needed. But if I was on the phone at >> 5: 00 AM in the morning, um, I didn't feel the need to get up at 4:30 AM to go in. >>I just worked from home and I discovered I could be more productive. They're doing think time work. And I really only needed the in-person time for collaboration. These hybrid model allowed me to have a great career at IBM and raise my two daughters at the same time. So when I joined Couchbase I joined a company that was all about being in-person and instead of a four minute commute, it was going to be an hour or more commute for me each way. This was going to be a really big transition for me, but I was excited enough by couch facing what it offered that I decided to give it a try. Well, that was February, 2020. I showed up early in the morning on March 10th, 2020 for an early morning meeting in person only to learn that I was one of the only few people that didn't get the memo. >>We were switching to a remote remote working model. And so over the last year, I have had the ability to watch cow's face and other companies pivot to make this remote working model possible and not only possible, but effective. And I'm really happy to see the results. Our remote work model does have its challenges that's for sure, but it also has its benefits better work-life balance and more time to interact with family members during the day and more quiet time, just to think we just did a retrospective on a major product release Couchbase server 7.0 that we did over the past 18 months. And one of the major insights by the leadership team is that working from home actually made people more effective. I don't think a full remote model is the right approach going forward, but a hybrid model that IBM adopted many years ago and that I was able to participate in for most of my career, I believe is a healthier and more productive approach. >>Well, great story. I love the, um, the, uh, you come back and now you take leverage all the best practices from the IBM days, but how did the, your team and the Couchbase engineering team react and were there any best practices or key learnings that you guys pulled out of that, >>Uh, the, the initial reaction was not good. I mean, as I mentioned, it was a culture based on in-person people had to be in person in person meetings. So it took a while to get used to it, but the, there was a forcing function, right? We had to work remotely. That was the only option. And so people made it work. I think the advancement of virtual meeting technology really, really helps a lot over earlier days in my career where I had just bad phone connections, that was very difficult. But with the virtual meetings that you have, where you can actually see people and interact, I think is really quite helpful. >>What's the DNA of the culture. What's the DNA. Every company's got the DNA entails Moore's law. Um, and at what's the engineering culture at Couchbase like if you could describe it. >>Uh, the engineering culture at Couchbase is very familiar to me. We are at our heart, a database company, and I grew up in the database world, which has a very unique culture based on two values, merit and mentorship. And we also focus on something that I like to call growing. The next generation. Now database technology started in the late sixties, early seventies with a few key players and institutions. These key players were extremely bright and they tackle it and solve really hard problems with elegant solutions long before anybody knew they were going to be necessary. Now, those original key players, people like Jim gray, Bruce Lindsey, Don Chamberlin, pat Salinger, David Dewitt, Michael Stonebraker. They just love solving hard problems. And they wanted to share that elegance with a new generation. And so they really focused on growing the next generation of leaders, which became the Mike caries and the Mohans and the lower houses of the world. And that culture grew over multiple generations with the previous generation cultivating, challenging and advocating for the next, I was really lucky to grow up in that culture. And I've advanced my career as a result, as being part of it. The reason I joined Couchbase is because I see that culture alive and well, here are two fundamental values on the engineering side, our merit and mentorship. >>One of the things I want to get your thoughts on, on the database questions. I remember, you know, back in the old glory days, you mentioned some of those luminaries, you know, there wasn't many database geeks out there, Zuri kind of small community now is databases are everywhere. So you see there's no one database that's ruling the world, but you starting to see a pattern of database kinds of things, and more emerging, more databases than ever before. They're on the internet, they're on the cloud. There are none the edge it's essentially we're living in a large distributed computing environment. So now it's cool to be in databases cause they're everywhere. So, I mean, this is kind of where we're at. What's your reaction to that? >>Uh, you're absolutely right there. There used to be a, a few small vendors and a few key technologies and it's grown over the years, but the fundamental problems are the same data, integrity, performance and scalability. And in the face of district distributed systems, those were all the hard problems that those key leaders solve back in the sixties and seventies. They're not, they're not new problems. They're still there. And they did a lot of the fundamental work that you can apply and reapply in different scenarios and situations. >>It's pretty exciting. I love that. I love the different architectures that are emerging and allows for more creativity for application developers. And this becomes like the key thing we're seeing right now, driving the business and a big conversation here at the, at the event is the powering, these modern applications that need low latency. There's no more, not many spinning disks anymore. It's all in Ram, all these kinds of different memory, you got decentralization and all kinds of new constructs. How do you make sense of it all? How do you talk to customers? What's the, what's the, what's the main core thing happening right now? If you had to describe it? >>Yeah, it depends on the type of customer you're talking to. Um, we have focused primarily on the enterprise market and in that market, there are really fundamental issues. Information for, for these enterprises is key. It's their core asset that they have and they understand very well that they need to protect it and make it available more quickly. I started as a DBA at Morgan Stanley back, um, right out of college. And at the time I think it was, it probably still is, but at the time it was the best run it shop that I'd ever seen in my life. The fundamental problems that we had to solve to get information from one stock exchange to another, to get it to the sec, um, are the same problems that we're solving today. Back then we were working on mainframes and over high-speed data comm links today, it's the same kind of problem. It's just the underlying infrastructure has changed. >>You know, the key has been a big supporter of women in tech. We've done thousands of interviews on why I got you. I want to ask you, uh, if you don't mind, um, career advice that you give women who are starting out in the field of engineering, computer science, what do you wish you knew when you started your career? And you could be that person now, what would you say? >>Yeah, well, there are a lot of things I wish I knew then, uh, that I know now, but I think there are two key aspects to a successful career in engineering. I actually got started as a math major and the reason I, I became a math major is a little convoluted. Is it as a girl, I was told we were bad at math. And so for some reason I decided that I had to major in it. That's actually how I got my start. Um, but I've had a great career and I think there are really two key aspects first. And is that it is a discipline in which respect is gained through merit. As I had mentioned earlier, engineers are notoriously detail oriented and most of our perfectionist, they love elegant, well thought out solutions and give respect when they see one. So understanding this can be a very important advantage if you're always prepared and you always bring your a game to every debate, every presentation, every conversation you have build up respect among your team, simply through merit. While that may mean that you need to be prepared to defend every point early on say, in your graduate career or when you're starting over time, others will learn to trust your judgment and begin to intuitively follow your lead just by reputation. The reverse is also true. If you don't bring your a game and you don't come prepared to debate, you will quickly lose respect. And that's particularly true if you're a woman. So if you don't know your stuff, don't engage in the debate until you do. That's awesome. >>That's >>Fine. Continue. Thank you. So my second piece of advice that I wish I could give my younger self is to understand the roles of leaders and influencers in your career and the importance of choosing and purposely working with each. I like to break it down into three types of influencers, managers, mentors, and advocates. So that first group are the people in your management chain. It's your first line manager, your director, your VP, et cetera. Their role in your career is to help you measure short-term success. And particularly with how that success aligns with their goals and the company's goals. But it's important to understand that they are not your mentors and they may not have a direct interest in your long-term career success. I like to think of them as say, you're sixth grade math teacher. You know, you're getting an a in the class and advancing to seventh grade. >>They own you for that. Um, but whether you get that basketball scholarship to college or getting to Harvard or become a CEO, they have very little influence over that. So a mentor is someone who does have a shared interest in your longterm success, maybe by your relationship with him or her, or because by helping you shape your career and achieve your own success, you help advance their goals. Whether it be the company success or helping more women achieve, we do put sip positions or getting more kids into college, on a basketball scholarship, whatever it is, they have some long-term goal that aligns with helping you with your career. And they gave great advice. But that mentor is not enough because they're often outside of the sphere of influence in your current position. And while they can offer great advice and coaching, they may not be able to help you directly advance. >>That's the role of the third type of influencer. Somebody that I call an advocate, an advocate is someone that's in a position to directly influence your advancement and champion you and your capabilities to others. They are in influential positions and others place, great value in their opinions. Advocates stay with you throughout your career, and they'll continue to support you and promote you wherever you are and wherever they are, whether that's the same organization or not. They're the ones who, when a leadership position opens up will say, I think Mary's the right person to take on that challenge, or we need to move in a new direction. I think Mary's the right person to lead that effort. Now advocates are the most important people to identify early on and often in your career. And they're often the most overlooked people early on, often pay too much attention and rely on their management chain for advanced managers, change on a dime, but mentors and advocates are there for you for the long haul. And that's one of the unique things about the database culture. Those set of advocates were just there already because they had focused on building the next generation. So I consider, you know, Mike Carey is my father and Mike Stonebraker is my grandfather. And Jim gray is my great-grandfather and they're always there to advocate for me. >>That's like a scheme and a database. You got to have it all white. They're kind of teed up. Beautiful, great advice. >>Thank you for that. That was really a masterclass. And that's going to be great advice for folks really trying to figure out how to play the cards they have a and the situation and to double down or move and find other opportunities. So great stuff there. I do have to ask you Maira, thanks for coming on the technical side and the product side Couchbase Capella was launched, uh, in conjunction with the event. What is, what is the bottom line for that as, as an operations and engineering, you know, built the products and roll it out. What's the main top line message for about that product? >>Yeah, well, we're very excited about the release of Capella and what it brings to the table is that it's a fully managed in an automated database cloud offering so that customers can focus on development and building and improving their applications and reducing the time to market without having to worry about the hard problems underneath and the operational database management efforts that come with it. Uh, as I mentioned earlier, I started my career as a UVA and it was one of the most sought after and highly paid positions in it because operating a database required so much work. So with Capella, what we're seeing is, you know, taking that job away from me, I'm not going to be able to apply for a DBA tomorrow. >>That's great stuff. Well, great. Thanks for coming. I really appreciate congratulations on the company and public offering this past summer in July and thanks for that great commentary and insight on the QPR. Thank you. >>Thank you very much. >>Okay. Mary Ross, VP of engineering operations at Couchbase part of Couchbase connect online. I'm John furry host of the cube. Thanks for watching.

>>Mhm >>Welcome to this preview of couch based connect online 2021. My name is Dave Volonte with the cube and we're here with couch based ceo matt cain matt. Good to see you again. Welcome >>Thanks Dave. Great to be here. >>We are super excited at the Cube to partner with Couch Base this year to share the news, the analysis from connect online 21. What can attendees expect from the event this year? What's the theme? What can people really take away? >>They were fired up, you know, there is no different. Our theme this year is modernized now and it's something that we're hearing from our customers across the world is they think about leveraging technology to get closer to their customers and at the top of every one of their strategic agendas is figuring out how to build the best applications to service our needs as our personal lives and in our business lives and we're really focused on talking about the technology that we uniquely architected to enable this that stands aspects of relational database technology and new capabilities, leveraging those people technology, putting that into an integrated platform and really supporting customers. And we love talking about what we built Dave but we love even more when our customers share what they've been doing with our platform, customers like Pepsi and Amadeus and American greetings, you're going to hear them and their development meant teams talk about how they have leverage couch base to solve some of the most fundamental application challenges and how that's really opening up new businesses for them in their end markets. >>Let's talk a little bit more mad about that, the modernized now. I mean the trends that we're seeing in in the market place, they were in motion before the pandemic. But digital digitization and modernization has really become a high priority. Talk about why in your view now is the time to modernize and what's the mandate for enterprises? >>Well look, I think digital transformation has been a focus point for some time and I think that's going to continue as we go forward. But I think as enterprise think about the challenges they have in front of them to successfully transform digitally, they may be thinking about the problem a little bit differently in light of current circumstances. Uh and what we're seeing is enterprises have the desire to innovate, but they may not always have the resources or the capabilities to do it at the place they want to. And so how do they approach this challenge first and foremost, they need a platform that can help bridge the legacy world and the new one that they can safely evolve applications and modernize, you know, workloads that were dependent on relational databases while putting them into new platforms. At the same time, they need people to do this work. So if I'm an democrats, almost an insatiable demand to build new applications, but I don't necessarily have all the people and teams and capability and skill sets needed to support that. So as a technology company, we've got to think through how do we help provide the tools that will open up more people's ability to contribute to that digital transformation leveraging things like sequel is the fact of language in the database technology allowing enterprises to repurpose workforces free up investment dollars, free up people to really focus on the next generation of properties that are going to change their businesses. And so I think the current economic conditions haven't changed the fact that digital transformation is the top of the priority list. If anything, that reinforced the urge with which enterprises need to go after this, but also the way that they need to do it. But I can't just continue to throw niche technologies of problems. I've really got to think about what kind of platforms tonight and then in the future and a couch base as the modern database for enterprise applications. This is what we're going to spend time talking about and helping customers understand the value that we can unlock for them as they invest in the couch based platform. >>Super relevant now since we last talked matt, he made some big moves, not the least of which is you're now a public company. We've been following that. But what's changed what's new product wise and maybe one of the fundamentals of the market that that your your customers and your culture or driving. >>Yeah, well let's talk about first, what's not changed? We continue to be long term oriented couch basically believe we're in truly what we call a generational market transition and the challenges in front of enterprises unparalleled. So too are the opportunities for enterprises that get this right? They will innovate and thriving in their respective markets. And so as a company, we pride ourselves in being maniacally focused at solving unmet, underserved needs in the world of databases. And really thinking through what technological challenges do we need to innovate on store, customers can take that technology and successful. That's not, that hasn't changed that, that won't change. We continue to be insanely customer focused and really studying those problems and making sure that we're adding value in everything we do from a product perspective services, how we show up to help our customers and that's really important. Um certainly as you said, it's a big milestone for the company step in the public market. We're very proud of what we've accomplished over our first decade or so of existence. But we truly believe that we've been built for this moment and that market transition that ever have referred to um that that movement into the public markets allows us to talk more broadly about all that we've built and how customers are taking advantage of our technology case in point is probably the biggest release in company history couch based server seven oh, so while we were busy taking a step into the public market, we also continue to innovate as I said and are very pleased to be a market with couch base 70 which fundamentally bridges for enterprise customers to move from relational to modern databases and do that in a single integrated platform. And we're going to talk about that connect in more detail and how application developers can re platform applications in a much more seamless way and then start to innovate in a way, you know, that they never have. So a ton of work underway. We've got some really exciting announcements which I think we'll talk about here in the second at least plant the seeds on those. But we're going to be really focused on the innovation that we've delivered up to this point because it's so fundamentally valuable to the enterprise customers we serve and couldn't be more excited to share the benefits of that. That's actually what we're going to help customers do as we go forward. >>Well, we see a lot of companies and as as we evaluated, you've hit critical mass in terms of how we think about it successful I. P. O. Your surpassed $100 million in revenue 500 plus customers talk about the opportunity for couch based to continue to grow. What's in store. What's the focus? >>Well, as I mentioned, we're going to we're going to continue to innovate and so you know, ahead of the conference. We're going to talk about some really important upcoming innovations and I'm not gonna steal too much of the thunder from the show, people are really pumped and putting that material together? We we focus a lot on ensuring that we have the best database in the market, particularly for enterprise applications. Uh and really thinking through the architecture that will support applications today and going forward and we've been really successful with that date. As you mentioned, we have not only a lot of enterprise customers and we're really proud of those customers would support what were even more proud of though. Dave is the mission critical nature the enterprise nature of those applications. These companies are truly running their businesses on applications powered by pouches as we go forward. We have almost unlimited potential for new opportunity in acquiring new customers. Um and we're really focused on that and evangelizing what we've done successfully with our existing base to new customers and their respective markets and we continue to acquire those and you know will successfully expand because of the power of our platform. We've done a lot to invest in our partner ecosystem. So you know we have many I. S. V. S. That are taking our solutions to market. We have G. S. I. S. That are building practices around couch base because our database provides capabilities that others don't and they can run their businesses and help their end customers transform with the power of couch face. But Dave what we like to talk about a couch bases, we have opportunities to really help customers once we get in. We think about many factors of growth. So when we support a customer with an application, what often happens is that application growth because the enterprises successful and they put more users in or they deployed a new new geography at the same time, they realize, wow, if I can support highly interactive, highly scalable distributed applications in this particular area, I have hundreds, if not thousands of those in my enterprise, so I can use the platform for that. Then one of the things that we focus on is giving more and more capabilities to developers to enhance the performance and the personalization of their applications I mentioned, we support the sequel query language, we've got operational analytics, we've embedded full text search, we have things like eventing all of these are elegantly architected features that allow developers to build great applications and the more that were successful in helping developers do that, you know, the more, the more the company is going to grow. Um and then on top of all that we couldn't be more excited about about cloud and couch based cloud from the very outset has been a cloud, native platform, are enterprises are running this and multi and hybrid cloud deployments, but what we really have an opportunity to do is help them and run more of the service of, of that cloud solution and we're gonna be talking a lot more uh you know, come come the show about some specifics around that offering and could be more excited about augmenting or portfolio with some new capabilities there >>lot to learn at this event. Tons of meat on the bone. Okay. Matt, we're gonna leave it right there. Couch based, connect online. It's a two day event, october 20th to the 21st. More than 80 sessions geared for architects, developers, business users, open source advocates. Now the easiest way to register, all you gotta do is go to couch base dot com. You'll see the link there. There's a hackathon with prizes. So start developing and win. And while you're there, check out the free downloads with a number of different deployment options. Couch based, connect 2021 modernized. Now we'll see you there. >>Mhm mm.

(upbeat music) >> This is Dave Vellante, and I'd like to welcome you back to The Cube's coverage of Couchbase ConnectONLINE, where the theme of this event is Modernize 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. Yup, you can find that in the constellation, that constellation in the night sky in late Feb, early March, in the Northern hemisphere. So with that little tidbit, I'd like to welcome in Scott Anderson to The Cube, who's the Senior Vice President of Product Management and Business Operations at Couchbase. Scott, welcome. Good to see you. >> Thank you very much. Thanks for having me. >> Yeah, it's our pleasure. So, you've launched Couchbase Capella. If I understand correctly, it's built on Couchbase server 7, which you launched just a few months ago in the middle of the Summer. Can you give us an overview of Capella? >> Yeah, absolutely. So Couchbase Capella, is our fully managed databases service for enterprise applications. One of the goals of launching Capella and our database as a service offering that we just announced today is, about increasing the accessibility of Couchbase. So, it's about making it easy for a Developer or an Enterprise to get up and running in just a few clicks and a couple of minutes. 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 a customer's in, and eventually into the production of their enterprise application, leveraging Capella and Couchbase Server 7. >> So let me ask you, I went pretty deep with Ravi on the, 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 guysbhave really done a awesome focus on SQL. 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 Ravi and our core engineering team have built. And we've talked about that, and I think Ravi mentioned that, the ease of SQL and applying that to a documented oriented database. and 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 of minutes later, you've got a database endpoint that is fully managed by Couchbase. 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 some of the mundane tasks of backup and recovery, scaling the environment upgrades and so forth. So it's really about ease of use making it, leveraging our incredibly robust broad platform, and then making that in different consumable model for our customers and developers and getting started really easily. The other thing that we've done, is really leveraged the best practices over the last 10 or 11 years, if some of the largest enterprises in the world using Couchbase for the mission critical applications. So we've codified those best practices. And that's how we keep that service high performant, always on, highly available. And that's one of the core value propositions that we're able to bring with Capella. It's really that management capability, global visibility of your clusters, coupled with what we believe is the best, no SQL database in the marketplace today. >> What about, what about costs total cost of ownership as you scale, a lot of times when you scale out and you get diseconomies of scale, it's kind of like, you know, you get that negative curve. What are you seeing? >> Yeah, we've done third party benchmark studies, which have proven out how we were able to linearly scale the environment and continue on that curve, as you add nodes, you're getting that incremental performance that you would expect. The other thing that we do that's really unique within in Couchbase is, our multi-dimensional 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 the cluster, or you can have dedicated nodes for each one of those services. The reason that is important is, you get work-life 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 cost. Indexes, where do 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 within the existing cluster, allows us to lower overall costs. That coupled with our blazing fast performance with our in-memory architecture, allows people to get incredible performance at scale. 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 data. >> Thank you for that. What do customers need to think about when they want to get started with Capella? How difficult is it for people to jump in? >> It is incredibly simple. It's as simple as going to couchbase.com Clicking on start your free trial. You go into 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 six to nine months is removing any friction we can in the process. Cause our goal is to give a firm 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 of support and the features that we think are appropriate for a dev cycle, a test cycle, and then inner production. And lastly, we'll 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 Couchbase. 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 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, for customers. 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 our Chief Marketing Officer in the overall team. 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 wanted a name of strength. We liked the alliteration, Couchbase and Capella together. One of the little facts may have tipped it over is, I believe in Latin, it means little goats. So we kind of played, I'm from the bay area. So I was thinking to Jerry Rice, goat, greatest of all times. So that was nice play on that also. But I leave it to them and really happy with the overall name, love the, literation, love some of the hidden meanings within that. And we're really, really excited about getting it going. So you wouldn't want me to pick the name. I get a vote, but I would say my overall influence is a little bit lower than where John's is and, and Matt Cain, who I know you spoke with previously. >> I love it. Jerry Rice definitely is the little goat. I'm from New England. So of course, we think Tom Brady is the big goat. >> I know, I grew up in that Joe Montana era. So maybe you can take that offline after this interview, we're going to have around debate, but I guess a Superbowl trophies are the ultimate measure at the end of the day. >> Oh wait, I 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? >> Yeah, exactly. >> Scott, it's great to have you on the cube. Thanks so much, really appreciate it. >> Thank you so much. I really appreciate it All right. Thank you for watching. Our pleasure. Thank you for watching The Cubes coverage of Couchbase Connect 2021. Keep it right there for more great content. (upbeat music)

(upbeat music) >> This is Dave Vellante, and I'd like to welcome you back to The Cube's coverage of Couchbase ConnectONLINE, where the theme of this event is Modernize 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. Yup, you can find that in the constellation, that constellation in the night sky in late Feb, early March, in the Northern hemisphere. So with that little tidbit, I'd like to welcome in Scott Anderson to The Cube, who's the Senior Vice President of Product Management and Business Operations at Couchbase. Scott, welcome. Good to see you. >> Thank you very much. Thanks for having me. >> Yeah, it's our pleasure. So, you've launched Couchbase Capella. If I understand correctly, it's built on Couchbase server 7, which you launched just a few months ago in the middle of the Summer. Can you give us an overview of Capella? >> Yeah, absolutely. So Couchbase Capella, is our fully managed databases service for enterprise applications. One of the goals of launching Capella and our database as a service offering that we just announced today is, about increasing the accessibility of Couchbase. So, it's about making it easy for a Developer or an Enterprise to get up and running in just a few clicks and a couple of minutes. 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 a customer's in, and eventually into the production of their enterprise application, leveraging Capella and Couchbase Server 7. >> So let me ask you, I went pretty deep with Ravi on the, 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 guysbhave really done a awesome focus on SQL. 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 Ravi and our core engineering team have built. And we've talked about that, and I think Ravi mentioned that, the ease of SQL and applying that to a documented oriented database. and 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 of minutes later, you've got a database endpoint that is fully managed by Couchbase. 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 some of the mundane tasks of backup and recovery, scaling the environment upgrades and so forth. So it's really about ease of use making it, leveraging our incredibly robust broad platform, and then making that in different consumable model for our customers and developers and getting started really easily. The other thing that we've done, is really leveraged the best practices over the last 10 or 11 years, if some of the largest enterprises in the world using Couchbase for the mission critical applications. So we've codified those best practices. And that's how we keep that service high performant, always on, highly available. And that's one of the core value propositions that we're able to bring with Capella. It's really that management capability, global visibility of your clusters, coupled with what we believe is the best, no SQL database in the marketplace today. >> What about, what about costs total cost of ownership as you scale, a lot of times when you scale out and you get diseconomies of scale, it's kind of like, you know, you get that negative curve. What are you seeing? >> Yeah, we've done third party benchmark studies, which have proven out how we were able to linearly scale the environment and continue on that curve, as you add nodes, you're getting that incremental performance that you would expect. The other thing that we do that's really unique within in Couchbase is, our multi-dimensional 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 the cluster, or you can have dedicated nodes for each one of those services. The reason that is important is, you get work-life 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 cost. Indexes, where do 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 within the existing cluster, allows us to lower overall costs. That coupled with our blazing fast performance with our in-memory architecture, allows people to get incredible performance at scale. 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 data. >> Thank you for that. What do customers need to think about when they want to get started with Capella? How difficult is it for people to jump in? >> It is incredibly simple. It's as simple as going to couchbase.com Clicking on start your free trial. You go into 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 six to nine months is removing any friction we can in the process. Cause our goal is to give a firm 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 of support and the features that we think are appropriate for a dev cycle, a test cycle, and then inner production. And lastly, we'll 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 Couchbase. 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 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, for customers. 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 our Chief Marketing Officer in the overall team. 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 wanted a name of strength. We liked the alliteration, Couchbase and Capella together. One of the little facts may have tipped it over is, I believe in Latin, it means little goats. So we kind of played, I'm from the bay area. So I was thinking to Jerry Rice, goat, greatest of all times. So that was nice play on that also. But I leave it to them and really happy with the overall name, love the, literation, love some of the hidden meanings within that. And we're really, really excited about getting it going. So you wouldn't want me to pick the name. I get a vote, but I would say my overall influence is a little bit lower than where John's is and, and Matt Cain, who I know you spoke with previously. >> I love it. Jerry Rice definitely is the little goat. I'm from New England. So of course, we think Tom Brady is the big goat. >> I know, I grew up in that Joe Montana era. So maybe you can take that offline after this interview, we're going to have around debate, but I guess a Superbowl trophies are the ultimate measure at the end of the day. >> Oh wait, I 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? >> Yeah, exactly. >> Scott, it's great to have you on the cube. Thanks so much, really appreciate it. >> Thank you so much. I really appreciate it All right. Thank you for watching. Our pleasure. Thank you for watching The Cubes coverage of Couchbase Connect 2021. Keep it right there for more great content. (upbeat music)