Desmond
My feedback
1 result found
-
11 votes
An error occurred while saving the comment Desmond
supported this idea
·
We're glad you're here
Please sign in to leave feedback
Signed in as
(Sign out)
We're glad you're here
Please sign in to leave feedback
Signed in as
(Sign out)
Feedback and Knowledge Base
-
Searching…
No results.
Clear search results
-
Give feedback
- Atlas 1,332 ideas
- Atlas App Services 238 ideas
- Atlas CLI 25 ideas
- Atlas Search 158 ideas
- Atlas Stream Processing 5 ideas
- Charts 250 ideas
- Compass 436 ideas
- Connectors (BI, Kafka, Spark) 41 ideas
- Data Federation and Data Lake 57 ideas
- Database 297 ideas
- Database Tools 0 ideas
- Documentation 11 ideas
- Drivers 77 ideas
- Education 39 ideas
- FLE and Queryable Encryption 3 ideas
- MongoDB Analyzer (for .NET) 2 ideas
- MongoDB for VS Code 73 ideas
- MongoDB Shell 36 ideas
- Ops Tools 462 ideas
- Realm 96 ideas
- Relational Migrator 3 ideas
- Support Website 17 ideas
- UI 113 ideas
- Vector Search 7 ideas
Hi Andrew,
I'm Desmond, the DBA at LIVE17, a long-term partner of Mongo. From a cloud SaaS operations perspective, I strongly recommend enabling the 'Cluster Rename' feature. This recommendation goes beyond just the convenience of switching from -dev or - test to prod mode without the need to move a large amount of data.
We understand that changing the cluster name affects the Cluster endpoint. In situations where we want to quickly recover from a disaster, we opt to restore a new cluster (e.g., MongoDB-bak) from the most recent snapshot. If the Cluster Rename feature is available, we won't need to spend extra time modifying API endpoints or any DNS Route53 settings. We can utilize the Cluster Rename feature to switch the Cluster endpoint, minimizing downtime.
This function has been present in AWS RDS for quite some time, significantly reducing the complexities of cloud SaaS operations. We believe MongoDB's goal is also to address the frequent data migration challenges during development.
Sincerely,
Desmond