Add Optimized TCO legacy migration use case (heterogeneous paths) by brianamarie · Pull Request #177 · percona/percona-messaging

brianamarie · 2026-06-03T10:31:14Z

Summary

Adds Legacy and proprietary database migration to open source under Optimized TCO with three sub-bullets: generic commercial sources (no named competitors), homogeneous and heterogeneous targets, and engagement (Percona-led scoping; specialized multi-source, multi-target migration tooling for heterogeneous paths after assessment).
Aligns Problem / Solution migration lines and tightens Expert Consulting to a single Common scenarios bullet (no extra subsection).
Updates PostgreSQL Optimized TCO legacy-exit copy to use generic proprietary/legacy language.

Out of scope / gating

No NOTICES.md changes.
No named competitors, partners, or products (HexaCluster, HexaRocket, reseller terms, or launch-announcement posture).
No solution-bundle SKU packaging.

Made with Cursor

Put migration detail in cost-optimization use cases (generic commercial sources, homogeneous/heterogeneous targets, Percona-led engagement with specialized tooling). Keep Expert Consulting to one common scenario bullet and align PostgreSQL TCO copy without naming competitors or partners. Co-authored-by: Cursor <cursoragent@cursor.com>

github-actions · 2026-06-03T10:31:28Z

github-actions · 2026-06-03T10:31:29Z

New File Governance Check

No added markdown files detected.

Doc Coverage Check

No new markdown docs detected.

Duplicate Detector

Changed markdown docs: 4

No significant overlap detected.

Manual waiver commands (maintainers)

/governance-ok all or /governance-all
/governance-ok new-file, /governance-ok doc-coverage, /governance-ok duplicate
/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 · 2026-06-03T10:31:32Z

Messaging Smart Suggestions

File	Why impacted	Claim	Confidence
`use-cases-value-pillars/cost-optimization.md`	PostgreSQL cost/TCO claims usually impact shared value proof messaging.	cost	0.65
`framework/core-positioning.md`	PostgreSQL cost/TCO claims usually impact shared value proof messaging.	cost	0.95
`products/postgresql/messaging.md`	PostgreSQL cost/TCO claims usually impact shared value proof messaging.	cost	0.65
`reference/canonical-naming.md`	License and open source positioning changes are cross-cutting.	cost	0.95
`reference/banned-terms.md`	License and open source positioning changes are cross-cutting.	cost	0.95
`framework/core-positioning.md`	License and open source positioning changes are cross-cutting.	cost	0.95
`framework/why-percona.md`	License and open source positioning changes are cross-cutting.	cost	0.95
`offerings/expert-support.md`	License and open source positioning changes are cross-cutting.	cost	0.95
`offerings/expertops.md`	License and open source positioning changes are cross-cutting.	cost	0.95
`offerings/expert-consulting.md`	License and open source positioning changes are cross-cutting.	cost	0.65
`offerings/expert-support.md`	Offering naming updates should stay aligned across offering pages.	cost	0.95
`offerings/expertops.md`	Offering naming updates should stay aligned across offering pages.	cost	0.95
`offerings/expert-consulting.md`	Offering naming updates should stay aligned across offering pages.	cost	0.65
`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
`framework/core-positioning.md`	Product messaging modules often need checks against company framing and shared pillars or offerings.	cost	0.95
`framework/why-percona.md`	Product messaging modules often need checks against company framing and shared pillars or offerings.	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.}

janwieremjewicz

Other than the 3 comments it looks good to me. None of these seems to be a blocker TBH, more stylistic and ensuring that the narrowing of scope is on purpose.

brianamarie · 2026-06-03T14:45:38Z


+- **Legacy and proprietary database migration to open source:** Renewal pressure on proprietary or legacy commercial databases drives moves to open source without new lock-in.
+  - **Sources:** Commercial proprietary RDBMS, commercial MySQL and MariaDB providers, other commercial PostgreSQL distributions, and other legacy commercial engines when assessment confirms a path.
+  - **Homogeneous and heterogeneous targets:** Open source PostgreSQL, MySQL, or MariaDB (Community) per Percona's MariaDB scope. **Homogeneous** paths stay within one engine family (e.g. on-prem to cloud on the same stack). **Heterogeneous** paths move legacy or proprietary engines to those targets. Proprietary-to-PostgreSQL paths are common; source-target pairs vary by estate.


@brianamarie todo add in detail with Hexarocket and Hexacluster as enablers of this capability

github-actions · 2026-06-04T10:05:16Z

Markdown hygiene auto-fix

Applied safe markdown hygiene fixes and pushed one bot commit to this PR branch.

Fixed files:

offerings/expert-consulting.md

_{Triggered by pull_request. Workflow markdown-hygiene-autofix.yml. Docs: AUTOMATION.md, automation/README.md.}

brianamarie · 2026-06-04T10:05:16Z

 - Open source without compromise: The Percona Distribution for PostgreSQL consolidates trusted community components into one enterprise-validated package, eliminating the cost and complexity of proprietary add-ons. Türk Telekom eliminated licensing costs, cut query times substantially, and boosted customer satisfaction by delivering high availability and resilience across critical services with Percona Distribution for PostgreSQL.
 - Migration clarity when PostgreSQL licensing or managed-service roadmaps change: Vendor bundles and subscription models evolve on timelines teams do not control. Percona publishes positioning on portable PostgreSQL software versus proprietary distributions and managed PostgreSQL stacks ([Percona Software for PostgreSQL](https://www.percona.com/postgresql/software)), which helps organizations compare options on cleared public materials and plan moves without proprietary APIs that trap operational state.
- Legacy RDBMS exit to PostgreSQL for TCO: Teams exiting proprietary or legacy RDBMS footprints can reduce license and support spend by landing on Percona Distribution for PostgreSQL with assessment-led migration through [Percona Expert Consulting and Services](https://www.percona.com/services/consulting). Scope and source-to-target patterns are confirmed during assessment.
+- Legacy RDBMS exit to PostgreSQL for TCO: From proprietary and legacy commercial databases, teams cut license spend on Percona Distribution for PostgreSQL via assessment-led [Percona Expert Consulting and Services](https://www.percona.com/services/consulting). Scope confirmed at assessment.


Suggested change

- Legacy RDBMS exit to PostgreSQL for TCO: From proprietary and legacy commercial databases, teams cut license spend on Percona Distribution for PostgreSQL via assessment-led [Percona Expert Consulting and Services](https://www.percona.com/services/consulting). Scope confirmed at assessment.

- Legacy database to PostgreSQL: From proprietary and legacy commercial databases, teams cut license spend on Percona Distribution for PostgreSQL via assessment-led [Percona Expert Consulting and Services](https://www.percona.com/services/consulting). Scope confirmed at assessment.

…scope. Lou approved naming HexaCluster and HexaRocket once in the Optimized TCO engagement model, with heterogeneous proprietary-to-open-source language elsewhere. Covers sources, targets, and Oracle to PostgreSQL across the supported stack including MongoDB-compatible and Valkey paths. Co-authored-by: Cursor <cursoragent@cursor.com>

thefactremains

Review: comment only. Verified against gh pr diff 177 (4 files: use-cases-value-pillars/cost-optimization.md, offerings/expert-consulting.md, products/postgresql/messaging.md, use-cases-value-pillars/README.md). The TCO legacy-migration content reads well. Two items to consider before merge.

(Nit, likely CI) The additions use "proprietary-to-open-source" in several places (offerings/expert-consulting.md, products/postgresql/messaging.md, and use-cases-value-pillars/cost-optimization.md). Repo rule: "open source" is never hyphenated, and the Vale OpenSourceHyphen rule will likely report it. Suggest rewording, for example "from proprietary engines to open source."
(Should-fix) The new legacy-migration use case in use-cases-value-pillars/cost-optimization.md names HexaCluster and HexaRocket plus third-party marks (Oracle, SQL Server, EDB, MongoDB, Sybase, DB2, SAP HANA, Redis), but NOTICES.md is not updated. NOTICES currently lists Oracle, MySQL, MongoDB, and Redis, so SQL Server, EDB, Sybase, DB2, SAP HANA, HexaCluster, and HexaRocket are not attributed. The HexaCluster and HexaRocket names were added in a later commit (cd29b7f) and are listed under "Out of scope / gating" in the PR description, so the description and the copy disagree. Per reference/brand-voice.md, confirm whether NOTICES.md needs these trademarks added, record the HexaCluster and HexaRocket naming approval in the PR, and reconcile the description with the copy.

Surface schema conversion, real-time sync, and validation across cost pillar, PostgreSQL messaging, and Expert Consulting so high-intent heterogeneous paths are explicit. Co-authored-by: Cursor <cursoragent@cursor.com>

brianamarie requested review from ImTheKai and janwieremjewicz as code owners June 3, 2026 10:31

janwieremjewicz previously approved these changes Jun 3, 2026

View reviewed changes

Comment thread offerings/expert-consulting.md Outdated

Comment thread use-cases-value-pillars/cost-optimization.md Outdated

Comment thread use-cases-value-pillars/cost-optimization.md Outdated

brianamarie commented Jun 3, 2026

View reviewed changes

Apply suggestion from @brianamarie

a8042fa

brianamarie dismissed janwieremjewicz’s stale review via a8042fa June 4, 2026 10:02

brianamarie and others added 3 commits June 4, 2026 12:04

Apply suggestion from @brianamarie

ff8450f

Merge ff8450f into 591b1d5

a97bebb

chore(markdown): auto-fix hygiene

8a19745

brianamarie commented Jun 4, 2026

View reviewed changes

github-actions Bot requested a review from thefactremains as a code owner June 4, 2026 10:05

brianamarie and others added 3 commits June 4, 2026 12:05

Apply suggestion from @brianamarie

527d29a

Merge branch 'main' into feat/hexacluster-messaging-restore

35f01ff

thefactremains reviewed Jun 5, 2026

View reviewed changes

Add MySQL-to-PostgreSQL migration detail for legacy exit use case.

bb55cb1

Surface schema conversion, real-time sync, and validation across cost pillar, PostgreSQL messaging, and Expert Consulting so high-intent heterogeneous paths are explicit. Co-authored-by: Cursor <cursoragent@cursor.com>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add Optimized TCO legacy migration use case (heterogeneous paths)#177

Add Optimized TCO legacy migration use case (heterogeneous paths)#177
brianamarie wants to merge 9 commits into
mainfrom
feat/hexacluster-messaging-restore

brianamarie commented Jun 3, 2026

Uh oh!

github-actions Bot commented Jun 3, 2026

Uh oh!

github-actions Bot commented Jun 3, 2026

Uh oh!

github-actions Bot commented Jun 3, 2026

Uh oh!

janwieremjewicz left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

brianamarie Jun 3, 2026

Uh oh!

github-actions Bot commented Jun 4, 2026

Uh oh!

brianamarie Jun 4, 2026

Uh oh!

thefactremains left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	- Legacy RDBMS exit to PostgreSQL for TCO: From proprietary and legacy commercial databases, teams cut license spend on Percona Distribution for PostgreSQL via assessment-led [Percona Expert Consulting and Services](https://www.percona.com/services/consulting). Scope confirmed at assessment.
	- Legacy database to PostgreSQL: From proprietary and legacy commercial databases, teams cut license spend on Percona Distribution for PostgreSQL via assessment-led [Percona Expert Consulting and Services](https://www.percona.com/services/consulting). Scope confirmed at assessment.

Conversation

brianamarie commented Jun 3, 2026

Summary

Out of scope / gating

Uh oh!

github-actions Bot commented Jun 3, 2026

Messaging Impact Check

postgres-cost-claim (BLOCKING)

licensing-or-open-source-claims (BLOCKING)

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

product-messaging-module-touch (WARN)

Uh oh!

github-actions Bot commented Jun 3, 2026

New File Governance Check

Doc Coverage Check

Duplicate Detector

Manual waiver commands (maintainers)

Uh oh!

github-actions Bot commented Jun 3, 2026

Messaging Smart Suggestions

Uh oh!

janwieremjewicz left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

brianamarie Jun 3, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot commented Jun 4, 2026

Markdown hygiene auto-fix

Uh oh!

brianamarie Jun 4, 2026

Choose a reason for hiding this comment

Uh oh!

thefactremains left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants