This is a snippet of the transcript, sign up to read more.
Now, to your point about optimizing MongoDB, it really depends on a number of factors. I've worked in accounts where it could be as easy as turning off certain clusters that are not being used, or turning off development environments, or staging environments that were just on without much usage. Right. So just basic low-hanging fruit that people were not paying too much attention to in prior years, they are now being a lot more careful about things like that. So, there's that layer of low-hanging fruit that you can just cut really easily, and then there are those areas where things could get a little bit more complicated, right? For instance, choosing other types of technologies or layers of technologies that could prevent higher consumption of MongoDB. Adding a caching layer that's not on MongoDB would prevent more utilization at the database layer. That's cheaper than actually buying more MongoDB Atlas or scaling a cluster to multiple nodes. Say you are on 10 nodes, and if you are anticipating high traffic, you might need to add another five nodes. Instead of doing that, you put a caching layer that's cheaper and will attend to the performance that the end users are expecting, and that obviously impacts the MongoDB revenue. So, I think naturally, companies are looking to do things like that. Some of the largest consumers of MongoDB in the West were actually on active plans to reduce their consumption of Atlas when I was there back in '22.
This is a snippet of the transcript, sign up to read more.
This document may not be reproduced, distributed, or transmitted in any form or by any means including resale of any part, unauthorised distribution to a third party or other electronic methods, without the prior written permission of IP 1 Ltd.
IP 1 Ltd, trading as In Practise (herein referred to as "IP") is a company registered in England and Wales and is not a registered investment advisor or broker-dealer, and is not licensed nor qualified to provide investment advice.
In Practise reserves all copyright, intellectual and other property rights in the Content. The information published in this transcript (“Content”) is for information purposes only and should not be used as the sole basis for making any investment decision. Information provided by IP is to be used as an educational tool and nothing in this Content shall be construed as an offer, recommendation or solicitation regarding any financial product, service or management of investments or securities. The views of the executive expressed in the Content are those of the expert and they are not endorsed by, nor do they represent the opinion of In Practise. In Practise makes no representations and accepts no liability for the Content or for any errors, omissions, or inaccuracies will in no way be held liable for any potential or actual violations of laws, including without limitation any securities laws, based on Information sent to you by In Practise.
© 2024 IP 1 Ltd. All rights reserved.