Hard to confirm the article and the tweet. The author should provide the exact details and operations for someone to replicate and verify, or at least do the math.
Racking up a $2500/day bill is several of magnitudes off - there’s nothing in the article to help put the workload in context.
I have zero interest in mongodb, as a stock or a technology, but this article doesn’t help to actually determine anything about cloud costs. (Lack of data points, irreproducible method and conclusion)
That makes it even more sus. Can you describe your workload? Unless you were doing something extremely heavy-duty for a long time, I just don't see this being at all factual.
Was your code not written with cost control in mind because there was a finite hardware limit you were running yourselves up against? Otherwise, I am baffled at how the difference could be so great between the three.
+1 - the post speaks about 100 times difference between VM and Atlas setup.
At a glance, Atlas cloud has typical ~ 20% premium if we compare their pricing to AWS/Azure VM setup. 20% is not x100.
So IMHO and AFAIK we're speaking here about serious misconfiguration.
Depending on exact specifications that is like $10k of hardware, so 4 days of rent pays the machine in full.
So in this service the actual cost of the hardware is a rounding error. It also needs power, cooling, a roof and some maintenance crew, but that still doesn't come close to the rental price. So what are customers actually paying for?
The mongodb pricing page says one can setup a M10 instance for $57/month. [https://www.mongodb.com/pricing]
Racking up a $2500/day bill is several of magnitudes off - there’s nothing in the article to help put the workload in context.
I have zero interest in mongodb, as a stock or a technology, but this article doesn’t help to actually determine anything about cloud costs. (Lack of data points, irreproducible method and conclusion)