Add MongoDB migration solution bundles to bundle matrix#143
Open
brianamarie wants to merge 6 commits into
Open
Add MongoDB migration solution bundles to bundle matrix#143brianamarie wants to merge 6 commits into
brianamarie wants to merge 6 commits into
Conversation
Document three Atlas and enterprise-exit packages (planning Jumpstart, full migration, modernization) in the canonical bundle matrix and clarify matrix-only structure in README. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
New File Governance CheckNo added markdown files detected. Doc Coverage CheckNo new markdown docs detected. Duplicate Detector
No significant overlap detected. Manual waiver commands (maintainers)
Waiver JSON is stored in a hidden PR comment ( Triggered by |
Contributor
Messaging Smart Suggestions
Only auto-apply suggestions at high confidence with reviewer approval. Triggered by |
Contributor
Messaging Impact Check
licensing-or-open-source-claims (BLOCKING)License and open source positioning changes are cross-cutting. Required review files:
Suggested additional scan:
offering-name-or-tier-change (WARN)Offering naming updates should stay aligned across offering pages. Required review files:
Suggested additional scan:
product-messaging-module-touch (WARN)Product messaging modules often need checks against company framing and shared pillars or offerings. Required review files:
Suggested additional scan:
Manual waiver commands (maintainers):
Waiver state is stored in Triggered by |
andrey-glazkov
previously approved these changes
May 24, 2026
Contributor
andrey-glazkov
left a comment
andrey-glazkov
left a comment
There was a problem hiding this comment.
Looks good to me.
Co-authored-by: Cursor <cursoragent@cursor.com>
Collaborator
Author
|
Small consolidation only, no scope expansion beyond the two original PRs. |
3 tasks
brianamarie
added
Content & messaging
brianamarie
commented
May 27, 2026
| - Operational complexity: Scaling and maintaining HA/DR clusters consumes significant DBA effort. Percona Server for MongoDB includes in-memory storage engine support and file copy-based initial sync, reducing recovery times and operational overhead. The Percona Kubernetes Operator for MongoDB and Percona Backup for MongoDB automate deployment, backups, and failover, while ExpertOps ensures predictable uptime and capacity planning. [Percona Backup for MongoDB 2.13.0 (2026-03-03)](https://docs.percona.com/percona-backup-mongodb/release-notes/2.13.0.html) strengthens backup operations with Workload Identity Federation for GCS (no long-lived service account keys), selective backups that include users and roles, and uninterrupted PITR during logical backups on external storage profiles. Together, these changes reduce security exposure and improve restore reliability for regulated and multi-storage environments. | ||
| - Faster recovery and replica sync: Scaling and maintaining HA/DR clusters consumes significant DBA effort when rebuilds and catch-up lag. Percona Server for MongoDB includes in-memory storage engine support and file copy-based initial sync, reducing recovery times and operational overhead during scale-out and node replacement. | ||
| - Steadier LDAP authentication: For LDAP-backed authentication, Percona Server for MongoDB caches userToDNMapping lookups to reduce repeated directory round-trips during auth. | ||
| - Automated backup and failover: The Percona Kubernetes Operator for MongoDB and Percona Backup for MongoDB automate deployment, backups, and failover, while ExpertOps ensures predictable uptime and capacity planning. [Percona Backup for MongoDB 2.13.0 (2026-03-03)](https://docs.percona.com/percona-backup-mongodb/release-notes/2.13.0.html) strengthens backup operations with Workload Identity Federation for GCS (no long-lived service account keys), selective backups that include users and roles, and uninterrupted PITR during logical backups on external storage profiles. Together, these changes reduce security exposure and improve restore reliability for regulated and multi-storage environments. |
Collaborator
Author
There was a problem hiding this comment.
@radoslawszulgo could you please review this bit?
Contributor
There was a problem hiding this comment.
TBH - I don't like we here releate to the latest release of PBM. This will force us to updated it very often. And still - I don't get the releation of "Automation and relability" to the last release of PBM. I guess we'd need better to refer to general features of PBM that fit into this story.
Collaborator
Author
There was a problem hiding this comment.
@radoslawszulgo My understanding is that the general features of PBM are for backup, which relates to reliability - do I have that wrong?
Contributor
There was a problem hiding this comment.
That's correct. I refer here to the sentence that "Percona Backup for MongoDB 2.13.0 (2026-03-03) strenghtents backup operations with Workload Identity federation .... " -> I don't see that WIF relates to automated backup and failover easily - well - it's an automated authentication - but we have many automated auth integrations - not only Google WIF.
|
|
||
| - Operational complexity: Scaling and maintaining HA/DR clusters consumes significant DBA effort. Percona Server for MongoDB includes in-memory storage engine support and file copy-based initial sync, reducing recovery times and operational overhead. The Percona Kubernetes Operator for MongoDB and Percona Backup for MongoDB automate deployment, backups, and failover, while ExpertOps ensures predictable uptime and capacity planning. [Percona Backup for MongoDB 2.13.0 (2026-03-03)](https://docs.percona.com/percona-backup-mongodb/release-notes/2.13.0.html) strengthens backup operations with Workload Identity Federation for GCS (no long-lived service account keys), selective backups that include users and roles, and uninterrupted PITR during logical backups on external storage profiles. Together, these changes reduce security exposure and improve restore reliability for regulated and multi-storage environments. | ||
| - Faster recovery and replica sync: Scaling and maintaining HA/DR clusters consumes significant DBA effort when rebuilds and catch-up lag. Percona Server for MongoDB includes in-memory storage engine support and file copy-based initial sync, reducing recovery times and operational overhead during scale-out and node replacement. | ||
| - Steadier LDAP authentication: For LDAP-backed authentication, Percona Server for MongoDB caches userToDNMapping lookups to reduce repeated directory round-trips during auth. |
Contributor
There was a problem hiding this comment.
for LDAP we have to highlight we're providing Long-term-support (LTS) for LDAP unlike MongoDB that deprecated LDAP and will remove LDAP with MongoDB 8.0 EOL.
Collaborator
Author
There was a problem hiding this comment.
Good call out - adding to this PR in the product and use case
| - Operational complexity: Scaling and maintaining HA/DR clusters consumes significant DBA effort. Percona Server for MongoDB includes in-memory storage engine support and file copy-based initial sync, reducing recovery times and operational overhead. The Percona Kubernetes Operator for MongoDB and Percona Backup for MongoDB automate deployment, backups, and failover, while ExpertOps ensures predictable uptime and capacity planning. [Percona Backup for MongoDB 2.13.0 (2026-03-03)](https://docs.percona.com/percona-backup-mongodb/release-notes/2.13.0.html) strengthens backup operations with Workload Identity Federation for GCS (no long-lived service account keys), selective backups that include users and roles, and uninterrupted PITR during logical backups on external storage profiles. Together, these changes reduce security exposure and improve restore reliability for regulated and multi-storage environments. | ||
| - Faster recovery and replica sync: Scaling and maintaining HA/DR clusters consumes significant DBA effort when rebuilds and catch-up lag. Percona Server for MongoDB includes in-memory storage engine support and file copy-based initial sync, reducing recovery times and operational overhead during scale-out and node replacement. | ||
| - Steadier LDAP authentication: For LDAP-backed authentication, Percona Server for MongoDB caches userToDNMapping lookups to reduce repeated directory round-trips during auth. | ||
| - Automated backup and failover: The Percona Kubernetes Operator for MongoDB and Percona Backup for MongoDB automate deployment, backups, and failover, while ExpertOps ensures predictable uptime and capacity planning. [Percona Backup for MongoDB 2.13.0 (2026-03-03)](https://docs.percona.com/percona-backup-mongodb/release-notes/2.13.0.html) strengthens backup operations with Workload Identity Federation for GCS (no long-lived service account keys), selective backups that include users and roles, and uninterrupted PITR during logical backups on external storage profiles. Together, these changes reduce security exposure and improve restore reliability for regulated and multi-storage environments. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Automated backup and failover: The Percona Kubernetes Operator for MongoDB and Percona Backup for MongoDB automate deployment, backups, and failover, while ExpertOps ensures predictable uptime and capacity planning. [Percona Backup for MongoDB 2.13.0 (2026-03-03)](https://docs.percona.com/percona-backup-mongodb/release-notes/2.13.0.html) strengthens backup operations with Workload Identity Federation for GCS (no long-lived service account keys), selective backups that include users and roles, and uninterrupted PITR during logical backups on external storage profiles. Together, these changes reduce security exposure and improve restore reliability for regulated and multi-storage environments. | |
| - Feasible disaster recovery: Percona Kubernetes Operator for MongoDB and Percona Backup for MongoDB automate deployment, backups, and restore, while ExpertOps ensures predictable uptime and capacity planning. Logical, physical, snapshot-based and incremental backups with Point-In-Time Recovery cover all needs depending on the requirements to achieve lowest Recovery Time Objective nad Recovery Point Objective. |
Collaborator
Author
There was a problem hiding this comment.
@radoslawszulgo Is the backup/failover feature not automated?
radoslawszulgo
requested changes
Jun 1, 2026
Co-authored-by: Radoslaw Szulgo <radoslaw.szulgo@percona.com>
Position Percona Server for MongoDB as the supported path for LDAP/AD when upstream MongoDB deprecates directory auth, with product-level proof on the MongoDB page and a matching security use case for field reuse. Co-authored-by: Cursor <cursoragent@cursor.com>
3 tasks
brianamarie
added
the
Inbound
Sync PR #143 with current main and resolve conflicts in MongoDB product messaging and the security pillar page. MongoDB messaging (products/mongodb/messaging.md): - Keep main FIPS 140-3 and source-available encryption copy; fold PR LDAP continuity (deprecation context, long-term LDAP/AD, userToDNMapping) into SSC. - Reorganize reliability: operational complexity vs automated backup and failover (evergreen PBM/Operator capabilities, no PBM 2.13.0 release pinning per review). - Move platform migration to Optimized TCO; keep major-version upgrade under Performance with expert-led cutover framing. - Remove forward-looking Vector Search / mongot copy. Security pillar: keep main sovereignty framework and use cases; add enterprise directory auth continuity use case from the PR branch. Co-authored-by: Cursor <cursoragent@cursor.com>
brianamarie
commented
Jun 4, 2026
| - Lower migration effort and risk: [Percona ClusterSync for MongoDB](https://docs.percona.com/percona-clustersync-for-mongodb/) supports near-zero-downtime migration and controlled cutover to self-managed Percona Server for MongoDB or MongoDB Community with cluster-to-cluster synchronization. Expert Support and ExpertOps help teams plan cutover timing and validation per [supported deployments](https://docs.percona.com/percona-clustersync-for-mongodb/system-requirements.html). Document-level parallel replication and an async bulk-write pipeline handle up to 30,000 operations per second, depending on the cluster architecture and document size (e.g., 5 KB vs. 100 KB payloads). These improvements ensure shorter migration windows and reduce replication lag before cutover. | ||
| - Lower major-version upgrade risk: [Percona ClusterSync for MongoDB](https://docs.percona.com/percona-clustersync-for-mongodb/) supports cross-major-version replication and controlled cutover from [Percona ClusterSync for MongoDB 0.9.0 (2026-06-01)](https://docs.percona.com/percona-clustersync-for-mongodb/release-notes/0.9.0.html) across [supported upgrade paths](https://docs.percona.com/percona-clustersync-for-mongodb/system-requirements.html), including 6.x to 7.x, 6.x to 8.x, and 7.x to 8.x. Teams with an end-of-life 6.0.17+ version can upgrade to an actively supported release with reduced risk compared to a traditional upgrade. | ||
| - Operational complexity: Manual HA/DR operations create business risk as well as labor cost: slow or failed failovers, outages during scale-out or node replacement, and replication catch-up lag can interrupt revenue-critical workloads while consuming scarce DBA time. Percona Server for MongoDB includes in-memory storage engine support and file copy-based initial sync to shorten recovery and lighten day-two work so topology changes stay reliable. | ||
| - Automated backup and failover: The Percona Operator for MongoDB and [Percona Backup for MongoDB](https://docs.percona.com/percona-backup-mongodb/) automate deployment, backup schedules, and restore on infrastructure you control; ExpertOps supports predictable uptime and capacity planning. Percona Backup for MongoDB supports logical, physical, snapshot-based, and incremental backups with point-in-time recovery, so teams can align backup design with recovery time and recovery point objectives. The Operator handles HA and failover in Kubernetes, which cuts manual runbooks and strengthens restore confidence in regulated and multi-storage environments. |
Collaborator
Author
There was a problem hiding this comment.
@radoslawszulgo the auth bit is now removed from the backup and failover section (most recent commit also re-organized these a bit, there was a merge conflict)
brianamarie
commented
Jun 4, 2026
| **Adaptability for Emerging Workloads** | ||
|
|
||
| - Multi-environment operations: The Percona Operator for MongoDB automates provisioning and scaling across Kubernetes and multi-cloud environments, while PMM provides cross-cluster observability and performance analytics. Minsait migrated tier-one telecom workloads to Percona Server for MongoDB on Google Cloud using the Percona Operator, achieving significant cost savings and operational freedom across Kubernetes environments. [Percona Operator for MongoDB 1.22.0 (2026-02-25)](https://docs.percona.com/percona-operator-for-mongodb/RN/Kubernetes-Operator-for-PSMONGODB-RN1.22.0.html) adds automatic PVC resizing and restore remapping for clusters with different replica set names, plus native MinIO backup support for S3-compatible storage. These features reduce disk-capacity incidents, improve restore reliability across environment changes, and stabilize backup connectivity for common object stores. See the [Operator release index](https://docs.percona.com/percona-operator-for-mongodb/RN/index.html). | ||
| - Vector and full-text search readiness: Percona is preparing a MongoDB Vector Search stack based on upstream `mongot`, focused on packaging, orchestration, and observability for self-managed deployments (aligned to MongoDB 9.0 GA timing). |
Collaborator
Author
There was a problem hiding this comment.
Future looking, shouldn't have been merged in the first place so fixing now. @radoslawszulgo friendly reminder to please open an issue with future-looking info 😊
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
offerings/solution-bundles/messaging.md: Migration Planning Jumpstart, Full Migration, and Migration Modernization.offerings/solution-bundles/README.mdso all bundles follow the same pattern (buyer moment, outcomes, inclusions in one table; scope and PS module detail stays in commercial systems such as the PS Scope Book).Test plan
products/mongodb/messaging.mdif we want stronger cross-propagation (not included in this PR).Made with Cursor
Includes consolidated changes from #132