(no title)
kosherhurricane | 3 months ago
Having said that, MongoDB pricing page promises 99.995% uptime, which is outstanding, and would probably be hard to beat that doing it oneself, even after adding redundancy. But maybe you don't need that much uptime for your particular use case.
buster|3 months ago
In fact after looking at https://www.mongodb.com/legal/sla/atlas/data-federation#:~:t... it makes me wonder how much worth the SLA is. 10% Service Credit after all the limitations?
Atlas can take their 10% Service Credit, i wouldn't care. Save the money and chose a stable provider.
arbol|3 months ago
> maybe you don't need that much uptime for your particular use case.
Correct. Thanks for reading!
tecleandor|3 months ago
Also, we noticed that after migration, the databases that were occupying ~600GB of disk in our (very old) on premise deployment, were around 1TB big on Atlas. After talking with support for a while we found that they were using Snappy compression with a relatively low compression level and we couldn't change that by ourselves. After requesting it through support, we changed to zstd compression, rebuilt all the storage, and a day or two later our storage was under 500GB.
And backup pricing is super opaque. It doesn't show concrete pricing on the docs, just ranges. And depending on the cloud you deployed, snapshots are priced differently so you can't just multiply you storage by the number of the snapshots, and they aren't transparent about the real size of the snapshots.
All the storage stuff is messy and expensive...
gervwyk|3 months ago
gizzlon|3 months ago
Or.. what? That's the important part