If my application is at a different cloud provider than the one hosting Atlas, is this a problem?

Haim_Barad · 2025-02-18T18:51:09.431Z

We have a next.js application querying a mongo database. This database server is hosted and maintained by our cloud provider (DigitalOcean).

We’re expanding globally and we do notice that queries outside of the geography might have additional latency. Also managing a growing database might be a challenge.

My question is - if we move to MongoDB Atlas (perhaps on AWS), does this make performance more of a problem or less of a problem? What should we consider when looking at this?

Andrew_Davidson · 2025-02-21T15:52:39.922Z

Latency could be an issue but if you were to align the region you use to a hyperscaler region that’s close geographically, it’d likely be close by ping time too. If you find one close enough, it might be effectively equivalent to a cross-availability zone network hop within a hyperscaler region to begin with.

Data transfer cost is another consideration: for larger-scale use cases that move a lot of data over the wire, this could be a problem

Haim_Barad · 2025-02-24T16:12:58.503Z

Thanks for the insight.

Is there anyway to get Atlas-like features in our own DigitalOcean infrastructure, I would appreciate a pointer. Better yet, are you working with DigitalOcean (and perhaps others) to bring Atlas to more cloud providers?