docs(readme): 架构图分层配色 + Kafka+Spark 对比

[NeverENG]

• 架构图重画:subgraph 按入口/存储/投递/分布式四层分组,classDef 分层配色,主数据流一条主线贯穿(替换原来堆在一起的流程图)。
• 「定位」下新增与 Kafka+Spark 清洗链路的对比表(清洗时机 / 数据搬运 / 延迟 / 运维),诚实标注适用区间(中小规模/边缘/低延迟)与不替代大规模有状态流处理的边界。

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@NeverENG, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 53 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 31b04137-dff0-4ef6-a9f2-47e14c4aec52

📥 Commits

Reviewing files that changed from the base of the PR and between 78bc1d6 and 3860ff5.

📒 Files selected for processing (1)

• README.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/readme-diagram-compare

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🐯 BanGD 数据库内核评审

整体风险：🟢 低

变更总结：这是一个纯文档（README.md）修改的 PR，不涉及任何源代码或存储引擎逻辑。变更分三块：(1) 重画 Mermaid 架构图，把节点按「入口/存储/投递/分布式」四层用 subgraph 分组，并用 classDef 分层配色，让主数据流（上游→入口→存储→投递→sink）形成一条清晰的纵向主线，替代原先平铺堆叠、数据流与分片关系混杂的图；(2) 标题与定位文案重写（改名 BanDB Flux、强调零依赖），将「作用」拆成「功能」清单并新增「崩溃恢复/断点重续」「限流」等条目；(3) 新增「相比 Kafka + Spark 清洗链路」对比表，从清洗时机/数据搬运/延迟/运维四个维度诚实标注适用边界（中小规模/边缘/低延迟），并明确不替代大规模有状态流处理。该 PR 不触碰任何磁盘格式、并发、WAL、存储不变量，是纯可读性/可传播性层面改进。

本评审不阻塞合入；架构级建议以 Issue 形式跟踪，普通问题在下方内联列出。

未发现需要从架构层面改进的问题。

---

_{本次评审消耗 token：共 15087 tokens（输入 8330，输出 357，缓存命中 6400，缓存写入 0）｜维度 [concurrency, memory, lock, storage, performance]｜对抗式复核 3 票/条，过滤疑似误报 0 条}