Lead MySQL messaging with in-place MySQL Enterprise replacement positioning#180
Lead MySQL messaging with in-place MySQL Enterprise replacement positioning#180thefactremains wants to merge 4 commits into
Conversation
…ioning Update products/mysql/messaging.md to position Percona Server for MySQL as an in-place replacement for MySQL Enterprise Edition. Add a new lead sub-theme "In-place replacement for MySQL Enterprise Edition" as the first item under Customer Challenges and Value Alignment, covering drop-in binary compatibility, open source equivalents for paid Enterprise capabilities, and capabilities beyond Enterprise Edition. All claims cite public docs.percona.com pages inline. Present-tense capability framing, engine scope inline, no competitive intelligence or internal talk tracks. markdownlint-cli2 passes with 0 errors. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Messaging Smart Suggestions
Only auto-apply suggestions at high confidence with reviewer approval. Triggered by |
Messaging Impact Check
licensing-or-open-source-claims (BLOCKING)License and open source positioning changes are cross-cutting. 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 |
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 |
|
Hello @thefactremains! Thank you so much for opening this PR. I've tried not to change any of the meaning or context, but have made some changes for information architecture and flow. Please feel free to edit again, make suggested changes, comments, whatever makes sense - and I'm happy to jump on a call if there's anything to talk through. 😊 I know I'd been hesitant about the 'drop in' claim, and I'm happy we can lean into it fully. After merging this (and likely #181 but this is headline) I'll:
|
…e to pillars. Reorganize products/mysql/messaging.md to lead with in-place MySQL Enterprise replacement: Enterprise parity and Beyond Enterprise capability map, with value-linked detail in TCO, Performance, Security, and Adaptability. Add drop-in migration framing, MariaDB Galera context for PXC positioning, PXC versus Group Replication as complementary HA paths, and FIPS in all supported PS builds from 8.4.7 plus PXC (standard builds; host OpenSSL required). Add short cross-references in cost-optimization and security-sovereignty-compliance value pillars. Comparison tables remain a follow-on track. Needs SME pass: confirm FIPS 8.4.7 and PXC FIPS scope before merge. Co-authored-by: Cursor <cursoragent@cursor.com>
|
(fyi - about to make a few more tweaks for architecture consistency, will push in a minute) |
Move in-place Enterprise replacement spine and Enterprise parity / Beyond Enterprise capability map under Optimized TCO as the lead bullets, matching the Customer Challenges layout used by other product messaging files. Feature detail remains in Performance, Security, and Adaptability; sales enablement unchanged. Co-authored-by: Cursor <cursoragent@cursor.com>
thefactremains
left a comment
thefactremains
left a comment
There was a problem hiding this comment.
Review: comment only. Verified against gh pr diff 180 (merge base 08855202), 3 files: products/mysql/messaging.md, use-cases-value-pillars/cost-optimization.md, use-cases-value-pillars/security-sovereignty-compliance.md. Strong update overall. Three items before merge.
-
(Should-fix before merge) In
products/mysql/messaging.md, the "High availability without vendor roadmap dependency" bullet opens with a competitive talk track: "After MariaDB nearly removed Galera from Community Server in 2026 (and walked back only after community outcry)...". Perreference/content-governance.md, competitive intelligence and internal talk tracks belong in private systems, not this public CC BY 4.0 repo, and perreference/brand-voice.md, canonical copy should not disparage a competitor. Suggest neutral, customer-facing wording, for example: "Percona XtraDB Cluster runs Percona's own open source Galera fork for synchronous multi-primary HA with split-brain prevention and WAN-friendly weighted quorum, a vendor-independent HA home that does not depend on another vendor's roadmap." Keep the Group Replication sentence as-is. -
(Accuracy) FIPS version. The copy states FIPS-capable binaries ship as of "8.4.7" in four added lines: the Enterprise parity bullet, the "FIPS for regulated environments" bullet, and the FIPS conversation starter (all in
products/mysql/messaging.md), plus thesecurity-sovereignty-compliance.mdcross-reference. The authoritativefips.mddoc and this PR's own description say 8.4.0-5, and the line this PR replaces also read 8.4.0-5. Recommend correcting 8.4.7 to 8.4.0-5, or confirming the exact version with a product SME before merge. The PR description already lists this as needing an SME pass. -
(Minor) The new link
https://www.percona.com/compare-mysql-mongodb-postgresql-mariadbresolves (HTTP 200). It replaced the previous docs.percona.com feature-comparison URL, so please confirm this marketing comparison page is the intended "feature comparison" target rather than a docs feature-comparison page.
|
Follow-up on item 3 (feature comparison link): the docs page that substantiates the Enterprise-parity and "95 vs 65" claims is Percona Server for MySQL feature comparison. It is a Percona Server vs MySQL (Community) feature table and is the direct source for several specifics in this PR (INFORMATION_SCHEMA 95 vs 65, MyRocks, per-object counters, binary log and temp file encryption, PAM and HashiCorp Vault keyring marked Enterprise-only in MySQL). The currently linked |
Correct FIPS version to 8.4.0-5, neutralize the PXC HA bullet, and cite the docs PS vs MySQL feature comparison for Enterprise feature claims. Refine cost and security pillar copy: fold scoped in-place Enterprise language into licensing, split SOSoC encryption from audit/access with cross-engine outcome framing. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Thank you @thefactremains - please take a peek at the newest changes when you get a chance |
2 participants
Summary
Updates the canonical MySQL product messaging in
products/mysql/messaging.mdto lead with Percona Server for MySQL as an in-place replacement for MySQL Enterprise Edition.This PR makes one change: it adds a new lead sub-theme, "In-place replacement for MySQL Enterprise Edition," as the first item under Customer Challenges and Value Alignment - MySQL (before Optimized TCO), with three value-linked bullets:
Rationale
Moves the most defensible competitive frame (in-place Enterprise Edition replacement) to the top of the page rather than leaving it implicit inside TCO. All claims are present tense, with engine scope inline and public docs.percona.com citations anchored at each claim.
New-file decision gate (reference/content-governance.md)
products/mysql/messaging.md(the canonical MySQL product file).Propagation follow-ups
Verification
npx -y markdownlint-cli2@0.22.1 "products/mysql/messaging.md"passes with 0 errors.Base branch
Based on
main. PR #172 (ingest/pr-14-mysql-tracker-deltas) is already merged intomain(merge commit 591b1d5), so this branch already includes that content and has no ordering dependency.Needs SME pass before merge
The Enterprise Edition parity and superset claims, and the FIPS-capable standard builds from 8.4.0-5 version detail, need a product-SME accuracy pass before merge.