There’s a lot of “cross pollination” on this board. While you’re reconsidering you MDB position, I’m scrutinizing my SQ position. Thinking I don’t want to pull the plug, but quite possibly it shouldn’t be as large as it is. I just don’t feel any urgency to trim and I want to have a good idea where I’ll redeploy the cash if I do partially liquidate it.
For what it’s worth, I’d probably suggest reducing Nutanix if you want to get back into Mongo. NTNX doesn’t seem likely to take off any time soon, since overall revenue growth is expected to be fairly pedestrian for the next few quarters.
Thanks for the idea, Bear, but while each of them has ambivalences, the problem is that I have slightly more conviction in Nutanix than in Mongo.
On MongoDB, Saul wrote, in part: worry about the long term viability of their open source business model, when perhaps using the open source solution may turn out to be “good enough” for many companies to just use it for free.
I’d just want to point out that Amazon is NOT giving away its DocumentDB alternative. It charges for it, as documented here: https://aws.amazon.com/documentdb/pricing/
BTW, such compatibility with MongoDB has already existed with Microsoft Azure at least since 2017 (see https://azure.microsoft.com/en-us/blog/documentdb-api-for-mo… ), yet Mongo continued to grow quickly even after that. The MS link says:
What is API for MongoDB?
DocumentDB: API for MongoDB is a flavor of DocumentDB that enables MongoDB developers to use familiar SDKs, tool chains, and libraries to develop against DocumentDB. MongoDB developers can now enjoy the advantages of DocumentDB, which include auto-indexing, no server management, limitless scale, enterprise-grade availability backed by service level agreements (SLAs), and enterprise-grade customer support.
What is happening is that the open source model has enabled Amazon to quickly build up a compatible commercial offering themselves.
AWS gets more exposure in the press than MS’s Azure, but many a corporation has standardized on Microsoft products overall. My own current company’s IT department is Azure based, which they did as an extension of Outlook, for instance. My own view is the Amazon makes things simpler for engineers to set things up themselves, so it’s better for internal proof-of-concept and smaller projects, while Microsoft throws lots of support people at you, so it’s better for larger IT departments that are happy to outsource the setup and configuration.
But, back to Mongo, my belief remains that Mongo will continue to grow and that adoption by Microsoft a couple years ago and now Amazon recently are indeed reinforcements that Mongo’s DB model is the current best of breed with no alternative in the future yet clear.
As usual, technical superiority doesn’t always translate to company financial success. It remains to be seen whether Amazon’s entry takes away customers from MDB, or whether it gets future customers to look more seriously at MongoDB’s technically superior offerings.
Thanks for the info, really helpful! I particularly enjoy your write-ups on the various tech companies in your portfolio.
I was wondering, when do you expect to post regarding February and/or March?
Unless I missed it, I could not find the link to those posts.
Please let me know.
when do you expect to post regarding February and/or March? Unless I missed it, I could not find the link to those posts.
Hi Dan, they are: