Skip to content

Add Enterprise MySQL Modernization Bundle to solution bundles matrix#218

Open
brianamarie wants to merge 1 commit into
mainfrom
offerings/enterprise-mysql-modernization-bundle
Open

Add Enterprise MySQL Modernization Bundle to solution bundles matrix#218
brianamarie wants to merge 1 commit into
mainfrom
offerings/enterprise-mysql-modernization-bundle

Conversation

@brianamarie

Copy link
Copy Markdown
Collaborator

Summary

  • Adds Enterprise MySQL Modernization Bundle as a new row in offerings/solution-bundles/messaging.md.
  • Positions the bundle for enterprise DBAs facing MySQL 8.0 EOL, Oracle/RDS cost pressure, performance or HA limits, or leadership questions about moving to PostgreSQL.
  • Emphasizes workload-led guidance and execution on MySQL first, with Extended Lifecycle Support (ELS) as a bridge, Support through transition on current and target stacks, and MySQL to PostgreSQL migration only when assessment scopes it.

Context

This is matrix-level canonical messaging only. Commercial scope (pricing, SKU, server limits, Support tier) still needs Services sign-off before seller-ready use.

Downstream follow-up

  • Marketing / web: After merge, notify the marketing team to add or update the solution bundles webpage with this bundle (LP tile copy, bundle description, and CTA still to be drafted from the matrix row).
  • Sales enablement: Create or update a solution bundle slide for the Enterprise MySQL Modernization Bundle for field and partner use.

Made with Cursor

@github-actions

Copy link
Copy Markdown
Contributor

New File Governance Check

No added markdown files detected.

Doc Coverage Check

No new markdown docs detected.

Manual waiver commands (maintainers)

  • /governance-ok all or /governance-all
  • /governance-ok new-file, /governance-ok doc-coverage
  • /governance-reset all or /governance-reset with the same token

Waiver JSON is stored in a hidden PR comment (messaging-governance-waiver-data:v1), same pattern as Impact Check.


Triggered by pull_request. Workflow content-governance-checks.yml. Docs: AUTOMATION.md, automation/README.md.

@github-actions

Copy link
Copy Markdown
Contributor

Messaging Smart Suggestions

File Why impacted Claim Confidence
offerings/expert-support/messaging.md Offering naming updates should stay aligned across offering pages. cost 0.95
offerings/expertops/messaging.md Offering naming updates should stay aligned across offering pages. cost 0.95
offerings/expert-consulting/messaging.md Offering naming updates should stay aligned across offering pages. cost 0.95
reference/canonical-naming.md Offering naming updates should stay aligned across offering pages. cost 0.95
framework/core-positioning.md Offering naming updates should stay aligned across offering pages. cost 0.95

Only auto-apply suggestions at high confidence with reviewer approval.


Triggered by pull_request. Workflow smart-suggestions.yml. Docs: AUTOMATION.md, automation/README.md.

@github-actions

Copy link
Copy Markdown
Contributor

Messaging Impact Check

  • Changed files: 1

offering-name-or-tier-change (WARN)

Offering naming updates should stay aligned across offering pages.

Required review files:

  • offerings/expert-support/messaging.md
  • offerings/expertops/messaging.md
  • offerings/expert-consulting/messaging.md
  • reference/canonical-naming.md
  • framework/core-positioning.md

Suggested additional scan:

  • products/**/messaging.md
  • use-cases-value-pillars/*.md

Manual waiver commands (maintainers):

  • /impact-ok all (optional same-line note after all is ignored)
  • /impact-all (same as /impact-ok all)
  • /impact-ok <exact missing path>
  • /impact-reset all
  • /impact-reset <exact missing path>

Waiver state is stored in <!-- messaging-impact-waiver-data:v1 -->.


Triggered by pull_request. Workflow impact-check.yml. Docs: AUTOMATION.md, automation/README.md.

| **QuickStart Bundle:** for new customers validating Percona or quickly stabilizing a smaller deployment | Rapid environment stabilization, baseline health and readiness, faster time-to-value with Percona | Targeted health check or tuning (Consulting), 3 months of Advanced Support, limited to one technology and ≤10 servers |
| **AI Readiness Bundle:** for teams adopting vector search or preparing PostgreSQL for AI-driven applications | PostgreSQL readiness for vector search and AI workloads, better observability, indexing, and concurrency | Setup and tuning of pgvector, optional evaluation of pgvectorscale, pg_stat_kcache, and pg_wait_sampling based on version and packaging compatibility, plus query pattern optimization, observability, and performance enhancements |
| **Financial Peak Readiness Bundle:** (working name; commercial title may differ) for financial services teams preparing database environments for tax season, quarter close, and financial audit windows when reporting load and change risk run high | Readiness before load spikes, clearer backup and restore expectations for critical dates, and migration or upgrade alignment with freeze windows | Performance and workload readiness (Consulting), backup and restore readiness (Consulting), migration and change-freeze preparation (Consulting) across MySQL, PostgreSQL, MongoDB-compatible environments, MariaDB Community, Redis, and Valkey; optional add-ons: Peak Season Resident (Consulting), Advanced Support or Premium Support |
| **Enterprise MySQL Modernization Bundle:** for enterprise DBAs facing MySQL 8.0 EOL, Oracle licensing or RDS extended support cost, performance or HA limits, or leadership asking whether to move to PostgreSQL, who need workload-led guidance and execution on MySQL first | Written stay-or-move recommendation with executive summary; hardened MySQL stack (upgrade, tuning, HA, MySQL with Valkey where needed); Extended Lifecycle Support (ELS) as a bridge while the upgrade plan executes; Support on current and target stacks through transition; MySQL to PostgreSQL migration only when assessment scopes it | Estate assessment and written recommendation (Consulting); MySQL hardening and upgrades (Consulting); Extended Lifecycle Support (ELS) where needed; MySQL to PostgreSQL migration when scoped (Consulting); 12 months Advanced Support through transition; optional Percona ExpertOps or Technical Account Manager after go-live |

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thefactremains and @andrey-glazkov , what do you think?

@andrey-glazkov I know we have some details to work out for the packaging/pricng and enablement, but wanted to put this together to give us a place to start.

@brianamarie brianamarie added Content & messaging Canonical copy, products, use cases, case studies, and narrative. Needs: product or GTM Product, marketing, or GTM should confirm scope, naming, or positioning. Area: MySQL MySQL ecosystem messaging (products/mysql/ and MySQL-scoped operator lines). labels Jun 30, 2026
Document workload-led MySQL assessment and hardening with ELS, optional PostgreSQL migration, and Support through transition for enterprise DBA buyer moments.

Co-authored-by: Cursor <cursoragent@cursor.com>
@brianamarie
brianamarie force-pushed the offerings/enterprise-mysql-modernization-bundle branch from 507d925 to 8a439ec Compare June 30, 2026 11:27

@thefactremains thefactremains left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@brianamarie brianamarie added the MISSING TIMELINE No concrete target date, release gate, or explicit no-hard-date decision in the body. label Jul 7, 2026
@brianamarie brianamarie added the Roadmap: soon High confidence next; right after or alongside launch prep. label Jul 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: MySQL MySQL ecosystem messaging (products/mysql/ and MySQL-scoped operator lines). Content & messaging Canonical copy, products, use cases, case studies, and narrative. MISSING TIMELINE No concrete target date, release gate, or explicit no-hard-date decision in the body. Needs: product or GTM Product, marketing, or GTM should confirm scope, naming, or positioning. Roadmap: soon High confidence next; right after or alongside launch prep.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants