Good day, everyone and welcome to MongoDB Second Quarter 2019 Earnings Call. Today's conference is being recorded. At this time, for opening remarks, I’d like to turn things over to Mr. Brian Denyeau. Please go ahead, sir.

Thank you, Kelly. Good afternoon and thank you for joining us today to review MongoDB's second quarter fiscal 2019 financial results, which we announced in our press release issued after the close of market today. Joining in the call today are Dev Ittycheria, President and CEO of MongoDB; and Michael Gordon, MongoDB's CFO. During this call, we may make statements related to our business that are forward-looking under federal securities laws. These statements are made pursuant to the Safe Harbor provisions of the Private Securities Litigation Reform Act of 1995, including statements related to our financial guidance for the third quarter and full year of fiscal 2019, our market opportunity, our go-to-market and growth strategies, our introduction of future product enhancements, potential advantages of those enhancements, and the impact of these product enhancements on our gross margin and sales opportunity, our ability to expand our leadership position and drive best-in-class revenue growth and the anticipated benefit of our platform for our customers and partners. The words anticipate, continue, estimate, expect, intend, will and similar expressions are intended to identify forward-looking statements or similar indications of future expectations. These statements reflect our views only as of today and should not be reflected upon as representing our views as of any subsequent date. We do not have plans to update these statements except as required by law. These statements are subject to a variety of risks and uncertainties that could cause actual results to differ materially from expectations. For a discussion of the material risk and other important factors that could affect our actual results, please refer to those contained in our annual report on Form 10-K filed with the SEC on March 30, 2018 and our other periodic filings with the SEC. These documents are available on the Investor Relations section of our website at www.mongodb.com. A replay of this call will also be available there for a limited time. Additionally, non-GAAP financial measures will be discussed on this conference call. Please refer to the tables in our earnings release on the Investor Relations portion of our website for a reconciliation of these measures to their most directly comparable GAAP financial measures. And with that, I'd like to turn the call over to Dev.

Thanks, Brian. Thanks to all of you for joining us today to review our second quarter results. We are incredibly pleased with our second quarter performance, which reflects the positive impact the investments in our product and go-to-market efforts are having on the business. To quickly summarize our second quarter results, we generated revenue of 57.5 million, a 61% year-over-year increase, which was above the high end of our guidance. We grew subscription revenues 63% year-over-year. We ended the quarter with over 7,400 customers, up 72% compared to a year ago. We saw strong growth across all major regions, including North America, EMEA and Asia. Atlas revenue grew more than 400% year-over-year and now represents 18% of revenue and we raised 254 million in net proceeds from our successful convertible notes offering. Our second quarter results further demonstrate MongoDB's clear leadership as the modern database platform of the future. Customers recognize that MongoDB offers the best way to work with data, to put data intelligently where it's needed and to allow customers to run applications anywhere. The MongoDB platform offers sophisticated ways to manage data and we are extending that further with the introduction of Global Clusters and MongoDB Atlas. This groundbreaking technology allows customers to easily create policies to strategically distribute data closer to their users for low latency of read and write operations. In addition, with this feature, customers can easily comply with the ever-changing and increasingly demanding regulatory environment for managing data like Europe's new GDPR rules. This is a big competitive differentiator for us, as it is incredibly challenging, if not impossible for companies to orchestrate these types of sophisticated data policies with legacy databases. Our ability to address these types of complex data problems is a significant driver in the increasingly strategic nature of our…

Thanks, Dev. As mentioned, we're very pleased with our second quarter performance and it was our fourth strong quarter as a public company. I'll begin with a detailed review of our second quarter results and then finish with our outlook for the third quarter and full fiscal year 2019. Total revenue in the quarter was 57.5 million, up 61% year-over-year. Subscription revenue was 52.9 million, up 63% year-over-year and professional services revenue was 4.6 million, up 48% year-over-year. In addition to our strong net customer acquisitions and expansion activity, we also recognized approximately $1.5 million of revenue that we had not anticipated during the second quarter. This was primarily due to a greater contribution to revenue from new contracts signed in the quarter, as well as the favorable impact related to bundled services subscriptions. Recall, when we sell software and services on a bundled basis, we do not begin recognizing subscription revenue from customers until the delivery of services has commenced. In Q2, this led us to start recognizing revenue from these customers in the second quarter versus our expectation that they would begin in the third quarter. The second quarter was also another strong quarter for MongoDB Atlas. Atlas represented 18% of revenue during the quarter, up from 5% in the year-ago period and 14% last quarter. During the quarter, we experienced some large Atlas wins, a few of which generated additional revenue as a result of testing, launching or migrating their applications. This reflects the elastic nature of cloud-related workloads and serves as a reminder that customers can have periods of elevated or reduced usage based on customer specific factors, including the application's lifecycle. We continue to see strong global demand for our offerings. During the second quarter, we grew our customer base by approximately 800 customers, bringing…

[Operator Instructions] We’ll hear first from Raimo Lenschow with Barclays.

Hey, congrats from my side. Two questions on Atlas, if I may. First, Dev, can you talk a little bit about the partnerships and what they are bringing to the table that you're seeing around Atlas distribution around AWS and IBM. I know IBM is a little bit early, but just what has been the reception there. And what's AWS doing to help you? That's my first question.

Sure. So just to be clear, so with regards to IBM, our relationship with IBM today does not include Atlas. And so it is designed for our on-prem enterprise advanced product. In terms of AWS, well, AWS has really helped on the demand fulfillment side, because customers can choose to procure Atlas to their marketplace program and so what it allows a customer to do is really reduce the friction in the process of basically procuring Atlas when they decide that MongoDB is a preferred choice. We also do obviously participate in a number of AWS Summits around the world. Obviously, they tend to bring lots of people, especially developers to these conferences and we view that as an opportunity to basically speak about what we're doing with MongoDB and Atlas in particular.

Okay. Perfect. And then the next one on Atlas is, if you think about the -- now that you have -- trying to have the enterprise features available, how do you -- what are the first examples in terms of how people are going to adopt? Is this kind of going to be like a lot of test and development initially or are people kind of quickly moving over and using it? Can you just kind of give us a little bit of feedback how you see that?

Yeah. I think -- so the enterprise features in Atlas are just allowing us to go after it, even workloads that have very strict, for example, security requirements. With the new features we have in Atlas, like enterprise key management, customers can bring their own keys and have comfort that no one else can see their data. We allow integration to LDAP. We allow you to do very sophisticated auditing of the database. So for those customers who have those extra level of security requirements, it really enables them to feel very comfortable of moving their workloads to the cloud on Atlas. And so it really expands the, what I'd say, the addressable market of Atlas, and allows customers to just be more and more comfortable of going to the cloud, using MongoDB Atlas.

We’ll hear next from Sanjit Singh with Morgan Stanley.

Thank you for taking the questions. Congrats on the accelerating growth trends of this quarter. I wanted to follow up on Raimo's question. I'm just trying to talking about the enterprise opportunity, not just with Atlas, but given a multi-document ACID support, you're rolling out Global clusters. Could you help -- Dev, can you help us understand like where does a customer lean more towards Enterprise Advanced versus Atlas. And what is your sort of view on how enterprise adoption is going to unfold throughout the balance of the year versus your commercial business?

Yes. So, our strategy, one of the key differentiating points about MongoDB is really give customers the freedom to run their workloads anywhere. And today, we have customers who run MongoDB on the mainframe. We have customers -- we have lots of customers who run it on-premise and as you can obviously see with the Atlas results, we have lots of customers who are now consuming MongoDB as a service. I should also say we also have lots of customers who buy Enterprise Advanced, but self-manage it in the cloud as well. So, we literally run the gamut of all the variety of options and we just believe that it's important to give customers choice. Every customer is at a different stage in their journey to the cloud. We have lots of government agencies, who are very, very careful and frankly cannot use the public cloud infrastructure today. We have lots of financial services customers, who for regulatory reasons, cannot use the public cloud today and so, we address their needs through our capabilities on-prem, and then we have lots of other customers even large enterprises to emerging startups, who are moving either select workloads or the entire business to the cloud, and having that choice really allows us to serve in a wide spectrum of needs. In terms of directionally, we clearly see everyone is on some journey to the cloud. So, we see the cloud becoming an increasingly important part of the business for MongoDB. Obviously, the Atlas results speak for themselves. The other advantage I think that we give customers is not just freedom to run the cloud, but to run on any cloud provider. And so, one of the things that we hear and we see a lot of enterprises do now is try and work with multiple cloud providers. They may have a primary and then a secondary, and the comfort they have going with MongoDB is that it's very easy to move applications from one cloud provider to another cloud provider. So, they don't have to worry about being locked into any one particular cloud. So, that's another big advantage of using MongoDB.

I appreciate the answer. Maybe a follow-up question and sort of thinking down the road in terms of serverless. I know on Stitch, you guys are rolling out Stitch as well. But just, maybe more higher level, what does serverless, as customers gravitate more towards serverless computing methods, what do you see as sort of the impact on the business in terms of the demand for database services from MongoDB’s perspective?

Yes. I mean, the company was basically founded to make a developer’s life really easy. To really let developers and organizations move very, very quickly and being able to develop applications that drive the business. And what basically serverless does for us is that it really allows developers to avoid all the mundane and tedious back end work that they normally have to do and basically only focus on value-added coding. And that becomes really, really important, because as customers and specifically developers think about what platform to use, they'll naturally gravitate to platforms and make their lives significantly easier. So MongoDB's popularity was driven by the fact that the document model and our approach just makes a developer’s life so much easier by giving them a very easy way to work with data, by making it very easy to move and put data where you want it from a scalability, reliability, availability point of view, and Stitch just takes that next level where they can basically not have to deal with all of the backend TDM work they have to do to build any web or mobile app. And so what Stitch does is allow you, for example, to essentially expose the power of a database through front-end code where you can basically create a database from the client side. It allows you to easily integrate to third party services whether it’s a payment service like Stripe or a notification like Twilio or even a third party service, an internal third party service that you may have. With Stitch now, you can use Stitch to sync data between your mobile device with MongoDB Mobile to the back end. And there's even things like with triggers or what used to announce previously with change streams, you can now easily enable the ability to take action on events or changes in your database. So when you think about where the world is going, JSON is becoming the synonymous with the word modern applications. MongoDB is the pre-eminent JSON database and Stitch basically, you should think about Stitch as really the lubricant that allows people to move very, very quickly and faster in building applications.

We’ll hear now from Heather Bellini with Goldman Sachs.

Hi, great. I had a few questions if you will. I wanted to follow-up on what you were talking about with Stitch and talking about serverless. I was just wondering if you could give any color on how you are seeing people to deploy applications, kind of momentum between serverless and containers, if you can just give us your take. And then also I wanted to ask a little bit about NoSQL competitive landscape and just see how you would kind of stack things up right now and kind of the breadth of your product offering and how it stacks up versus the competitive universe, if you’ve noticed any changes in you guys pulling ahead of the competition.

Yes. Sure. So I want to just clarify. So containers, basically, the world is moving to containers because it's just an easy way to manage infrastructure. Kubernetes has become the de facto platform that everyone is gravitating to. There were a few other options a few years ago, but Kubernetes has become the standard. What we have done is basically create an operator for Kubernetes where people from the Kubernetes platform can basically manage provisioning and orchestrating and basically migrating databases on a kind of a containerized environment. So, that makes -- so customers are incredibly excited about that, because as people move to containers, it becomes as easy to manage MongoDB, because we support those containerized environments. Stitch is all about enabling developers to basically become much more productive and move much more quickly in building applications. Everyone is under pressure to try and increase the development velocity of the development teams and the way you can do that is by giving them a very modern platform that allows them to build applications quickly, to add features quickly, and to basically reduce the need to do a lot of what developers consider a lot of mundane and tedious tasks. And so, for example, with Stitch, you don't have to use an app server anymore because typically the app server is where you program the application logic. Now, you can do that from front end code where the intelligence moves to the client side and basically, query the database and basically eliminate the need for that middle tier. So, that makes a developer’s life very easy. Plus invariably, as you move to a micro services architecture, there may be third-party services or internal services you want to integrate to. Stitch makes that incredibly easy. There may be things that you want to do when like those changes happening to your database. For example, I'll use example where like say you're an airline company and you decide to move the flight from New York to Phoenix, from one gate to another, when that database event happens, you can automatically generate a trigger that sends a notification to everyone's mobile app saying, this gate has changed. Today, it's done on a pull notification. Now, you can push those notifications out. So, these are all things that if you didn't have Stitch would make a developer’s life a lot more complicated and they have to spend a lot more time coding these applications. Stitch allows developers to really abstract all that mundane work and really focus on value added development.

Right. And then just the competitive tier kind of with all this that you're putting out there, have you noticed a widening in your weed? Any comments on kind of the competitive universe that you could share?

Yes, I mean, we do not frankly see other NoSQL vendors in deals anymore. I mean, I'm sure that they're getting deals, but we frankly see them less and less. I can't remember the last time, I had a sales rep complain to me about a competitive situation with another NoSQL competitor. I think it's become clear to everyone that we have become the de facto leader in the modern database space and now customers are just contemplating what workload should they move to the cloud and what new app should they build on MongoDB. And that's where our salespeople are spending the most time.

From Stifel, we’ll hear from Brad Reback.

Great. Thanks very much. Dev, the last few quarters, I think the last three in a row, you batted about a 1,000 average customers sequentially. Should we think about that as the sustainable rate going forward or is there an opportunity to step that up?

Again, there's two parts to our Atlas business. It's our self-serve business and our sales-force [ph] business. Our self-serve business, we started first and we got a lot of traction very, very quickly. And for the last, I would say, year, have been really focused on enabling our sales force to drive Atlas deals and those deals tend to be significantly bigger than the self-serve deals. And so we're seeing -- we've seen material progress and growth on the sales side. I think you're going to see us continue to invest and innovate on both sides of the business. We think the self-serve channel is a very unique channel for us. It's basically servicing the long tail of our business, especially in markets that we don't necessarily have a presence in. And so you'll see us and we already are investing even more aggressively in our self-serve business. So you are going to see us invest in both parts of the business. But I think what we're really pleased with today is just the uptake on the sales side where we're seeing material contribution and bigger and bigger deals, deals happening more quickly and quicker up sales from the sales organization, which we're very happy about.

And then maybe one quick follow up. As you think about your future acquisition strategy, given the recent capital raise, are there any real pressing needs or will it be very much a tactical type of execution going forward?

Yeah, we really consider the ability to raise capital last quarter as really opportunistic. We didn't have any kind of near term kind of needs to use that cap -- deploy the capital for either M&A or any other kind of operational needs. We just found, saw an opportunity to raise a lot of cheap capital. It clearly allows us to be more aggressive, should the opportunity arise. But right now, we have no near-term pressing needs to use that capital.

[Operator Instructions] We’ll hear now from Jack Andrews with Needham.

Dev, on the last earnings call, you talked about -- you referenced some 20 plus conversations you were having with C level executives in terms of just the increasing strategic importance of MongoDB. I was wondering if you could kind of update us on the amount of conversations you're having and just what is the -- where are those conversations leading today?

I would say that those conversations are frankly increasing. We have changed our sales methodology, where we're asking our sales people once they do sufficient kind of homework on an account to go high in the implementation as quickly possible for a number of reasons. One, to qualify where the real demand and interest is in kind of potentially using MongoDB. Two, to kind of educate those senior level stakeholders on our differentiation and value proposition. And three, to basically increase the velocity of business, even if you get a deal, if you have the air cover, it's much easier to go and ask for the follow-on deal because the senior level stakeholders are now fully aware of the value we can add. So, now, we've changed our engagement model where we’ve kind of institutionalized that where we try and get high very early in the sales process and that's starting to pay big dividends for us.

And then just as a follow-up, could you update us in terms of how you're thinking about the mainframe modernization opportunity in particular? I mean, what's the sense of urgency from customers around mainframe based applications?

Yeah, I mean, so it really varies. As I said, we do have some customers who are happily running the mainframes and want to run MongoDB, because at some point in time, they do recognize that there's a certain half-life to their mainframe real estate and so they want to potentially migrate their applications, while running on the mainframe, but then have an easy glide path to a more modern, compute environment, whether it's on-prem or in the cloud. That's point number one. Point number two, we do see, in many situations where the use cases or the changing nature of their needs of the business is requiring them to consider offloading workloads from the mainframe to a more modern kind of computing architecture. And that's where customers are very interested. We have lots of proof points, where we have customers, large banks, large tech companies, service companies and so forth who are moving workloads off the mainframe on to MongoDB. And so, what we try and figure out is what is the problem of the pain that customers are having, whether it's a cost problem, because the mix utilization on the mainframe is getting too high, whether it's a performance problem because they can't really address the needs of the users and then, we will then obviously work with them and help them think through all the available options. And so, the mainframe offload use case is a very popular one in our sales force, but there are as many others as well. So, it's really depending on what's going on in that particular account.

We’ll hear next from Brent Bracelin with KeyBanc.

Thanks for taking the question. Dev, maybe for you, I wanted to go back to the quarter. If I look at just the revenue growth, 61% growth is the highest we've seen here in two years, on a sequential basis, 19% growth is the highest we've seen also on record here in the last couple of years. So my question is why now? Why are you seeing this acceleration in the business? Is it a confluence of internal factors that are driving it, even if I look at the MongoDB business, ex Atlas, it also accelerated? So walk us through why you think this is happening? How much of it is kind of company-specific things you're doing internally versus just the external factors and the market being kind of ready for a more modern database?

Thank you. So we do feel good about our position. We do feel good that every quarter we're getting more and more credible with customers and being really the default modern database for all the use cases. We do feel like, we as an organization are executing better. We're getting -- the efficacy of our go-to-market efforts are just getting better. We are expanding to different regions. We also think the product road map and product execution has been incredibly strong, and so we feel very good about, not just the core product, but obviously Atlas has grown really, really quickly. We've added new features and capabilities. We’ve rolled out new products like Stitch and Mobile. So we feel like it's not one thing. I would also say and Michael talked a little about this in his prepared remarks, there were some one-time events that happened, I would say, in Q2 that we just didn't expect. So I wouldn't want you to extrapolate that this is the new normal. But we obviously feel very good about the state of the business and the trajectory of the business.

And then as a follow-up for Michael. Maybe if I look at the gross margin profile here, I guess it's a little surprising that you're able to kind of hold the gross margins even with the strength that you're seeing in Atlas. So can you just walk us through with that material mix shift to Atlas, how you're able to kind of sustain the gross margin profile here.

Yes, sure. So as I mentioned earlier, we've made very good progress on the Atlas gross margins, relative to our expectations and we're tracking well ahead of plan in terms of gross margins. Atlas's still lower gross margin than the balance of the business. And so we still have plenty of levers to flip or turn and dials to adjust. On the business, we mentioned that the first thing that we had done which we'd said we'd do by the end of the year is we've introduced some of the premium features and Enterprise Advanced, meaning principally the advanced security features into availability in Atlas. We've not yet seen the benefit of that, because we only just introduced that. But over time, that should be very accretive both from a revenue perspective as well as from a gross margin perspective. And there are some internal cost optimizations that are also available to us. So, I think the short answer is, we've had very strong execution relative to our kind of margin game plan for Atlas, but we've got more work that we want to do on that front, but we're very pleased with the progress to-date.

And from JMP Securities, we’ll hear from Pat Walravens.

Okay. Thanks. And let me add my --

I think we lost you, Pat. Pat, are you still there? Operator, I think we may have lost Pat.

Okay. We’ll move on to Brian White with Monness, Crespi.

Dev, I'm wondering how we should think about competition from the leading public cloud vendors? They both had conferences over the summer. Database was a major focus, a lot of new innovations and I know Google was playing up the Cloud Firestore NoSQL database, and they did an update recently. So, maybe if you could just give us some color on how we should think about these big competitors?

Yes. Obviously, we have great relationships with the cloud providers themselves. They're the ones -- just to remind you, they're the ones who help fund development of Atlas onto their particular cloud platforms. They did so, because it saw the amount of MongoDB usage on their specific clouds. I think the second thing I would say is that one of the things that's always been a strength of MongoDB is the developer mind share that we've had and the popularity of the platform. And so, I would say that doesn't happen overnight and we've been shipping product for over 10 years now -- almost 10 years now and so, that -- and the people are very familiar with the product. The feature set is far superior to any other kind of other modern database. I would say most of the database offerings from the cloud providers have two core limitations. One, they tend to be built on key value stores, which have a lot -- have far more limited functionality in terms of the expressiveness of the query language and other features that they just don't have. The second thing is they really lock in a customer onto that specific cloud platform. And I think most customers today are much more sensitive about locking than they have been in the past, especially given the state of their relationships with legacy database vendors. And so that's another consideration. So with MongoDB, you truly have the freedom to run MongoDB anywhere. It is truly one of the most popular -- in fact is the most popular modern database in the world today. And they've also seen just the rapid innovations that we've had to offer and so we feel very good about our positioning.

And with support for ACID on 4.0, are there new use cases. I know it's early, but that are coming into the conversation that maybe you didn't see before?

Oh, most definitely. The level of conversations and the tone of conversation has changed radically since we announced support for ACID. And so I think it's taken off the potential objection people had, is that could they really use us for certain use cases where ACID type data guarantees was required. And so it's really helped change the nature of the conversations and we feel like it's only expanding the aperture of use cases we can go after.

[Operator Instructions] We’ll move next to Tyler Radke with Citi.

I was running around different calls today. I apologize if my question has been asked already. I just wanted to ask you about the -- among your existing customers, just what that looks -- or I guess in terms of Atlas, what that looks like in terms of adoption by existing customers that are using the self-managed version of MongoDB versus net new how that's kind of split today.

Well, Atlas, just as so we're all clear, Atlas is a different consumption model. So you have to have chosen MongoDB for your database, for your application before you would consider using Atlas. What Atlas does, it allows you to basically outsource all of the ongoing provisioning management, backup, patching, updating of your infrastructure and really allow you to focus on allowing you to build better apps that can address the needs of your business. And so we tend to see customers who are -- we tend to see all types of customers. Customers moving new workloads onto Atlas. We see customers migrating existing workloads onto Atlas. We see customers who are using MongoDB on-prem, spin out new instances on Atlas. We see development workloads on Atlas. We see test workloads in Atlas and we see production workloads in Atlas. And we see this globally. So Atlas is the most widely available database or service offering. Today, I believe it's available in like 57 different regions. No other database or service vendor can claim that because of the virtue that we can run across Amazon, Google and Microsoft's real estate. And so, in terms of geo-coverage, we are the most widely available offering. And so we tend to have customers almost across every industry, nearly every geography using Atlas in some way, shape or form.

Great. So, it sounds like a combination of existing as well as new. Just a follow-up on the competitive environment, I was just wondering if there's any update there on either from the legacy players, and maybe a comment I might have missed it on, what percent of your deals are involved in legacy displacements? But also, I'd be curious to hear your take on the competitive environment in a non-legacy world and kind of the NoSQL world if you will?

Yeah. So we tend to see about 30% of our business typically on average every quarter be migrations of legacy workloads to MongoDB. And so, we continue to see lots of existing workloads move to MongoDB. And obviously, we also see lots of new workloads coming to MongoDB, because it's so much easier to build application in MongoDB than a relational database. In terms of the new vendors, this question was asked before, we typically are not seeing some of the other NoSQL players anymore. I think the market has clearly consolidated around MongoDB and we feel -- we see that in terms of people kind of standardizing on MongoDB at least -- at minimum as one of the core database platforms as they plan to use in their enterprise. And so, from a competitive point of view, I would say the legacy vendors are more competitive from a wallet share where they have an existing share of the wallet, but from a technology point of view, they're becoming less and less relevant.

And we’ll go back to Pat Walravens.

So, I have two questions. One is sort of following up on these competitive questions. If you look specifically like, Oracle seems to be trying to react, they have the self-healing functionality and they're pushing the database on cloud and the database in the cloud is cheaper. What's the customers’ reaction to that? Is it going to work? And do you think the pace of migration from workload to Mongo accelerates?

Well, I mean, I would tell you that since I've been with the company now, I'm coming close to my four year anniversary, I would say the antipathy towards the legacy vendors has never been higher. So we do see customers very, very motivated to move off their legacy platforms as a function of their relationships with those vendors. And so that's one big reason. The second big reason is that the architecture of these legacy databases is frankly old. The relational database, the first white paper came out 50 years ago and Oracle was founded 41 years ago. And so, yes, they obviously add a lots of features and capabilities. But if you want a very modern platform that allows you to scale gracefully, that allows you to add features very, very quickly, that allows you to move data easily all around the world to serve your user base, you can't really do that easily on a legacy database. And so when you look at like the computer science programs that the leading colleges have, MongoDB is one of the most popular technologies that students develop on today. I had one customer state publicly at MongoDB World that once you go MongoDB, you can't go back. So the MongoDB is a much more compelling platform to build applications on than relational databases. And so until we see that happening as well, that's a big driver to why customers are going with MongoDB.

Great. And then my follow up is more specific. So how important are graph databases and how does that work for Mongo?

Yes. So graph databases were designed for certain use cases around mapping, kind of say social profiles and independent relationships between -- who your friends are or social interconnections. We've actually already embedded a bunch of graph functionality into MongoDB, and you'll see us continue to add more functionality over time. And so we don't believe it makes sense for a customer to choose a net new database for every net new use case. It just doesn't become scalable, it's hard to manage, hard to support. It's hard for your developers to learn all these different technologies. And so we see customers increasingly standardize on MongoDB, because we address the widest set of use cases available in the marketplace.

And at this time, I’d like to turn things back over to Dev Ittycheria for any closing remarks.

Well, thank you again for joining us on this call. I'd like to reiterate we feel really good about the business. We're very proud about what we accomplished in Q2, but we know that we have a huge opportunity in front of us and it's back to the [indiscernible] for us. So thank you again for joining the call and we wish you well. Take care.

And that does conclude today's conference. Thank you all for joining us.