055-design-parallel-change

仓库创建 2025年2月9日最近提交 3 天前SkillHot 收录 16 小时前

▸ 精选理由

适合复杂迁移场景，帮助降低中断与兼容性风险。

这个 Skill 做什么

指导 Java 企业系统中数据库并行变更的扩展-迁移-收缩序列化方案。

为 Java 企业系统设计“并行变更”（Parallel Change）的展开—迁移—收缩三步流程，处理列重命名、大表回填、枚举/状态迁移、索引或唯一性调整等复杂场景。在判断是否需要兼容窗口或决定迁移序列化策略前使用，比直接写 Flyway migration 更先把风险和回滚路径想清楚。特点是交互式引导、面向线上零停机和兼容性安全的部署方案。

▸ 展开 SKILL.md 英文原文

Use when a database schema or data-meaning change needs Parallel Change, including expand, migrate, and contract sequencing for column renames, type or data reinterpretation, large-table backfills, relationship-table changes, enum/status transitions, timezone/default changes, and index or uniqueness changes. This should trigger before framework-specific Flyway implementation guidance when deciding whether a migration needs a compatibility window or whether a simpler migration is sufficient. Part of Plinth Toolkit

开发编程数据迁移并行变更数据库通用

423

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/jabrena/plinth/main/skills/055-design-parallel-change/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/jabrena/plinth/main/skills/055-design-parallel-change/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Parallel Change Design

Guide Java Enterprise developers through Parallel Change for database migration scenarios. **This is an interactive SKILL**.

**What is covered in this Skill?**

- Deciding whether a database migration needs a compatibility window
- Sequencing database changes as expand, migrate, and contract deployable steps
- Preserving old and new application versions during rollout and rollback windows
- Handling column renames, type or data reinterpretation, large backfills, relationship-table changes, and index or uniqueness changes
- Explaining tradeoffs such as temporary dual paths, extra migrations, verification effort, and delayed cleanup
- Routing framework-specific imple

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有