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

(upbeat music) >> From our studios in the heart of Silicone Valley Palo Alto, California. This is a CUBE conversation. >> Hello everyone. Welcome to this CUBE conversation here at our Palo Alto CUBE studios. I'm John Furrier, host of theCUBE. Got a great conversation here with Matt Cain, CEO of Couchbase. Matt, welcome to theCUBE. >> John, thanks for having me here. >> So it's great to have you on because we've been following Couchbase really from the beginning but in 2011 that was the big movement with Couchbase and Membase coming together. Since then quite a tear. Couple of things, one from a business standpoint, good mix of you guys. And then you've got the cloud trend just absolute change the game with scale. So enterprise is now a reeling, cloud is there, the roll of data's changed. Now data's now a part of everything. This has been a big part of the successful companies in this next cloud 2.0 or this next shift. Give us an update on Couchbase. What's going on with the company? You've been the CEO for a couple of years, what's new? >> Yeah, so I'm 2 1/2 years in, John. It's been a great ride so far. Let's talk a little bit about how successful the company is and then we'll spend some time on the market. We just finished the first half of our fiscal year and the business is on a phenomenal trajectory. We're up 70% year on year. Average contract values up 50%. Total contract value up over 100%. We now call 30% of the Fortune 100 customers. So in terms of business success we're really proud of what we're able to do and the problems that we're solving for our customers. The backdrop, and what we're so excited about is the market transition that we're participating in. And it's our belief at Couchbase that the world of databases represents the single biggest market transition that's going to occur in technology over the next couple years. And I think there are two fundamental drivers behind that transition which you talked about. One of them is a technology disruption and the other is business disruption. On the business side we believe deeply in digital transformation or the fourth industrial revolution. And we spend our time going around the world talking to enterprise customers and everyone of 'em is figuring out how to use technology to get closer to their customers and change their business. In order to do that they need to build next generation applications that change our customer experience as both professionals and our personal lives. To enable that though, you need a completely different approach to the database. And how you manage the underlying data to enable those experiences and Couchbase sits at the intersection of those two transitions. >> Want to get into some of the database software dynamics from being a software company, a database company. You guys are, you're on a good wave, you've got a good surfboard as we say in California. But the couple of things I want to get your thoughts on, you see the database market like the oracles of the world. The database that rules the world, that's changed. Now there's multiple databases out there. Different needs for different workloads. And then you've got open-source. So you've got the two things going on I want to get your reaction to. One is the changing landscape of the database market. And two, the impact of open-source because both have been changing and growing and evolving. What's your reaction to those two dynamics? >> So let's talk databases first. I think to reflect on databases one needs to think about the applications that those databases have been architected to support. And if you look at legacy solutions, legacy systems, it was really built on relational technology. And the applications those were optimized for and have been really running for the last many decades were big monolithic applications. And I like to say the implementation of one of those at a large financial firm in New York probably wasn't much different than a consumer company in Seattle. That is changing now in the world of microservices and customer experiences and applications demand a different type of database. And so as we think about what is an application literally everything that we do between the human world and the digital world goes via an application. Whether it's our, you know, checking our banking statements, how we engage with our health care provider, how we travel, how we buy things, whether we're in a store or we're doing it from the comfort of our home. Everything is via an application and what we've come to expect is I want that application to work my way which is different than your way. Well that's a very different thing than legacy applications that were built for CRM or ERP and so databases are going through this big transformation because of that business transition that I talked about where we as consumer are demanding different ways of engaging. And if you look at enterprise success in digital transformation it's very tied to the experiences that they're creating which necessitate a database that is capable of handling those. So we're seeing a massive shift in database technologies or proliferation of new companies that are supporting next generation applications. With respect to open-source, when I talk to enterprises they want the flexibility of a new way of acquiring technology. And people are very used to, "I want to examine things "in the way I want to learn about it. "And I want to play with technology "to make sure that it's going to meet my needs." In the case of databases, does it have the scale and performance? Does it have the usability? And so as an open-source company we want to enable our application developers, our enterprise architects, our dev-ops teams to use the technology and see what's it like. And I think enterprises really appreciate that model. So I think open-source is not only unique to databases, it's how enterprises want to-- >> And certainly is growing and changing as well. So you mentioned open-source and databases. I want to get your thoughts on the cloud impact because if you look at the success of Amazon which I call them the leaders and they won the cloud 1.0 game, or the first inning, or the first game of the double header as some say. APIs led itself well to decoupling and creating highly cohesive workloads. Using APIs and (mumbles). There you got to store data in the databases. You might have one workload with one database and another workload using other databases. So have you have a diverse database landscape. >> For sure. >> So that's kind of out there. So if that's the case how do I as an enterprise deal with this because now I'm thinking, "Okay, I want to stitch it all together. "I got to maintain security. "Now I'm dealing with multiple clouds." It's become a discussion and design point for dealing with all these new dimensions. What's the mind of the customer in all this? >> Yeah, and on top of that I want to do it without dramatically increasing my total cost of ownership. And so I talk a lot to enterprises that represent that very challenge. What they say is I have to change the customer experience. In order to do that I need to understand who they are. What are their preferences? What inventory do I have as an organization? What do I have in physical locations? What we talk about is different data silos. And the reality is data has been in those silos for a long time and in some cases it's not coming out anytime soon. So one of the new approaches with data platforms is how do I take advantage of existing investment and infrastructure and layer in new technology platforms that can sit between the application and the legacy systems? And then you can suck that data into a data store that is helping feed the applications on a real time basis whether that's in the cloud or out to the edge. And Couchbase is one of the examples of a database that can handle that but can handle it at scale unlike any other company on the planet. So when we talk to customers it's how do you extract all that different information which has rich potential if they application logic can present it in a way that's customized but do that in a way that's constantly on, available from anywhere in the network topology and reliable. So it is a challenge and it's one of the greatest computer science challenges in the enterprise right now. >> On that point I want to ask you, what's the number one story or trend that people should be paying attention to? >> Yeah, so you asked a question on cloud, which I think is fundamental, and enterprise is like pay as you go models and utilization based economics which make complete sense. A lot of the architecture therefor is being driven in a centralized manor. So bring information into centralized cloud take advantage of bundling effects. I believe that one of the best kept secrets if you will or biggest trends that people aren't spending as much time on is edge. If you think about us in this studio right now there isn't a cloud sitting behind us and yet you're working on your machine, I was on my device a moment ago and I'm expecting real time information across all my applications. We are constantly manipulating, moving, accessing data and we expect to be able to do that at all times. Well in order to do that at the scale in which we're talking you have to have database technology at the edge. And by definition if you're expecting a roundtrip of data processing, which you're potentially doing, is increasing latency. And that's if you have a reliable connection. If you don't have a reliable connection you're dead in the water with it with that application. So if you think about the future of healthcare, if you think about next generation retail, if you think about connected homes and connected cars, the reality is we're going to expect massive processing of data out at the edge. And I think data platform companies have to be mindful of what they're architecting for. Now Couchbase is uniquely positioned in NoSQL databases that we can run in any public cloud and we can run that same platform out to the edge and orchestrate the movement of applications and data between every point of the network topology. And that's when our enterprises say, "Wow, this is game changing technology "that allows me to serve my customers "the way they want to be served." >> Most people might not know this about you, and I'm going to put you on the spot here, is that you had almost a 10 year run at Cisco. >> Yeah, that's right. >> From the 2000 timeframe. Those were the years that Cisco was cutting its teeth into going from running the internet routes to building application layers and staring see... And the debate at that time was should Cisco move up the stack. I'm sure you were involved in a lot of those conversations. They never did and they're kind of staying in their swim lane. But the network is the network and we're in a distributed network with the cloud, so the question is what is the edge now? So is the edge just the network edge? Is it the persons body? Is it the wearable? How do you guys define the edge? >> I think the edge is constantly being pushed further and further, right? One of the things that we talk a lot about is mobile devices, right? If we think about the device that we as humans ultimately touch at the end where we're not dependent on sensors and things, it is our mobile devices and we all know the impact that's had. I'd be willing to bet you that cup of coffee that you have Couchbase database running in your mobile device because we can actually embed it inside the application and allow the application architect to determine how much data you want to use. But the way we've architected things is we think for the future. This isn't just mobile devices, this is the ability to put things directly into sensors. And if we think about how applications are working the amount of data that you can draw with machine learning algorithms, which we've enabled in our latest release, imagine a world where we're embedding a database instance inside of a sensor. So companies aren't quite there today, but we're not that far off where that's going to be the case. >> Well I bring up the Cisco example because you obviously at that time the challenge was moving packets around from point A to point B. You mentioned storage, you store things from here to there. Move packets around in point A to point B. That's the general construct. But when we think about data they're not packets you're talking about sometimes megabytes and betabytes of data. So the general theme is don't move data around the network. How does that impact your business? How does that impact a customer? Because okay they maybe have campuses or wide area networks or SD-WAN, whatever they got. They still want a instrument, they still want to run compute at the edge, but moving the data around has become persona non gratae in **. So how do people get around that? What's the design point? >> So you and I remember these examples when we use to go into conference rooms and ask for ethernet cables, right? The days of what is my wifi connectivity weren't there yet. If we think about that philosophical challenge that was I'm used to a certain experience with connectivity, how do I enable that same connectivity and performance as I get further and further away from the central topology? And so what we did at Cisco is put more and more sophistication into branch routing and make sure that we had reliability and performance between all points of the topology. The reality is if you were to take that same design approach to databases, what you end up with is that centralized cloud model which a lot of companies have chosen. The problem with it occurs when you're running truly business critical applications that demand real-time performance and processing of massive applications. And so-- >> Like what, retail? >> Yeah. So at Couchbase what we've decided to do is take the data logic where the data resides. So we actually now call four of the top 10 retailers in the world customers. And what they are doing is changing our experience as consumers. Omnichannel. When I walk into a store, imagine if you're at a do-it-yourself retailer, somethings popped off the back of your washing machine and you say, "I don't know how old the washing machine is. "I don't know what the part is." Go into one of these mega stores that we know, with the application now via Couchbase in a mobile phone I could take a picture of that. With machine learning algorithms I'm now running technology to say, "Do I have this in inventory?" "What is it compatible with?" "Oh, and it happens to be on aisle 5." Or, "We don't have it and we're going to ship it out." I mean that's game-changing stuff. Well to enable that use case I need to understand who you are. I need to know what you've bought before. I need to understand our product catalog, what things are compatible with. You're literally storing, in that case, three or four billion instances in a data store that you need to access on a real-time basis. >> In milliseconds. >> In less than 2 1/2 second millisecond response rates. To make the challenge even more exciting, those customers come to us and they say, "Well what if there's a hurricane?" "What if there is no internet connectivity?" "What if I don't have a cellular connection?" I still want my users to have a great customer experience. Well now all of a sudden that isn't an extension of a cloud, that becomes it's own cloud. Now to orchestrate the movement of information and applications from that point and have consistency across all your other stores, you need to figure out orchestrating applications, orchestrating massive amounts of data, having consistency. And so the way to do it, bring the data logic where the data resides and then really understand how applications want to move things around. >> So first of all, my database antenna goes up. The comparison of the old days was you had to go to a database, run packets across the network, access the database, do a lookup, send it back and then go back again. >> Right, right. And that's not possible. That's interesting modern approach. But you also mentioned all that complexity that's involved in that. Okay, no power or no connectivity you have to have an almost a private cloud instance right there. I mean this is complex. >> Very complex. >> And this is some of the kinds of things we saw with the recent Jedi proposal that Amazon and Microsoft fought over. Microsoft won to deal with the battle fields. All this complexity where there's no bandwidth, you got to have the data stored locally, it's got to use the back hall properly. So there's a lot of things going on in the system. There's a lot to keep track of. How do you guys manage that from a product standpoint because there's somethings are out of your control. >> Yeah. >> How does Couchbase make that scale work? >> So that's a great question. Let me again complete the problem statement which is databases need to account for all that complexity but application developers and dev-ops teams don't want to deal with the specifics of a database. And so when we're selling into enterprises at this magnitude we need to be very relevant to application developers where they want speed and agility and familiarity of tools they know and yet we need to have the robustness and completeness of a platform that can literally run business critical applications. And so part of the power of Couchbase is that we engineer with extreme elegance, that we put a lot of that sophistication into the database and our job is to write the code that manages that complexity. But what we also do is we go to enterprise and we say we give you the full power of this NoSQL engine that is in memory, shared nothing, scale out, highest performance on the planet but we allow you all the power and familiarity of the language you know which is SQL. You've got this, I'm sure back to your database education you were familiar with, SQLs a programing language, well there's an entire world of database people and architects that understand that as an interface. So how do I account for that complexity but then go to you and say, "You know that language "that you've been speaking the whole time "talking to your old database? "Well you can speak with that same language "on your new database." And that's how you can really break through enabling customers to modernize their applications with all this complexity but do so in a way that they're comfortable with and is aligned to the skills that they-- >> So you extract away the interface, or language NoSQL I know there are others and modernize onto the covers? >> Correct. >> And at scale? >> At the highest scale. >> All right, I got to ask you about multi-cloud because multi-cloud is something that we were talking before we came on camera around cloud sprawl, inheriting clouds, M&A. Companies have multiple clouds they're dealing with but no one's, well my opinion, no one's architecting to build the best multi-cloud system. They're dealing with multi-clouds and design point which you mentioned which is interesting. I want to get your thoughts on this because you're hearing a lot of multi-cloud buzz. And it's a reality but it's also a challenge for application developers. And I want to get your thoughts on this. How should people thinking about multi-cloud in your opinion? >> Yeah, so my perspective starts with what we hear from our customers. And our customers say for truly business critical applications that they are running their business on, whether it's core booking engines, customer platforms, the touchpoint between users and stores, they say, "Look, I need to design a system "that's reliable and higher performing "and public cloud is a reality. "At the same time I have legacy data center on-prem, "I've got things out at the edge," and so they have to architect a multi-cloud, hybrid cloud, and distributed environment. And so depending on the layer of the stack that you're in I think the cloud companies would talk about their multi-cloud strategy. I come at it a different way which is how do we build a data platform that supports the applications that demand a hybrid multi-cloud environment? And so when we have a certain application that's running on-prem, how do we alive for a reliable failover instance to be running in a public cloud? To me that is truly fulfilling on the demands that enterprises have. And so I think multi-cloud is a strategy of all enterprises. Giving the flexibility with things like Kubernetes to avoid cloud lock in. Making sure your system can handle migration of workloads and active, active, active, passive scenario. I think that's our approach to multi-cloud. >> It's interesting, again back to this Jedi thing which was front and center in the news. Kind of speaks to the modern era of what the needs are. The Department of Defense has a multi-cloud strategy, they have multiple clouds, and well turns out Microsoft might be the sole source. But their idea was it's okay to have a sole source cloud for a workload but still deal within a multi-cloud framework. What's your thoughts on this? Some people are saying, "Hey, if you've got a workload "that runs great on cloud, do it." >> Yeah. I don't want to make that decision for the enterprise, I want them to determine what the best instance is based on the application that they're enabling. So I ask all my enterprise customers, "How many applications do you have in your environment?" Thousands of applications. It would be wrong for me to go dictate and say, "Well I have the answer "for every one of those applications." Instead we want to build a sophisticated platform that says look, if these are the requirements, the performance requirements, run your database in this instance and you determine if that's the best for you. If you have a legacy application that needs an underlying mainframe or relational database, that's fine. We're not asking you to forklift upgrade that. Put the database in there that's going to give you the performance and requirements you want. And so again, it's where do application developers want to stand up their application for the best performance? I'll tell you what, in the 2 1/2 years I've been at Couchbase I've sat down with Fortune 100 CIOs that have absolutely told me, "Here is our cloud strategy "with public cloud vendor number one." Come back two years later and they said, "We have shifted for X, Y, and Z reason "and we are going to public cloud vendor number two." If we had chosen one specific deployment and not given thought to how enterprises are eventually going to want to have that flexibility we would be having a very different conversation. And so when we talk about we're enterprise class, multi-cloud to edge, NoSQL database, it's giving enterprises this flexibility at a database-- >> So on that example of I went with cloud number one and then moved to cloud number two, was that a I'm stopping with cloud one going to cloud two or I'm going to move a little bit to cloud two or both? >> I think it varies depending on the CIO that you're talking to. It could be they didn't handle GDPR the way I wanted to or it could be they're not deployed in a certain geographic reason. It could be-- >> Capabilities issue. >> Capabilities. Could be business relationship. You know, I have a particular commercial relationship over here therefor I have an incentive to move here. Some of 'em have dual strategies, so I think it's very dangerous for companies like us to try to-- >> Beauty's in the eye of the beholder as I always say with cloud. You pick your cloud based on what you're trying to do. Final question, security obviously, cloud security you're seeing. Amazon just had a recent even called re:Inforce which was I think the first cloud security show, RSA, there's a bunch of other shows that go on, they're all different. But security clearly is being baked in everywhere. Kind of like data, kind of horizontally embedded, need real time, you need a lot of complexity involved. They want to make it easier. What's your view on how security is playing out for Couchbase? >> Look, it's a paramount design principle for us. And we think that to build a database for business critical applications you need to have reliability, you need to have performance, you need to have scalability, you have to have security. So it's part of how we think about every component from cloud to edge and everything in between. How do we have encryption? How do we have multi-factor authentication? How do we ensure that not just securing the data itself, but how do we give the operational controls to the database teams to orchestrate the movement of data and synchronize it in a reliable way. So absolutely important to us because it's important to our customers. >> Awesome. Matt Cain, CEO of Couchbase here inside theCUBE for CUBE conversation. Matt, I want to give you a chance to get the plug in for the company. Give the pitch if I'm a customer or prospect. Hey Couchbase I heard a little buzz. You guys got momentum going on, got good references. What's the pitch to me? >> Yeah so look, Couchbase is the only company on the planet that can make the following claim. We bring the best of NoSQL with the power and familiarity of SQL in one elegant solution from the public cloud to the edge. So let me walk through that. Our architecture was enabled for the highest performance in the world. Billions of documents. We have a customer who on a daily basis is running 8 million operations per second with less than two millisecond response time. Their business is running on Couchbase. You can't do that if you have the best data schema, the architecture for scalability, scale out, do that at high total cost of ownership. At the same time we want to bring the familiarity of programing languages that people know so that application developers don't have a big barrier to entry in deploying Couchbase. And that's where we've uniquely enabled the SQL query language for both query's, our operational analytics capability, that combination is extremely powerful. To be able to run in anyone of the public clouds, which we do via the marketplace or customers bring in their own nodes to their instances knowing that that's a changing thing per our conversation. But having a seamless integrated platform where you can run the same query in the public cloud as you can at the edge and then synchronizing that back together, that is a very powerful thing. One elegant platform we have, you know, we're a multi-model database. We can run a key-value cache, we can run a JSON database. We give you advanced querying, we give you indexing. To do that in one integrated platform no one else has thought about that and future proof their solution. Let me give you an example of how that all wraps up. One of the more innovative industries right now believe it or not, are cruise lines. And so we talk about digital transformation which is by definition customer experience. Well if you're in the cruise line business, if you're not creating a great customer experience, it's not like airline travel where you've got to get from point A to point B so you chose the best. This is I'm opting for an experience if this isn't great. so one of the most leading edge cruise lines out there has deployed Couchbase and they give every passenger a wearable. That wearable now fundamentally changes the interface between me as a passenger and the physical boat, the digital services, and the other people on the ship. And this is in a world... It's a floating device. There is no cloud, there is no cellular connections. So let's say we happen to be on the same ship. We end up at sports bar after we drop our family off, maybe we're talking databases, maybe we're talking something else. And we have beer, we have a second beer, what we don't know is that this cruise line is using our device. They know who we are, they know where we are, they're using geospatial technology back in e-commerce. They have a hypothesis that we're now friends, right? Or at least maybe we want to see each other again. Unbeknownst to us the next day we get a promotion that says 50% off at the sports bar for the next game. Wow that's great, I'm going to go. And then I run into you and it's like, "Wow, what are the chances that I run into you?" Well the chances in the old world very slim. The chances in new world very good. If I had little kids the digital content in the cabin is different. If there's a movie getting out how it navigates me around the ship is different. All of this is empowered by massive amounts of data processing, data collection and they've embedded that now in a device. Now if you're in that business and now you've got weeks worth of information on what we like, ship comes back to shore, how do you take all that information, extract it back to a cloud, improve the algorithm, start to offer different shipping option. They're literally changing the physical display of the boats to optimize customer experience. So think about that. Power of processing massive amounts of information in real time. If I'm getting a promotion and it's too late and I miss a game, does me no good. The combination of all those different data silos, right? Doing that where application developers can be agile and swift and make changes in an innovative way and stay ahead of their competition. Cloud to edge. Right? I mean that's literally a ship comes back, it goes to cloud, it enables it in this consistent... We're the only company on the planet that can do that. >> Lot of complexity involved. >> Yeah. >> Awesome. Quick plug. Are you guys hiring? What's going on with the company? What are you looking for? >> As quickly as possible. Based on our conversation earlier and your knowledge of databases, we're looking for quota carriers and engineers. So if you want to come on over we're-- >> I was thinking about the cruise ship and having a couple of beers with you watching some sports. My (mumbles) says >> Sounds like sports-- >> "Hey John's had so many beers "why don't you hit the tables?" >> Sounds like-- >> "We'll take your money." >> Sound like more a rep than an engineer. (both laughing) >> Matt, thanks for coming to theCUBE. Really appreciate it. Matt Cain, CEO of Couchbase. I'm John Furrier with theCUBE. Thanks for watching. (upbeat music)

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

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

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

>> Narrator: Live from Orlando, Florida. It's theCUBE. Covering Accelerate 19. Brought to you by Fortinet. >> Welcome back to theCUBE. We are live in Orlando, Florida for Fortinet Accelerate 2019. I'm Lisa Martin with my co-host for the day Peter Burroughs. Peter and I are pleased to welcome back to theCUBE Patrice Perche, the senior executive vice president of world wide sales and support from Fortinet. Patrice, it's a pleasure to have you, fresh from the Keynote Stage, here on theCUBE program. >> Yeah, well thank you for inviting me here. It's a great opportunity. >> So lots of people this morning and an energy infused keynote starting from all this loud music that I loved and helped wake me up, so thanks to your events team for that. About 4000 attendees, >> Patrice: Yeah. >> From 40 countries. You have a ton of partners here. You can hear a lot of the noise behind us. I'd like you to share with our audience the connection that you made in your keynote about what you guys shared last Accelerate 2018 and the connection to the world economic forum from just a few months ago. >> Okay well, the last year we definitely in fact exposed our strategy in term of the product, in term of the go to market and of course how we can increase in fact the value proposition to our customer, it was all about the fabric and the eco-system that we build around the fabric. So we have been of course since now 12 months working hard on expanding and growing what I call the Phase two of the fabric and when Cain went to Davos which the World Economic Forum is held early in January. And when we got all this, I would say a vision from Klaus Schwab which is the Chairman and Founder of the World Economic Forum. Explaining that the false revolution that we are all going through. The Cyber Security its a massive, I would say problem for them and it will be a key point for the future because they will enable, in fact, most of those take technology and use it that we will go for this revolution, so >> Peter: It's intrinsic. >> It's intrinsic, they call it guardian. So it really is something that if we can't, fix this problem, it's all about digital trust. So none of the user, you, myself we will not trust maybe voting system, or you cannot trust. We know that everything is going digital. And they expressed the need for of course the education, because you need to educate and you need to, increase the skilled people especially with cyber-security as we have a huge shortfall about 1.5million, some say even two million for next year. They need also need to work as an eco-system. So, for them the eco-system is really to see public, private collaboration but also Government, technologies, companies like us. And that's in fact the purpose of Davos. To bring all this different, in fact groups and be able to talk and share and define some line for the future. And for us of-course, the concept of the eco-system is all about building around in fact this major problem that we are facing, has all the traits. In fact, a collective approach where everybody can add value. We as a vendor we build technology, we build a lot of value but we can't be with each of the customers. So and we want to build a partnership not only with the partner but also with the customer because cyber security is a real time problem. So when something happen, you need to jump, and you need to make sure that all the line is set and then everybody can work together to fix the problem. So this eco-system really resonates value well for us after we was talking last year at the Accelerate. And the last I will say pillar for the Economic Forum is about of course Education and clearly I was mentioning one of the Engineers from the SERP which is nuclear agency in Europe Januity she said that 3D, of course the problem is that with these robots we will have a lot of jobs that will be omitted. So they talk about 800 million. So it's a massive number but it sees more than an opportunity to up-skill people. So the education is really helping of course especially the young generation to go and to up-skill it and especially on the cyber security. Because, as everything is going digital, we have to secure everything so it's really, these pieces will grow much beyond that what we think today. Those three pillars are the Education, the Eco-system and of course the Technology. And the good news is that Ken was representing in fact cyber security at the Davos, so it was also a great moment for us to see in fact pushing 14 at that stage of level of discussion so. Those three pillars: Education, Technology and Eco-system of course fit very well with our strategy that we build and that's why I decided to share a bit this morning. It's not everybody going to such a place. And what really resonate well in term of the strategy and the vision we are in fact pursuing so that's what we are doing. >> So I want to build on something that you said to do so I want to paraphrase. Peter who is much smarter than I am, Peter Drucker who observed many years ago there's a difference in strategies between what he called: value in exchange was his presumption that what I am selling is valuable. And value in utility which is a presumption that the value stems from how the something is used. And that notion of partnership that Fortinet has put in place with its customers so they can get value in utility is so crucially important. And you talked a bit this morning about you know the different levels of customization, and how you are going to allow customers to engage you and apply technology to suit their business. Could you take a bit about that especially based on your experience in the field? >> Yeah so as I mention I think we, it has been also our sales strategy from day one. So we always consider that in order to succeed, we need to work through the partners and through the people that are very close to our customer. And as technology evolves of course it's a real challenge to keep them at the level. Even for us, internally, we used to understand and be always at the top level about the new technology that we are putting in place. We imagine that, just for the employees, it's a challenge so we do a lot of training. But then for the partner it's another challenge. So, I think we have been always trying to help them to of course evolving on this expertise, but we don't see that the cloud of course there is a certain I will say a trend about Okay lets go Direct because we don't. The cloud can allow to sell direct to the customer so you don't need those channels. So there's no value for them. We don't see that in the cyber security because it's a much more complex environment and I think that is why we have been successful. We even see some of our competitor, they tempted to go on this direction. I think it's maybe one of the challenges we'll face in the future. So for us they key message I was trying to give this morning to the partner is really that we count on them, it's a partnership, it's very important and of course when we adapt our partner program we want to learn from them to make sure that the three pillars of this program will fit well with their, in fact, view because of course we are from a vendor in certain perspective, they have of course a different perspective on their side. What I was mentioning the goal to market because we see that some are very specialized on the cloud, some are specialized on the premise. We have to define what is the go to market here. What kind of expertise there are in fact having because as you can see we have very broad product of frame cover, you know from almost everything, so from OT, IT, even imbedded. So, we are working with partners that are, as an example, on the connected car. That's for maybe the next two years where we will secure those car. They are not the typical or traditional partner that you see on the networking business so, we try to adapt in fact our engagement with them and make sure that in fact we build a value proposition that can fit in fact for the customer requirement. So it's really about be very close and try to have a bit of a-la-carte kind of approach. And not try to enforce a very historical view that we had in fact, to be honest. But okay, you have like three tiers, depending of level of business and then you sign. So it's really moving away from that. >> I want to stay in this notion of partners because I think it's so crucially important. You talked about the skills that they have the capabilities that they have, but your partners in general are amongst the companies that have to learn the most about cyber security. Because they are the ones that are trying to match technology to the outcomes the customers have. That leads to a question about your education programs. I got to believe that there is, that even as you're trying to educate your enterprise customers, you're also really investing in your enterprise, in upgrading and up scaling your partnership. Talk a bit about the relationship of education and Eco-system from a very practical standpoint. >> Yeah so it's a very good point because of course we need to help them to evolve and as an example we have seen traditional IT partner, interested to evolve on this OT security but they didn't have too much skill so it was new for them. So we see the purpose of building this NSC training vocation course which we have eight level, which started in 2015 and we have about now almost 200 000 certified engineers. A very large portion of those Engineers come from partners. So, on this program, in fact the origin of the program, depending on where you want to play. If it's cloud, you will have to go for NSC4. If you want to go beyond a OT, it can be NSC5. We build in fact this expertise and we ask them also to of course follow those course so the engagement with us, the requirement will be also that they have the right certified Engineer. Depending on level of engagement they want to work with us. So we build this course which is a lot of work and we have a lot of, a big team to make this happen. We have to refresh constantly because it's evolving almost every day. But as for this, the great value, you may have seen it pass on the networking sites. Cisco made a bit similar approach, which was very successful. I think we went like three years ago on thinking about this and that's what we are achieving right now and we are in fact the most I will say advanced in such a report and I think it's all NSC certification is becoming a bit stand out in the market. Both from end-user but the partner. And even going as we was mentioning, we are also working with the Academics to build in fact and train in fact new Engineers that will come in the market in the next two to three years. So we help them on, it's not pure about product, it's really about cyber security expertise that we have and of course we help them on understanding a bit how the Fortinet value can deploy on the customer, so that aspect and we try to target of course young I will say people going for university but also veterans who we had program to bring those veterans because they're also looking we are talking about up skilling. That's a perfect example on bringing a change to them. And I think it's high level, maybe it's a bit, you know think that we have a high potential. But we want of course to help on resolving the overall challenge to be unemployed. I can tell you that if you invest time and you get a certification on cyber security you will never have any problems with a job. So that's a bit the overall idea we have behind this education and certification. And truly the partner, I will say, evolution in terms of their expertise, it's based about this NSC. >> Alright Patrice as we kind of get towards the end here, let's talk about outcomes. Peter mentioned that word, I know that when I was looking at my notes here that in Q4 of 2018, service providers, and managed security service providers represented 11 of the top 25 deals. You guys also closed a massive seven figure deal in Europe. Let's talk about outcomes that Fortinet and your partner eco-system are helping businesses achieve at the business level. Not just in terms of obviously improving security but are you helping businesses generate new revenue streams, skip to new products on market faster, identify attacks and become pro active? What is one of those really key outcomes that you are proud of? >> I think the, and I was part of the presentation last year. We all, I would say on this digital transformation journey. Whole company, even us. We're evolving with much more tools, much automation. So I think every sector, whether it's public or private company, has to go for this evolution. The biggest challenge is all about digital so again the blocking point is about security. So last year we explained about how we can help with positioning our platform in the security fabric to run to this obstacle and that was the purpose of the security transformation that we was talking last year. And I know it's some, even complete as relayed a message, it was interesting that it was part of all. So I think it was really trying to unlock this digital transformation that add business benefit because at the end this whole, those company will evolve in the future, generate more profit, be more efficient, leverage, I would say, the data that they are collecting from almost everywhere. From customer but also the sensor, and transform this to a more business intelligence and then I will say generate in fact future revenue and future dollars from that. That has been a bit the idea behind. So we definitely help on evolving and going through this digital transformation journey. I think we had few example of course as one of our customers, they deploying world wide on their gas-station. A better customer journey. Typically of course you calm, you try to make your gas and you want to be connected. And they try to increase of course by upselling a lot of things. So of course you have your go for the coffee machine, you can even buy many goods. We have been deploying you know, with secure access so they have secure access they go for the internet so that's where we play with segmentation. But our wireless which is fully connected also to the Fortigate and the analytic tools allow them to do business intelligence in term of where people are moving inside you know the shops. And then, you know, redesign and rethink about okay, how they move here. So that's, that allow them to accelerate even more business or decide that maybe this spot doesn't work well, so they push that to the side and they evolve. That's depicted the value of all this intelligence and we can grasp from the data that we collect to transform to a business value. >> So I want to make one comment before we close here and that is that I don't know the degree to which people really understand the relationship between secure networking and digital business. Data is an interesting asset. It could be shared, it could be copied, it could be easily corrupted. In many respects over the next five years we believe that people will recognize that network security is the basis for privatizing data. It is what you do to turn data into an asset. I don't think people have made that connection, to the degree that they need to. >> No I agree, I agree because maybe the mindset they think about network, they think about wired. In fact we are talking about 5G, we are talking about Wireless so the data is that what we want to protect because we don't want that people stole your personal information or even company. >> It's more than protect. You want to create the asset. >> Yes, we integrate the asset. And then of course when we talk about network it's no longer wires, of course it's much more virtual I would say networks. And that's the misinterpretation and why they feel okay the network is moving away. No, it's even more in the future. And as Cain mentioned early this morning: I think the edge will become much more important in future because the compute power that we are having now on every device and even. That will in fact allow to of course generate much more data. Yeah and you need to protect. You notice when you need to go and to consolidate this into the cloud. So it's really, the age will become a very important aspect. But this will be a hybrid and that's what we feel as Fortinet we've been building in fact the very comprehensive offer and to the partner and to our customer. We just want, in fact to give them the time to move at their pace. But they have everything ready for today. That's a bit the concept. >> Well if only we had more time Patrice, we could keep going and going. Thank you so much for sharing some time on the program today talking about your GTM, what you are doing to educate partners and customers and this tremendous potential that Fortinet is attacking. We appreciate your time. >> Thank you very much, I appreciate it too. >> We want to thank you for watching for Peter Burroughs, I'm Lisa Martin. You're watching theCUBE. (upbeat music)

hi everybody we are live at AWS reinvents in Las Vegas I'm Jeff Kelly with Wikibon org you're watching the cube silicon angles premiere live broadcast we go out to the technology events and as John foyer likes to say extract the signal from the noise so being here at the AWS show we were talk we're going to talk to a lot of AWS customers here a lot about what they're doing in in this case around analytics data warehousing and data integration so for this segment I'm joined by two customers Daniel heacock senior business systems analyst with a tix and Adam Cain's who's a data architect with federated sample welcome guys thanks for joining us on the cube Thanks your first time so we'll promise we'll make this as painless as possible so so you guys have a couple things in common we were talking beforehand some of the workflows are similar you work your you're using Amazon Web Services redshift platform for data warehousing you're using attunity for some of the data integration to bring that in from your for your operational transactional databases and using a bi tool on top to kind of tease out some of the insights from that data but why don't we get started Daniel we'll start with you tell us a little bit about etix kind of what you guys do and then we'll just kind of get into the use cases and talk to use AWS and the tuner need some of the other technologies you use it sure yeah so the company I work for is etix we are a primary market ticketing company in the entertainment industry we provide a box office solutions to venues and venue owners all types of events casinos fairs festivals pretty much you name and we sell some tickets in that industry we we provide a software solution that enables those menu owners to engage their customers and sell tickets so could kind of a competitor to something like ticketmaster the behemoth in the industry and you're definitely so Ticketmaster would be the behemoth in the industry and we are we consider ourselves a smaller sexier version that more friendly to the customer customer friendly more agile absolutely so Adam tell us a little bit about better a sample sure federated sample is a technology company in the market research industry and we aim to do is add an exchange layer between buyers and sellers so we facilitate the transaction between when a buyer or a company like coke would say hey we need to do a survey we will negotiate pricing and route our respondents to their surveys try to make that a more seamless process so they don't have to go out and find your very respond right everything online and right right absolutely got it so so let's talk a little bit about let's start with AWS so obviously we're here to reinvent a big show 9,000 people here so you guys you know talk about agile talk about cloud enabling kind of innovation and I'm gonna start with you what kind of brought you to AWS are you using red shift and I think you mentioned you're all in the cloud right just give us your impressions of the show in AWS and what that's meant your business right shows been great so far as to we were originally on-premise entirely at data center out in California and it just didn't meet our rapid growth we're a smaller company startup so we couldn't handle the growth so we need something more elastic more agile so we ended up moving our entire infrastructure into amazon web services so then we found that we had a need to actually perform analytics on that data and that's when we started the transition to you know redshift and so the idea being you're moving data from your transactional system which is also on AWS into redshift so using attunity for that they're clapping solution talk a little bit about that and and you know how that is differentiate from some of the other integration methods you could have chosen right so we started with a more conventional integration method a homegrown solution to move our data from our production sequel server into redshift and it worked but it was not optimal didn't have all the bells and whistles and it was prone to bad management being like not many people could configure it know how to use it so then we saw cloud being from attunity and they offered a native solution using secret survey replication that could tie into our native sequel server and then push that data directly into cloud being at a very fast rate so moving that data from from the sequel server it is essentially a real-time replication so that yes that's moving that data into redshifts of the year analysts can actually write when they're doing there the reporting or doing some real ad hoc kind of queries they can be confident they've got the most up-to-date data from your secret service right actual system right yeah nearly real-time and just to put in perspective the reports that we were running on our other system we're taking you know 10 15 minutes to run in redshift we're running those same reports in minutes 1 12 minutes right and if you're running those reports so quickly you know the people sometimes forget when you're talking about you know real time or interactive queries and reporting it's somewhat only as good as the data timeliness that you've got that you by Dave the timeless of the data you've got in that database because right trying to make some real-time decisions you've got a lag of depending on the workload and your use case even 15 minutes to an hour back might really impact you're ready to make those decisions so Adam talk a little bit about your use case is it is a similar cloud cloud architecture are you moving from upside Daniel moving from on-premise to so you're actually working with an on-premise data center it's an Oracle database and so we've basically we we ran into two limitations one regarding to our current reporting infrastructure and then to kind of our business intelligence capabilities and so as an analyst I've been kind of tasked with creating internal feedback loops within our organization as far as delivering certain types of KPIs and metrics to you know inform our our different teams or operations teams our marketing teams so that has been one of the kind of BI lms that we've been able to achieve because of the replication and the redshift and then the the other is actually making our reporting more I guess comprehensive we're able to run now that we're using redshift we're able to run reports that we were previously not be able to do to run on our on-premise transactional database so really we just are kind of embracing the power of redshift and it's enabling us and a lot of different types of ways yeah i mean we're hearing a lot about red shift at the show it's the amazon says the fastest-growing service AWS has had from a revenue perspective and it's six seven year history so clearly there's a lot of power in that platform it removes a lot of the concerns around having to manage that infrastructure obviously but the performance you know that's that's something I think when people are have their own data centers their own databases tuning those for the type of performance you're looking for is can be a challenge is that one of the drivers to kind of your move to redshift oh for sure the performance i I'm trying to think of a good example of a metric to compare but it's basically enabled us to develop a product or to develop products that would not have been possible otherwise there were certain i guess the ability to crunch data like you said in a specific time frame is very important for reporting purposes and if you're not able to meet a certain time frame then certain type of report is just not going to be useful so it's opening the door for new types of products within our organization well let's dig into that a little bit the different data types we're talking about so you've got a tea tix you're talking about customer transactions your custom are you talking about profiles of different types of customers tell us about some of the data sources that you're moving from your transactional system which i think is an Oracle database to to red shift and then you know what are some of those types of analytic workloads what kind of insights are you looking for sure so you know we're in the business of selling tickets and so one of our you know main concerns or I guess you should say we're in the business of helping our customers sell tickets and so we're always trying to figure out ways to improve their marketing efforts and so marketing segmentation is one of the huge ones appending data from large data services in order to get customer demographic information is something as you know easy to do in red shift and so we're able to use that information transaction information customer information I guess better engage our fans and likewise Adam could you maybe walk us through kind of a use case maybe your types of data you're looking at right that you're moving into red ship with attunity and then you know what kind of analytics are you doing on top of that what kind of insights are you gathering right so are our date is a little bit different than then ticketing but what we ultimately capture is is a respondent answers to questions so we try to find the value in a particular set of answers so we can determine the quality of the supply that's sent from suppliers so if they say that a person meets a certain demographic that we can actually verify that that person reads that demographic and then we can actually help them improve their supply that they push down to that respondent to it everybody makes more money because the completion rates go up so overall just business and analysis on that type of information so that we can help our customers and help ourselves so I wonder if we could talk a little bit about kind of the BI layer on top as well I think you're both using jaspersoft but you know beyond that you know one of the topics we've been covering on the cube another and on Wikibon is this whole analytics for all movement and we've been hearing about self service business intelligence for 20-plus years from some of the more incumbent vendors like business objects and cognos that others but really I mean if you look at a typical enterprise business intelligence usage or adoption rate kind of stalls out by eighteen percent twenty percent talk about how you've seen this kind of industry evolve a little bit maybe talk about jaspersoft specifically but what are some of the things that you think have to happen or some of the types of tools that are needed to really make business intelligence more consumable for analysts and more business use people who are not necessarily trained in statistics aren't data scientists Adam we start yes so one of the things that we're doing is with our jaspersoft we're trying to figure out you know certain we have a pis and we have traditional you know client server applications which ones our customers want to use the most because we're trying to push everybody towards an API oriented so we're trying to put that data into redshift with Jasper soft and kind of flip that data and look at it year-to-date or over a period of time to see where all of our money's coming from where others are rather than getting driven from and our business users are now empowered with jaspersoft to do that themselves they don't rely on us to pull data from they could just tie right into jaspersoft grab the data they need for whatever period of time they want and look at it in a nice pretty chart as a similar experience you're having any text definitely and I think one of the things I should emphasize about our use of Jasper's off and basically really any bi tool you choose to use in the Amazon platform is just the ability to launch it almost immediately and be able to play with data within 5-10 minutes of trying to launch it yeah it's pretty amazing what how quickly things can come from just a thought into action so well that's a good point because I mean you think about not just bitten telligence but the whole datawarehousing world it was you know the traditional method is you you know the business user a business unit goes to IT they say here are some of the requirements of the metrics we want on these reports IT then gun it goes away and builds it comes back six months later 12 months later here you go here's the report and next thing you know the business doesn't remember what they asked for this isn't necessarily going to serve our needs anymore and you've just essentially it's not a particularly useful model and Amazon really helps you kind of shorten that time frame significantly it sounds like between what you can do with redshift and some of their other database products and whatever bi to used to use is that kind of how you see this evolving oh definitely and the options I guess the the kind of plug and play workflow is is pretty pretty amazing and it's a it's given us the flexibility in our organization to be able to say well we can use this tool for now and there's a there's a chance we may decide there's something different in the future that we want to use and plugin in its place we're confident that that product will be there whenever the you know whenever the need is there right well that's the other thing you can you can start to use a tool and if it doesn't meet your need you can stop using it move to another tool so I think that puts you know vendors like jaspersoft than others puts them on their toes they've got to continually innovate and make their product useful otherwise you know they know that you know there were AWS customers can simply press the button stop using it press another button stop start using another tool so I think it's good in that sense but kind of you know when you talk about cloud and especially around data you get questions around privacy about data ownership who owns the data if it's in amazon's cloud is your data but you know it's on there in their data centers how do you feel about that Adam is there any concerns around either privacy or data ownership when it comes to using the cloud I mean you guys are all in in the cloud so right yeah so we've isolated a lot of our data into virtual private clouds so with that segment of the network we feel much more comfortable putting our data in a public space because we do feel like it's secure enough for our type of data so that was one of the major concerns up front but you know after talking with Amazon and going through the whole process of migrating to we kind of feel way more comfortable with that if you expand on that a little so you've got a private instance essentially in amazon's rep right so we have a private subnet so it's a segmented piece of their network that's just for us okay so we're not you can't access this publicly only within our VPN client or within our infrastructure itself so we're segmented we're away from that everybody else interesting so they offer that kind of type of service when there's more privacy concern as a security concern definitely and of course a lot depends on the type of data i mean how sensitive that data is if it you know but personally identifiable data obviously is going to be more sensitive than if it's just a general market data that anyone could potentially access daniel is we'll talk about your concerns around that or did you have concerns definitely a more of a governance people process question than a technology question I think well I definitely a technology question to a certain extent I mean as a as a transaction based business we were obviously very concerned with security and our CTO is very adamant about that and so that was one of the first first issues that we address whenever we decided to go this route and I'm obviously AWS has has taken all the precautions we have a very similar set up to what Adam is describing as far as our security we are very much confident that it is a very robust solution so looking forward how do you see your use of both the cloud and kind of analytics evolving you know one of the things we've been covering a lot is the as use case to get more complex your kind of you've got to orchestrate more data flows you've got to move data for more places you mentioned you're using attunity to do some of that replication from your transactional database and some red shift you know what are some of the other potential data integration challenges you see fate you see yourselves facing as you kind of potentially get more complex deployments we've got more data maybe you start using more services on Amazon how do you look to tackle some of those eight integration challenges let me start that's a good question one of the things we're trying to do inside of you know our organization is I guess bring data from all the different sources that we have together we have you know we use Salesforce for our sales team we collect information from MailChimp from our digital marketing agency that that we'd like to tile that information together and so that's something we're working on attunity has been a great help there and they're you know they're their product development as far as their capabilities of bringing in information from other sources is growing so that's a you know we're confident that the demand is there and that the product will develop as we as we move forward well I mean it's interesting that we've got you know you two gentlemen up here one with a kind of a on premise to cloud deployment and one all in the cloud so I'm clearly tuning you can kind of gap both those right on premise and cloud roll but also work in the cloud environment Adam when we if you could talk a little bit about how you see this kind of evolving as you get more complex maybe bring in more systems are you looking to bring in more data sources maybe even third-party data sources outside data sources how are you how do you look at this evolve right President Lee we do have a Mongo database so we have other sources that we're doing now there's talks of even trying to stick that in dynamo DB which is a reg amazon offering and that ties directly into redshift so we could load that data directly into that using that key pair or however we want to use that type of data data Mart but one of the things that we're trying to work out right now is just distribution and you know being agile you know elasticity which I work those issues with our growing database so so our database grows rather large each month so working on scalability is our primary focus but other data sources so we look into other database technologies that we can leverage in addition to sequel server to help distribute that load you so we've got time just for one more question I wonder I always like to ask when we get customers and users on if you can give some advice to other practitioners for watching so I mean if you can give one piece of advice to somebody who might be in your position they're looking at maybe they've got an on-premise data warehouse or maybe they're just trying to figure out a way to to get make better use of their data I mean what would the we the one thing would it be a technology piece of advice maybe you know looked at something like red shift or and solutions like attunity but maybe it would be more of a you know cultural question around the use of data and I'm I instead of making data-driven decisions but with that kind of one piece of ice big I could put you on the spot okay I would say don't try to do it yourself when the experts have done it for I couldn't put it any more simpler than that very succinct but very powerful but for me my biggest takeaway would be just redshift I was kind of apprehensive to use it at first I was so used to other technologies but we can do so much with redshift now add you know half the cost so your good works pretty compelling all right fantastic well Adam pains Daniel heacock thank you so much for joining us on the cube appreciate it we'll be right back with our next guests we're live here at AWS reinvent in Las Vegas you're watching the cube the cute