Skip to content

Split Valkey/Redis into key/value parent with asymmetric siblings#245

Open
brianamarie wants to merge 14 commits into
mainfrom
split-valkey-redis-messaging
Open

Split Valkey/Redis into key/value parent with asymmetric siblings#245
brianamarie wants to merge 14 commits into
mainfrom
split-valkey-redis-messaging

Conversation

@brianamarie

@brianamarie brianamarie commented Jul 21, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Replace the combined products/valkey-redis module with products/key-value: shared parent plus asymmetric Valkey and Redis children (KvRocks/Proxy stubs only), per @stockholmux
  • Valkey leads on memory/TCO, Linux Foundation governance, traditional workloads, HA/production readiness, and honest gaps (Search/JSON, geo, 7.2.4 migration gate). Redis keeps stay-on-Redis as first-class and an evaluate, validate, migrate path to Valkey.
  • Port useful fact-sheet guidance from Integrate Valkey/Redis fact-sheet guidance into product messaging #186 (platform/SRE buyer, memory-driven spend, cache as operational infrastructure, primary DB offload, public resources) into the split and matching value-pillar use cases, without restoring the combined page.

Considerations

  • Repitition: is it creating a maintenance headache, or is it serving the purpose of how audiences use these pages? (whereas nesting it in an umbrella level could make it cleaner on one hand, but not readable/functional?)

brianamarie and others added 2 commits July 21, 2026 12:36
Replace the combined products/valkey-redis module with products/key-value
so shared workloads stay one family while Valkey leads on memory,
governance, and HA, and Redis keeps stay-or-migrate transition messaging
for Kyle review.

Co-authored-by: Cursor <cursoragent@cursor.com>
Bring PR #186 buyer, memory, and cache-tier positioning into the
asymmetric parent/Valkey/Redis modules and matching value-pillar use
cases, without restoring the combined page.

Co-authored-by: Cursor <cursoragent@cursor.com>
@brianamarie
brianamarie requested a review from Cinneely as a code owner July 21, 2026 11:52
@github-actions

Copy link
Copy Markdown
Contributor

New File Governance Check

  • Added markdown files: 3
    • products/key-value/messaging.md
    • products/key-value/redis/messaging.md
    • products/key-value/valkey/messaging.md

Missing or insufficient required sections:

  • Existing files reviewed first

  • Exact gap not covered by existing files

  • Why this must be a new canonical file

  • Owner and maintenance plan

  • Decomposition and propagation plan

Copy and paste the scaffold below into your PR body, then replace placeholders with specific details:

## New markdown file gate (required only when adding new `.md` files)

### Existing files reviewed first

- List the specific files you reviewed and what each one does.

### Exact gap not covered by existing files

- Explain what is still missing after reviewing existing canonical files.

### Why this must be a new canonical file

- State why editing an existing file is not sufficient.

### Owner and maintenance plan

- Name the owner and how this file will stay accurate over time.

### Decomposition and propagation plan

- List related files and downstream assets that may need updates.

Doc Coverage Check

  • New markdown docs: 3
  • Navigation docs scanned: 12
    • products/key-value/messaging.md (missing navigation link)
    • products/key-value/redis/messaging.md (missing navigation link)
    • products/key-value/valkey/messaging.md (missing navigation link)

Docs missing discoverability links:

  • products/key-value/messaging.md
  • products/key-value/redis/messaging.md
  • products/key-value/valkey/messaging.md

Add at least one markdown link to each missing file from README.md or CONTRIBUTING.md.

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 Impact Check

  • Changed files: 17

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

License and open source positioning changes are cross-cutting.

Required review files:

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

Suggested additional scan:

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

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

product-messaging-module-touch (WARN)

Product messaging modules often need checks against company framing and shared pillars or offerings.

Required review files:

  • framework/core-positioning.md
  • framework/why-percona.md

Suggested additional scan:

  • use-cases-value-pillars/*.md
  • offerings/*.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.

@github-actions

Copy link
Copy Markdown
Contributor

Messaging Smart Suggestions

File Why impacted Claim Confidence
reference/canonical-naming.md License and open source positioning changes are cross-cutting. cost 0.65
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/messaging.md License and open source positioning changes are cross-cutting. cost 0.95
offerings/expertops/messaging.md License and open source positioning changes are cross-cutting. cost 0.65
offerings/expert-consulting/messaging.md License and open source positioning changes are cross-cutting. cost 0.95
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.65
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.65
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.

Comment thread products/key-value/redis/messaging.md Outdated
Comment thread products/key-value/redis/messaging.md Outdated
Comment thread products/key-value/redis/messaging.md Outdated
@github-actions

github-actions Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Markdown hygiene auto-fix

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

Fixed files:

  • products/key-value/messaging.md

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

@brianamarie
brianamarie requested a review from stockholmux July 23, 2026 10:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant