>> Welcome back to New York City everybody. This is The Cube's coverage of MongoDB World 2022, Dev Ittycheria, here is the president and CEO of MongoDB. Thanks for spending some time with us. >> It's Great to be here Dave, thanks for having me. >> You're very welcome. So your keynotes this morning, I was hearkening back to Steve Ballmer, running around the stage screaming, developers, developers, developers. You weren't jumping around like a madman, but the message was the same. And you've not deviated from that message. I remember when it was 10th Gen, so you've been consistent. >> Yes. >> Why is Mongo DB so alluring to developers? >> Yeah, because I would say the reason we're so popular Dave is that our whole business was founded on the ethos, so making developers incredibly productive. Just getting the infrastructure out of the way so that the developers is really focused on what's important and that's building great applications that transform their business. And the way you do that is you look at where they spend most of the time. and they spend most of the time working with data. How do you present data, the right data, the right time, at the right place, and the right way. And when you remove the friction of working with data, you unleash so much more productivity, which people just say, oh my goodness, I can move so much faster. Product leaders can get products out the door faster than the competitors. Senior level executives can seize new opportunities or respond to new threats. And that was so profound during COVID when everyone had to think about pivoting their business. >> When you came to MongoDB, why did you choose this company? What was it that excited you about it? >> I get that question a lot. I would say conventional wisdom would suggest that MongoDB was not a great choice. There weren't that many companies who were very successful in open source, Red Hat was the only one. No one had really built a deep technology company in New York city. They say, you got to do it in the valley. And database companies need a lot of capital. Now turns out that raising capital of this past decade was a lot easier, but it still takes a lot of time, and a lot of capitals, you have to have a lot of patience. When I did my diligence, I was actually a VC before I joined MongoDB. The whole next generation database segment was really taking off. And actually I looked at some competing investments to MongoDB, and when I did my diligence, it was clear even then. And this is circa 2012, that MongoDB is way ahead in terms of customer attraction, commercials, and even kind of developer mind share. And so I ended up passing those investments. and then lo and behold, I got a call from a very senior executive recruiter who said, Dev, you got to take a meeting with MongoDB, there's something really interesting going on. And they had raised a lot of capital and they had just not been able to kind of really execute in terms of the opportunity. And they realized they needed to make a change. And so one thing led to another. One of the things that really actually convinced me, is when I did my diligence, I realized the customers they had loved MongoDB. They just really weren't executing on all cylinders. And I always believe you never bet against a company whose customers love the product. And said, that's something here. The second thing I would say is open source. Yes, is true that open source was not very successful, but that was open source 1.0. Open source 2.0, the technology is much better than the commercial options. And so that convinced me. And then New York, I lived in New York a big part of my life. I think New York's a fabulous place to build a business. There's so much talent, your customers are right... You walk out the door, there's customers all over the place. And getting to Europe is very easy, Almost like flying to the west coast. So it's a very central place to build a business. >> And it's easier to fix execution, wouldn't you say? And maybe even go to market than it is to fix a product that customers really don't love. >> Correct, it's much easier to fix leadership issues, culture issues, execution issues. Nailing product market fit is very, very hard. And there were signs, there's still some issues, there's still some rough spots, but there a lot of signs that this company was very, very close, and that's why I took the bet. >> And this is before there was that huge influx of capital into the separating compute from storage and the whole cloud thing, which is interesting. Because you take a company like Cloudera, they got caught up in that and got kind of washed over. And I guess you could argue Hortonworks did too, and they could have dead ended both. And then that just didn't work. But it's interesting to see Mongo, the market kind of came to you. And that really does speak to the product. It wasn't a barrier for you. You guys have obviously a lot of work to get into the cloud with Atlas, but it seemed like a natural fit with the product. It wasn't like a complete fork. >> Well, I think the challenge that we had was we had a lot of adoption, but we had tough time commercializing the business. And at some point I had to tell the all employees, it's great that we have all these people who are using MongoDB, but if you don't start generating revenue, our investors are going to get tired of subsidizing this company. So I had to try and change the culture. And as you imagine, the engineers didn't really like the salespeople, the salespeople thought the engineers didn't really want to make any money. And what I said, like, let's all galvanize around customers and let's make them really excited and try and create a lot of value. And so we just put a lot more discipline in terms of how we prosecuted deals. We put a lot more discipline in terms of what are the problems we're trying to solve. And one thing led to another, we started building the business brick by brick. And one of the things that became clear for me was that the old open source model of trying to find that happy medium between what you give away and what you charge for, is always a tough game. Like because finding that where the paywall is, if you give away too much new features, you don't make any money. If you don't give away enough, you don't have any adoption. So you're caught in this catch-22. The best way to monetize open source, is open source as a service. And we saw Amazon do that frankly. We learned a lot from how Amazon did that. And one of the advantages that MongoDB had that I didn't fully appreciate when I joined the company, but I was very grateful. It is that they had a much more restrictive license. Which we ended up actually changing and made it even more restrictive, which allowed us to perfect ourselves from being cannibalized by the cloud providers, so that we could build our own business using our own IP that we had invested in and create a cloud service. >> That was a huge milestone. And of course you have great relationships with all the cloud providers, but it got contentious there for a while, but, you give the cloud providers an inch, they're going to take a mile. That's just the way, they're aggressive like that. But thank you for going through the history with me a little bit, because when you go back to the IPO, IPO was 2017, right? >> Correct. >> I always tell young investors, my kids especially, don't buy a stock at IPO, you're going to have a better chance, but the window from Mongo was very narrow. So, you didn't really get a much better chance a little bit. And then it's been a rocket ship since then. Sure, there's been some volatility, but you look at some of the big IPOs, like Facebook, or Snap, or even Snowflake, there was better opportunities. But you guys have executed really, really well. That's part of your ethos in your management team. And it came across on the earnings call recently. >> Yep. >> It was very optimistic, yet at the same time you set cautious tones and you got, I think high marks. >> Yes. >> For some of that caution but that execution. So talk about where you feel the business is today given the economic uncertainty? >> Well, what I'd say is we feel really good about the long term. We feel like the secular trends are really in our favor. Software's fundamentally transforming every industry. And people want to use modern software to either automate inefficient processes, enable new capabilities, drive better customer experiences. And the level of performance and scale you need for today's modern applications is profoundly different than applications yesterday. So we think we're well positioned for that. What we said on the earnings call was that we started seeing a moderation of growth, slight moderation of growth in our low end of the business in Europe. It was in our self-serve business and in the SMB space for the NQ1, towards the end of Q1. And we saw a little bit of that show up in the self-serve business in may in Q2. And that's why while we raised guidance, we basically quantified the impact, which is roughly about 30 to 35 million for the year, based on what we saw. And in that assumption, we assumed like... We just can't assume it's going to only be at the low in the market, probably some effect at the enterprise market. Maybe not as much, but there'll be some effect. So we need to factor that in. And we wanted to help kind of investors have some sort of framework to think about what the impact is. We don't want to be one of those companies that said absolutely nothing. And we don't want to be one of those companies that just waves the hand, but then it wasn't really that useful for investors. >> Yeah, I thought it was substantive. You talked about those market trends, you cited three things. The developers recognize that there are limits to legacy RDBMS. You talked about the, what I call point solutions creep. And then the document model is the best for developers. >> Great. >> And when the conversation turned to consumption, everybody's concerned about consumption obviously. You said... My take, somewhat insulated from that because you're running mission critical apps. It's not discretionary. My question to you is, should we rethink the definition of mission-critical? You think of Oracle mission critical running a bank. Mission -critical today in this digital world seems to be different, is that fair? >> Gosh, when's the last time you ever saw a website down? Like if you're running like any kind of digital channel, or engaging with the customers, or your partners, or your suppliers, you need to be up all the time. And so you need a very resilient, highly available data platform. It needs to be highly performance as you add more users, you need to be scale. And we saw a lot of that when COVID hit. Like companies had to completely repovit. And we talked about some examples where like a health and beauty retailer who was all kind of basically retail, had to suddenly pivot to e-commerce strategy. We've had streaming and gaming companies suddenly saw this massive influx of data that they scaled their operations very, very quickly. So I would say anytime you're engaging with customers, customers they're so used to the kind of the consumer facing applications. I almost joke like slow is the old down. If you're not performant, it doesn't matter. They're going to abandon you and go somewhere else. So if you're an e-commerce site and you're not performing well and not serving up the right skews, depending on what they're looking for, they're going to go somewhere else. >> So it's a click away. You talk about a hundred billion TAM, maybe that's even undercounted as you start to bring new capabilities in there. But there's no lack of market for you. >> Correct. >> How do you think about the market opportunity? >> Well, we believe... Again, software is transforming so many industries. IDC says that 715 million applications will be built over the next two to three years by 2025. To put that number of perspective, that's more apps that will be built the next three to four years than were built in the last 40. The rate and pace of innovation is as exploding. And people are building custom applications. Yes, Workday, Salesforce, other companies, commercial companies are great companies, but my competitors can use Workday or Salesforce, some of those commercial companies. That doesn't gimme a competitive advantage, what gives me a competitive advantage is building custom software that better engage my customers, that transforms my business in adding new capabilities or drives more efficiency. And the applications are only getting smarter. And so you're seeing that innovation explode and that plays to our strength. People need platforms like MongoDB to build the next generation of applications. >> So Atlas is now roughly 60% of your business, think is growing at 85%. So it's at least the midterm future. But my question to you is, is it the future? 'Cause when we start to think about the edge, it's not necessarily the cloud. You're not going to be able to go that round trip and the latency. And we had Verizon on earlier, talking about what they're doing with 5G, and the Mobile Edge. Is Mongo positioning for that edge? And is our definition of cloud changing? Where it's not just OnPrem and across clouds, but it's also out to the edge, this continuous experience. >> So I'll make two points. One, definitely we believe the applications of the future will be mobile first or purely mobile. Because one with the advent of 5G, the distinction between mobile and web is going to blur, with a hundred times faster networking speeds. But the second point I make is that how that shows up on our revenue on our income table will look like Atlas. Because we don't charge nothing for the end point, it's basically driving consumption of the back end. And so we've introduced a bunch of very, very sophisticated capabilities to synchronized data from the edge to the backend and vice versa with things like flexible sync. So we see so many customers now using that capability, whether you're field service technicians, whether you're a mobile first company, et cetera. So that will drive Atlas revenue. So on an income statement, it'll look like Atlas, but we're obviously addressing those broader set of mobile needs. >> You talk a lot about product market fit former VC, of course, Mark Andreen says, product market fit you kind of know when you see it, your hair's on fire, you can't buy a service. How do you know when you have product market fit? >> Well, one, we have the luxury of lots of customers. So they tell us pretty clearly when they're happy, and we can see that by usage behavior. Now the other benefit of a cloud service, is we can see the level of activity. We can see the level of engagement. We can see how much data they're consuming. We can see all the actions they're taking. So you get the fidelity of feedback you get from Atlas versus someone doing something behind their own firewall. And you kind of call 'em and check in on them is very, very different. So that level of insight gives us visibility in terms of what products and features have been used, gives us a sense how things going well, or is there something awry. Maybe they have misconfigured something or they don't know how to use some capabilities. So the level of engagement that we can have with a customer using a service is so much different. And so we've really invested in our customer success organization. So the byproduct of that is that our retention rates are also very, very strong. Because you have such better information about what's happening in terms of your customers. >> See retention in real time. You've been somewhat... Is just so hard to say this 'cause you're growing at 50% a year. But you're somewhat conservative about the pace of hiring for go to market. And I'm curious as to how you think about scaling, especially when you introduce new products. Atlas is several years ago. But as you extend your capabilities and add new products, how do you decide when to scale? >> So it's a constant process. We've been quite aggressive in scaling organization for a couple reasons. One, we have very low market share, so the market's vastly under penetrated. We still don't have reps in every NFL sitting in the United States, which just kind of crazy. There's other parts of the world that we are just still vastly under penetrated in. But we also look at how those organizations are doing. So if we see a team really killing it, we're going to deploy more resources. Because one, it tells us there's more opportunity there, and there's a strong team there. If we see a team that maybe is struggling a little bit, we'll try and uncover. Rather than just applying more resources in, we'll try and uncover what are the issues and make sure we stabilize the organization and then devote resources. It's all in the measure of like being very disciplined about where we deploy our resources, to get those kind of returns. And on the product side, we obviously go through a very iterative process and kind of do rank order all the projects and what we think the expected returns are. Obviously, we look at the customer feedback, we look at what our strategic priorities are. And that informs what projects we fund and what projects kind of are below the line. And we do that over and over again every quarter. So every quarter we revisit the business, we have a very QBR centric culture. So we're constantly checking in and seeing how the business is operating. And then we make those investment decisions. In general, we've been investing very aggressively in terms of expanding our reach around the world. >> It seems like, well, with Mongo, your product portfolios... From an outside observer standpoint, it seems like you've always had pretty good product market fit. But I was curious, in your VC days, would you ever encourage companies to scale go to market prior to having confidence in product market fit? Or did you always see those as sequential activities? >> Well, I think the challenge is this part it's analysis part is judgment. So you don't necessarily have to have perfect product market fit to start investing. But you also don't want to plow a bunch of resources and realize the product doesn't work and then how you're burning through a lot of cash. So there's a little bit of art to the process. When I joined MongoDB, I could tell that we had a strong engineering team. They knew how to build high quality products, but we just struggled with commercialization. The culture wasn't great across the company. And we had some leadership challenges. So that's when I joined, I kind of focused on those things and tried to bring the organization together. And slowly we started chipping away and making people feel like they were winners. And once you start winning, that becomes contagious. And then the nice thing is when you start winning, you get a lot more customer feedback. That feedback helps you refine your products even more, which then adds... It's like the flywheel effect that starts taking off. >> So it seems the culture's working now. Do you have a favorite product from the announcements today? >> Well, I really like our foray to analytics. And essentially what we're seeing is really two big trends. One you're seeing applications get smarter. What applications are doing is really automating a lot of processes and rather than someone having to press a button. Based on analytics, you can automate a lot of decision making. So that's one theme that we're seeing as applications get smarter. The second theme is that people want more and more insight in terms of what's happening. And the source of that is insights is your operational database. Because that's where you're having transactions, that's where you know what products are selling, that's where you know what customers are buying. So people want more and more real time data versus waiting to take that data, put it somewhere else and then run reports and then get some update at the end of the night or maybe at the week. So that's driving a lot of really interesting use cases. And especially when you marry in things like time series use cases where you're collecting a lot of data people want to see trend analysis what's happening. Which I think it's a very exciting area. We introduced a very cool feature called Queryable Encryption, which basically... The problem with encrypting data, is you can't really query it because my definition's encrypted. >> Yeah, you're right. >> But obviously data security is very important. What we announced, is we're using very sophisticated cryptography. People can query the data, but they don't have really access to the data. So it really protects you from like data breaches or malicious users accessing your data, but you still can kind of make that data usable. So that was a very interesting announcer that we made today. >> Sounds like magic without the performance hit. >> Yes. >> You can do that. Dev, thanks so much for coming in The Cube. Congratulations on all activity, bumper sticker on day one. >> Oh, it's super exciting. The energy was palpable, 3,300 people in the room, lots of customers, lots of users. We had lots of investors here as well for our investor day, have a dinner tonight with a bunch of senior execs, so it's been a busy day. >> Future is bright for MongoBD. Dev, thanks for so much for coming on The Cube. And thanks for watching, this is Dave Vellante and we'll see you next time. (upbeat music)

>>Welcome back to NYC the Cube's coverage of Mongo DB 2022, a few thousand people here at least bigger than many people, perhaps expected, and a lot of buzz going on and we're gonna talk devs. I'm really excited to welcome back. Robbie Bellson who's the developer relations lead at Verizon and Ian Massingham. Who's the vice president of developer relations at Mongo DB Jens. Good to see you. Great >>To be here. >>Thanks having you. So Robbie, we just met a few weeks ago at the, the red hat summit in Boston and was blown away by what Verizon is doing in, in developer land. And of course, Ian, you know, Mongo it's rayon Detra is, is developers start there? Why is Mongo so developer friendly from your perspective? >>Well, it's been the ethos of MongoDB since day one. You know, back when we launched the first version of MongoDB back in 2009, we've always been about making developers lives easier. And then in 2016, we announced and released MongoDB Atlas, which is our cloud managed service for MongoDB, you know, starting with a small number of regions built on top of AWS and about 2,500 adoption events per week for MongoDB Atlas. After the first year today, MongoDB Atlas provides a managed service for MongoDB developers around the world. We're present in almost a hundred cloud regions across S DCP and Azure. And that adoption number is now running at about 25,000 developers a week. So, you know, the proof are in proof is really in the metrics. MongoDB is an incredibly popular platform for developers that wanna build data-centric applications. You just can't argue with the metrics really, >>You know, Ravi, sometimes there's an analyst who come up with these theories and one of the theories I've been spouting for a long time is that developers are gonna win the edge. And now to, to see you at Verizon building out this developer community was really exciting to me. So explain how you got this started with this journey. >>Absolutely. As you think about Verizon 5g edge or mobile edge computing portfolio, we knew from the start that developers would play a central role and not only consuming the service, but shaping the roadmap for what it means to build a 5g future. And so we started this journey back in late 20, 19 and fast forward to about a year ago with Mongo, we realized, well, wait a minute, you look at the core service offerings available at the edge. We didn't know really what to do with data. We wanted to figure it out. We wanted the vote of confidence from developers. So there I was in an apartment in Colorado racing, your open source Mongo against that in the region edge versus region, what would you see? And we saw tremendous performance improvements. It was so much faster. It's more than 40% faster for thousands and thousands of rights. And we said, well, wait a minute. There's something here. So what often starts is an organic developer, led intuition or hypothesis can really expand to a much broader go to market motion that really brings in the enterprise. And that's been our strategy from day one. Well, >>It's interesting. You talk about the performance. I, I just got off of a session talking about benchmarks in the financial services industry, you know, amazing numbers. And that's one of the hallmarks of, of Mongo is it can play in a lot of different places. So you guys both have developer relations in your title. Is that how you met some formal developer relations? >>We were a >>Program. >>Yeah, I would say that Verizon is one of the few customers that we also collaborate with on a developer relations effort. You know, it's in our mutual best interest to try to drive MongoDB consumption amongst developers using Verizon's 5g edge network and their platform. So of course we work together to help, to increase awareness of MongoDB amongst mobile developers that want to use that kind of technology. >>But so what's your story on this? >>I mean, as I, as I mentioned, everything starts with an organic developer discovery. It all started. I just cold messaged a developer advocate on Twitter and here we are at MongoDB world. It's amazing how things turn out. But one of the things that's really resonated with me as I was speaking with one of, one of your leads within your organization, they were mentioning that as Mongo DVIA developed over the years, the mantra really became, we wanna make software development easy. Yep. And that really stuck with me because from a network perspective, we wanna make networking easy. Developers are not gonna care about the internals of 5g network. In fact, they want us to abstract away those complexities so that they can focus on building their apps. So what better co-innovation opportunity than taking MongoDB, making software easy, and we make the network easy. >>So how do you think about the edge? How does you know variety? I mean, to me, you know, there's a lot of edge use cases, you know, think about the home Depot or lows. Okay, great. I can put like a little mini data center in there. That's cool. That's that's edge. Like, but when I think of Verizon, I mean, you got cell towers, you've got the far edge. How do you think about edge Robbie? >>Well, the edge is a, I believe a very ambiguous term by design. The edge is the device, the mobile device, an IOT device, right? It could be the radio towers that you mentioned. It could be in the Metro edge. The CDN, no one edge is better than the other. They're all just serving different use cases. So when we talk about the edge, we're focused on the mobile edge, which we believe is most conducive to B2B applications, a fleet of IOT devices that you can control a manufacturing plant, a fleet of ground and aerial robotics. And in doing so you can create a powerful compute mesh where you could have a private network and private mobile edge computing by way of say an AWS outpost and then public mobile edge computing by way of AWS wavelength. And why keep them separate. You could have a single compute mesh even with MongoDB. And this is something that we've been exploring. You can extend Atlas, take a cluster, leave it in the region and then use realm the mobile portfolio and spread it all across the edge. So you're creating that unified compute and data mesh together. >>So you're describing what we've been expecting is a new architecture emerging, and that's gonna probably bring new economics of new use cases, right? Where are we today in that first of all, is that a reasonable premise that this is a sort of a new architecture that's being built out and where are we in that build out? How, how do you think about the, the future of >>That? Absolutely. It's definitely early days. I think we're still trying to figure it out, but the architecture is definitely changing the idea to rip out a mobile device that was initially built and envisioned for the device and only for the device and say, well, wait a minute. Why can't it live at the edge? And ultimately become multi-tenant if that's the data volume that may be produced to each of those edge zones with hypothesis that was validated by developers that we continue to build out, but we recognize that we can't, we can't get that static. We gotta keep evolving. So one of our newest ideas as we think about, well, wait a minute, how can Mongo play in the 5g future? We started to get really clever with our 5g network APIs. And I, I think we talked about this briefly last time, 5g, programmability and network APIs have been talked about for a while, but developers haven't had a chance to really use them and our edge discovery service answering the question in this case of which database is the closest database, doesn't have to be invoked by the device anymore. You can take a thin client model and invoke it from the cloud using Atlas functions. So we're constantly permuting across the entire portfolio edge or otherwise for what it means to build at the edge. We've seen such tremendous results. >>So how does Mongo think about the edge and, and, and playing, you know, we've been wondering, okay, which database is actually gonna be positioned best for the edge? >>Well, I think if you've got an ultra low latency access network using data technology, that adds latency is probably not a great idea. So MongoDB since the very formative years of the company and product has been built with performance and scalability in mind, including things like in memory storage for the storage engine that we run as well. So really trying to match the performance characteristics of the data infrastructure with the evolution in the mobile network, I think is really fundamentally important. And that first principles build of MongoDB with performance and scalability in mind is actually really important here. >>So was that a lighter weight instance of, of Mongo or not >>Necessarily? No, not necessarily. No, no, not necessarily. We do have edge cashing with realm, the mobile databases Robbie's already mentioned, but the core database is designed from day one with those performance and scalability characteristics in mind, >>I've been playing around with this. This is kind of a, I get a lot of heat for this term, but super cloud. So super cloud, you might have data on Preem. You might have data in various clouds. You're gonna have data out at the edge. And, and you've got an abstraction that allows a developer to, to, to tap services without necessarily if, if he or she wants to go deep into the S great, but then there's a higher level of services that they can actually build for their customers. So is that a technical reality from a developer standpoint, in your view, >>We support that with the Mongo DB multi-cloud deployment model. So you can place Mongo DB, Atlas nodes in any one of the three hyperscalers that we mentioned, AWS, GCP or Azure, and you can distribute your data across nodes within a cluster that is spread across different cloud providers. So that kinds of an kind of answers the question about how you do data placement inside the MongoDB clustered environment that you run across the different providers. And then for the abstraction layer. When you say that I hear, you know, drivers ODMs the other intermediary software components that we provide to make developers more productive in manipulating data in MongoDB. This is one of the most interesting things about the technology. We're not forcing developers to learn a different dialect or language in order to interact with MongoDB. We meet them where they are by providing idiomatic interfaces to MongoDB in JavaScript in C sharp, in Python, in rust, in that in fact in 12 different pro programming languages that we support as a first party plus additional community contributed programming languages that the community have created drivers for ODMs for. So there's really that model that you've described in hypothesis exist in reality, using >>Those different Compli. It's not just a series of siloed instances in, >>In different it's the, it's the fabric essentially. Yeah. >>What, what does the Verizon developer look like? Where does that individual come from? We talked about this a little bit a few weeks ago, but I wonder if you could describe it. >>Absolutely. My view is that the Verizon or just mobile edge ecosystem in general for developers are present at this very conference. They're everywhere. They're building apps. And as Ian mentioned, those idiomatic interfaces, we need to take our network APIs, take the infrastructure that's being exposed and make sure that it's leveraging languages, frameworks, automation, tools, the likes of Terraform and beyond. We wanna meet developers where they are and build tools that are easy for them to use. And so you had talked about the super cloud. I often call it the cloud continuum. So we, we took it P abstraction by abstraction. We started with, will it work in one edge? Will it work in multiple edges, public and private? Will it work in all of the edges for a given region, public or private, will it work in multiple regions? Could it work in multi clouds? We've taken it piece by piece by piece and in doing so abstracting way, the complexity of the network, meaning developers, where they are providing those idiomatic interfaces to interact with our API. So think the edge discovery, but not in a silo within Atlas functions. So the way that we're able to converge portfolios, using tools that dev developers already use know and love just makes it that much easier. Do, >>Do you feel like I like the cloud continuum cause that's really what it is. The super cloud does the security model, how does the security model evolve with that? >>At least in the context of the mobile edge, the attack surface is a lot smaller because it's only for mobile traffic not to say that there couldn't be various configuration and human error that could be entertained by a given application experience, but it is a much more secure and also reliable environment from a failure domain perspective, there's more edge zones. So it's less conducive to a regionwide failure because there's so many more availability zones. And that goes hand in hand with security. Mm. >>Thoughts on security from your perspective, I mean, you added, you've made some announcements this week, the, the, the encryption component that you guys announced. >>Yeah. We, we issued a press release this morning about a capability called queryable encryption, which actually as we record this Mark Porter, our CTO is talking about in his keynote, and this is really the next generation of security for data stored within databases. So the trade off within field level encryption within databases has always been very hard, very, very rigid. Either you have keys stored within your database, which means that your memory, so your data is decrypted while it's resident in memory on your database engine. This allow, of course, allows you to perform query operations on that data. Or you have keys that are managed and stored in the client, which means the data is permanently OBS from the engine. And therefore you can't offload query capabilities to your data platform. You've gotta do everything in the client. So if you want 10 records, but you've got a million encrypted records, you have to pull a million encrypted records to the client, decrypt them all and see performance hit in there. Big performance hit what we've got with queryable encryption, which we announced today is the ability to keep data encrypted in memory in the engine, in the database, in the data platform, issue queries from the client, but use a technology called structural encryption to allow the database engine, to make decisions, operate queries, and find data without ever being able to see it without it ever being decrypted in the memory of the engine. So it's groundbreaking technology based on research in the field of structured encryption with a first commercial database provided to bring this to market. >>So how does the mobile edge developer think about that? I mean, you hear a lot about shifting left and not bolting on security. I mean, is this, is this an example of that? >>It certainly could be, but I think the mobile edge developer still stuck with how does this stuff even work? And I think we need to, we need to be mindful of that as we build out learning journeys. So one of my favorite moments with Mongo was an immersion day. We had hosted earlier last year where we, our, from an enterprise perspective, we're focused on BW BS, but there's nothing stopping us. You're building a B2C app based on the theme of the winner Olympics. At the time, you could take a picture of Sean White or of Nathan Chen and see that it was in fact that athlete and then overlaid on that web app was the number of medals they accrued with the little trumpeteer congratulating you for selecting that athlete. So I think it's important to build trust and drive education with developers with a more simple experience and then rapidly evolve overlaying the features that Ian just mentioned over time. >>I think one of the keys with cryptography is back to the familiar messaging for the cloud offloading heavy lifting. You actually need to make it difficult to impossible for developers to get this wrong, and you wanna make it as easy as possible for developers to deal with cryptography. And that of course is what we're trying to do with our driver technology combined with structure encryption, with query encryption. >>But Robbie, your point is lots of opportunity for education. I mean, I have to say the developers that I work with, it's, I'm, I'm in awe of how they solve problems and I, and the way they solve problems, if they don't know the answer, they figure out how to go get it. So how, how are your two communities and other communities, you know, how are they coming together to, to solve such problems and share whether it's best practices or how do I do this? >>Well, I'm not gonna lie in person. Events are a bunch of fun. And one of the easiest domain knowledge exchange opportunities, when you're all in person, you can ideate, you can whiteboard, you can brainstorm. And often those conversations are what leads to that infrastructure module that an immersion day features. And it's just amazing what in person events can do, but community groups of interest, whether it's a Twitch stream, whether it's a particular code sample, we rely heavily on digital means today to upscale the developer community, but also build on by, by means of a simple port request, introduce new features that maybe you weren't even thinking of before. >>Yeah. You know, that's a really important point because when you meet people face to face, you build a connection. And so if you ask a question, you're more likely perhaps to get an answer, or if one doesn't exist in a, in a search, you know, you, oh, Hey, we met at the, at the conference and let's collaborate on this guys. Congratulations on, on this brave new world. You're in a really interesting spot. You know, developers, developers, developers, as Steve bomber says screamed. And I was glad to see Dave was not screaming and jumping up and down on the stage like that, but, but the message still resonates. So thank you, definitely appreciate. All right, keep it right there. This is Dave ante for the cubes coverage of Mago DB world 2022 from New York city. We'll be right back.

>>Mhm. Mhm. Yeah. Hello, everybody. Welcome to the Cubes. Coverage of Mongo db World 2022. This is the first Mongo live mongo DB World. Since 2019, the Cube has covered a number of of mongo shows actually going back to when the company was called Engine. Some of you may recall Margo since then has done an i p o p o in 2017, it's It's been a rocket ship company. It's up. It'll probably do 1.2 billion in revenue this year. It's got a billion dollars in cash on the balance sheet. Uh, despite the tech clash, it's still got a 19 or $20 million valuation growing above 50% a year. Uh, company just had a really strong quarter, and and there seems to be hitting on all cylinders. My name is Dave Volonte. And here to kick it off with me as Sanjeev Mohan, who was the principal at Sanremo. So great to see you. You become a wonderful cube contributor, Former Gartner analyst. Really sharp? No, the database space in the data space generally really well, so thanks for coming back on >>you. You know, it's just amazing how exciting. The entire data space is like they used to say. Companies are All companies are software companies. All companies are data >>companies, >>so data has become the the foundation. >>They say software is eating the world. Data is eating software and a little little quips here. But this is a good size show. Four or 5000 people? I don't really know exactly. You know the numbers, but it's exciting. And of course, a lot of financial services were here at the Javits Centre. Um, let's let's lay down the basics for people of Mongo, DB is a is a document database, but they've been advancing. That's a document database as an alternative to R D. B M s. Explain that, but explain also how Mongo has broadened its capabilities and serving a lot more use cases. >>So that's my forte is like databases technology. But before even I talk about that, I have to say I am blown away by this mongo db world because mongo db uh, in beckons to all of us during the pandemic has really come of age, and it's a billion dollar company. Now we are in this brand new Javits Centre That's been built during the pandemic. And and now the company is holding this event the high 1000 people last year. So I think this company has really grown. And why has it drawn is because its offerings have grown to more developers than just a document database document databases. Revolution revolutionised the whole DBM s space where no sequel came up. Because for a change, you don't need a structured schema. You could start bringing data in this document model scheme, uh, like varying schema. But since then, they've added, uh, things like such. So they have you seen such? They added a geospatial. They had a time series last year, and this year they keep adding more and more so like, for example, they are going to add some column store indexes. So from being a purely transactional, they are now starting to address analytical. And they're starting to address more use cases, like, you know, uh, like what? What was announced this morning at keynote was faceted search. So they're expanding the going deeper and deeper into these other data >>structures. Taking Lucy made a search of first class citizens, but I want to ask you some basic questions about document database. So it's no fixed schemes. You put anything in there? Actually, so more data friendly. They're trying to simplify the use of data. Okay, that's that's pretty clear. >>What are the >>trade offs of a document database? >>So it's not like, you know, one technology has solved every problem. Every technology comes with its own tradeoffs. So in a document, you basically get rid of joining tables with primary foreign keys because you can have a flexible schemer and so and wouldn't sing single document. So it's very easy to write and and search. But when you have a lot of repeated elements and you start getting more and more complex, your document size can start expanding quite a bit because you're trying to club everything into a single space. So So that is where the complexity goes >>up. So what does that mean for for practitioner, it means they have to think about what? How they how they are ultimately gonna structure, how they're going to query so they can get the best performances that right. So they're gonna put some time in up front in order to make it pay back at the tail end, but clearly it's it's working. But is that the correct way of thinking about >>100% in, uh, the sequel world? You didn't care about the sequel. Analytical queries You just cared about how your data model was structured and then sequel would would basically such any model. But in the new sequel world, you have to know your patterns before you. You invest into the database so it's changed that equation where you come in knowing what you are signing up. >>So a couple of questions, if I can kind of Colombo questions so to Margo talks about how it's really supporting mission critical applications and at the same time, my understanding is the architecture of mongo specifically, or a document database in general. But specifically, you've got a a primary, uh, database, and you and that is the sort of the master, if you will, right and then you can create secondaries. But so help me square the circle between mission critical and really maybe a more of a focus on, say, consistency versus availability. Do customers have to sort of think about and design in that availability? How do they do that? How a Mongol customers handling that. >>So I have to say, uh, my experience of mongo db was was that the whole company, the whole ethos was developed a friendly. So, to be honest, I don't think Mongo DB was as much focused on high availability, disaster, recovery, even security. To some extent, they were more focused on developer productivity. >>And you've experienced >>simplicity. Make it simple, make the developers productive as fast as you can. What has really, uh, was an inflexion point for Mongo DB was the launch of Atlas because the atlas they were able to introduce all of these management features and hide it abstracted from the end users. So now they've got, you know, like 2014 is when Atlas came out and it was in four regions. But today they're in 100 regions, so they keep expanding, then every hyper scale cloud provider, and they've abstracted that whole managed. >>So Atlas, of course, is the managed database as a service in the cloud. And so it's those clouds, cloud infrastructure and cloud tooling that has allowed them to go after those high available application. My other question is when you talk about adding search, geospatial time series There are a lot of specialised databases that take time series persons. You have time series specialists that go deep into time series can accompany like Mongo with an all in one strategy. Uh, how close can they get to that functionality? Do they have to be? You know, it's kind of a classic Microsoft, you know, maybe not perfect, but good enough. I mean, can they compete with those other areas? Uh, with those other specialists? And what happens to those specialists if the answer is yes. What's your take on that? If that question >>makes sense So David, this is not a mongo db only issue This is this is an issue with, you know, anytime serious database, any graph database Should I put a graph database or should I put a multifunctional database multidimensional database? And and I really think there is no right or wrong answer. It just really comes down to your use case. If you have an extremely let's, uh, complex graph, you know, then maybe you should go with best of breed purpose built database. But more and more, we're starting to see that organisations are looking to simplify their environment by going in for maybe a unified database that has multiple data structures. Yeah, well, >>it's certainly it's interesting when you hear Mongo speak. They don't They don't call out Oracle specifically, but when they talk about legacy r d m r d B m s that don't scale and are complex and are expensive, they're talking about Oracle first. And of course, there are others. Um, And then when they talk about, uh, bespoke databases the horses for courses, databases that they show a picture of that that's like the poster child for Amazon. Of course, they don't call out Amazon. They're a great partner of Amazon's. But those are really the sort of two areas that mangoes going after, Um, now Oracle. Of course, we'll talk about their converged strategy, and they're taking a similar approach. But so help us understand the difference. There is just because they're sort of or close traditional r d B M s, and they have all the drawbacks associated with that. But by the way, there are some benefits as well. So how do you see that all playing >>out? So you know it. Really, uh, it's coming down to the the origins of these databases. Uh, I think they're converging to a point where they are offering similar services. And if you look at some of the benchmark numbers or you talk to users, I from a business point of view, I I don't think there's too much of a difference. Uh, technology writes. The difference is that Mongo DB started in the document space. They were more interested in availability rather than consistency. Oracle started in the relation database with focus on financial services, so asset compliance is what they're based on. And since then they've been adding other pieces, so so they differ from where they started. Oracle has been in the industry for some since 19 seventies, so they have that maturity. But then they have that legacy, >>you know, I love. Recently, Oracle announced the mongo db uh, kpi. So basically saying why? Why leave Oracle when you can just, you know, do the market? So that, to me, is a sign that Mongo DB is doing well because the Oracle calls you out, whether your workday or snowflake or mongo. You know, whoever that's a sign to me that you've got momentum and you're stealing share in that marketplace, and clearly Mongo is they're growing at 50 plus percent per year. So thinking about the early I mentioned 10 gen Early on, I remember that one of the first conferences I went to mongo conferences. It was just It was all developers. A lot of developers here as well. But they have really, since 2014, expanded the capabilities you talk about, Atlas, you talked about all these other you know, types of databases that they've added. If it seems like Mongo is becoming a platform company, uh, what are your thoughts on that in terms of them sort of up levelling the message there now, a billion dollar plus company. What's the next? You know, wave for Mongo. >>So, uh, Oracle announced mongo db a p i s a W s has document d. B has cost most db so they all have a p. I compatible a p. I s not the source code because, you know, mongo DB has its own SPL licence, so they have written their own layer on top. But at the end of the day, you know, if you if you these companies have to keep innovating to catch up with Mongo DB because we can announce a brand new capability, then all these other players have to catch up. So other cloud providers have 80% or so of capabilities, but they'll never have 100% of what Mongo DB has. So people who are diehard Mongo DB fans they prefer to stay on mongo db. They are now able to write more applications like you know, mongo DB bought realm, which is their front end. Uh, like, you know, like, if you're on social media kind of thing, you can build your applications and sink it with Atlas. So So mongo DB is now at a point where they are adding more capabilities that more like developers like, You know, five G is coming. Autonomous cars are coming, so now they can address Iot kind of use cases. So that's why it's becoming such a juggle, not because it's becoming a platform rather than a single document database. >>So atlases, the near the midterm future. Today it's about 60% of revenues, but they have what we call self serve, which is really the traditional on premise stuff. They're connecting those worlds. You're bringing up the point that. Of course, they go across clouds. You also bring up the point that they've got edge plays. We're gonna talk to Verizon later on today. And they're they've got, uh, edge edge activity going on with developers. I I call it Super Cloud. Right, This layer that floats above. Now, of course, a lot of the super Cloud concert says we're gonna hide the underlying complexity. But for developers, they wanna they might want to tap those primitives, so presumably will let them do that. But But that hybrid that what we call Super Cloud that is a new wave of innovation, is it not? And do you? Do you agree with that? And do you see that as a real opportunity from Mongo in terms of penetrating a new tan? >>Yes. So I see this is a new opportunity. In fact, one of the reasons mongo DB has grown so quickly is because they are addressing more markets than they had three pandemic. Um, Also, there are all gradations of users. Some users want full control. They want an eye as kind of, uh, someone passed. And some businesses are like, you know, we don't care. We don't want to deal with the database. So today we heard, uh, mongo db. Several went gear. So now they have surveillance capability, their past. But if you if you're more into communities, they have communities. Operator. So they're addressing the full stack of different types of developers different workloads, different geographical regions. So that that's why the market is expected. >>We're seeing abstraction layers, you know, throughout the started a physical virtual containers surveillance and eventually SuperClubs Sanjeev. Great analysis. Thanks so much for taking your time to come with the cube. Alright, Keep it right there. But right back, right after this short break. This is Dave Volonte from the Javits Centre. Mongo db World 2022. Thank you. >>Mm.