Add a single-node option.
mLab had the option to create a single-node deployment, which was very nice for development environments where redundancy isn't important, but keeping costs down is.
Would be nice to see this in Atlas as well.
Dan
shared this idea
-
Helmut
commented
Hi, especially for staging purpose it would be very important for us to have a single node option. The Shared options seem not to fit our purpose as even in Staging systems we have a lot of data (to detect performance impacts early). We see folks are questioning our costs on MongoDB Atlas for Staging. So having the single node option would helps us on various aspects (development, quality, business).
Cheers, Helmut -
Tiago
commented
Hi Benjamin,
Replacing a single-node option with queryable Cloud Backup might not make sense for us if that implies enabling Continuous Cloud Backup on the cluster. The cost would be higher than a temporary single-node.
Btw, how is that going here? It has been more than 3 years.
-
Hi Tiago,
I am planning on re-introducing the queryable button with cloud backup in the future, which will make what you described not necessary. Stay tuned!
-
Tiago
commented
There is a very good use case for the single-node cluster. Occasionally when we need to restore a backup (snapshot) just to get some information there, we need to provision a whole 3 nodes cluster. It becomes an unnecessary expensive operation as we don't need high availability and won't have much traffic.
The shared/free tier is not an option as it limits the storage to 5 GB.
A single-node cluster would perfectly fit this situation.
-
Scott
commented
Same need. Most of the data I have is ephemeral and replaced hourly. So there's no need for my application to have the redundancy that comes with a higher cost.
-
Hi Dan, We've hoped that folks would find the Atlas shared tier (M0 free tier, M2, and M5) offerings would address the lower-cost offering category. Have you explored these offerings: is there anything we can do to improve them to better service your needs?
