Program review content template

[xuechaos]

方案评审内容模板

一、背景与问题

1. 背景信息同步*（可选，在信息已经同步后，只需要简单介绍）*

• 基本背景信息
  • 概念解释
  • 背景说明

2. 现状与问题

• 现状的描述
  • 基本状态
  • 可选信息
    • 集群的规模
    • 部署情况
• 问题说明（原因和影响范围）
• 问题分析

二、技术方案

• 可选方案&方案选型
  • 多个方案的优缺点的分析
  • 最后方案的确定的理由和分析过程
• 方案详细描述（以下为举例）
  • 算法或架构图以及描述信息
  • 是否验证，验证方法
  • 方案客户体验分析
    • API层面的体验
    • 界面的体验
    • 架构是否容易理解
    • 架构是否容易维护和运维
  • 方案的重点侧重考虑的问题
  • 涉及到相关问题考虑（以下为举例）
    • 可用性
    • 扩展性
    • 易用性
    • 规模大会不会引发问题

设计原则
分片算法制定
分片算法验证
升级分片的考虑&高可用的考虑&规模大的考虑
使用的边界&架构的优势&风险分析
详细架构图

三、具体发布计划

• 发布时间计划
• 目前进度
• 验证计划

自验证策略
发布策略
发布步骤
可能的风险

[nacos-bot]

Hi @xuechaos, we detect non-English characters in the issue. This comment is an auto translation from @nacos-bot to help other users to understand this issue.
We encourage you to describe your issue in English which is more friendly to other users.

Program review content template

#计划评论Content Template

I. Background and issues

1. Background information synchronization* (optional, after the information has been synchronized, only need to be briefly introduced)*

• Basic background information
• Concept explanation
• Background description

2. Status and problems

• Description of the status quo
• Basic status
• Optional information
• The size of the cluster
• Deployment situation
• Description of the problem (reason and scope of influence)
• problem analysis

II. Technical solution

• Optional & Solution Selection
• Analysis of the advantages and disadvantages of multiple programs
• Reasons for the final plan and the analysis process
• Detailed description of the program (the following is an example)
• Algorithm or architecture diagram and description information
• Whether to verify, verification method
• Solution customer experience analysis
• API level experience
• Interface experience
• Is the architecture easy to understand?
• Is the architecture easy to maintain and operate?
• The focus of the program focuses on issues
• Involved in related issues (the following is an example)
• Availability
• Scalability
• Ease of use
• Scale conference will not cause problems

Design Principles
Fragmentation algorithm
Fragmentation algorithm verification
Upgrade sharding considerations & high availability considerations & large scale considerations
Advantages & Risk Analysis of Boundary & Architecture Used
Detailed architecture diagram

III. Specific release plan

• Release time plan
• Current progress
• Verification plan

Self-validation strategy
Release strategy
Release step
Possible risk

[stale]

Thanks for your feedback and contribution. But the issue/pull request has not had recent activity more than 180 days. This issue/pull request will be closed if no further activity occurs 7 days later.
We may solve this issue in new version. So can you upgrade to newest version and retry?
If there are still issues or want to contribute again. Please create new issue or pull request again.