https://peter-notes.com/categories/%E8%BB%9F%E9%AB%94%E6%9E%B6%E6%A7%8B/Recent content in 軟體架構 on Peter.H's Full-Stack GAMEhttps://peter-notes.com/images/og-image.jpghttps://peter-notes.com/images/og-image.jpgHugozh-twFri, 22 May 2026 00:00:00 +0000https://peter-notes.com/posts/strategic-cutover-docs-with-tactical-headless-orchestrators/Fri, 22 May 2026 00:00:00 +0000https://peter-notes.com/posts/strategic-cutover-docs-with-tactical-headless-orchestrators/Cutover doc 解決跨 session、跨天的戰略協調，但單一高階任務底下的執行還是手動驅動。把社群上流行的 orchestrator + claude headless pattern 接到 cutover doc 之下，組成戰略層（長期決策記憶）+ 戰術層（單 loop 內自動化執行）的兩層記憶體階層。https://peter-notes.com/posts/async-multi-agent-coordination-via-markdown-control-plane/Fri, 22 May 2026 00:00:00 +0000https://peter-notes.com/posts/async-multi-agent-coordination-via-markdown-control-plane/從一個跨三個 repo、橫跨十多個 AI session 的 schema migration 中萃取出的 8 個 control-plane document 設計模式：append-only audit、cross-session message queue、pickup prompt engineering，讓非同步 AI agent 協作成為可工程化的問題。https://peter-notes.com/posts/schema-pivot-dual-write-migration/Fri, 15 May 2026 00:00:00 +0000https://peter-notes.com/posts/schema-pivot-dual-write-migration/外部系統匯入的 customers 表跑了三年,現在想換成 SaaS 自己的 users 表為主。Stop-the-world 風險太高,dual-write 過渡是唯一可行解。本文拆解 3 階段 migration、partial cut-over、DISTINCT ON 去重、永久共存政策的設計考量與實戰踩坑。https://peter-notes.com/posts/authorization-degraded-mode-design/Tue, 20 Jan 2026 00:00:00 +0000https://peter-notes.com/posts/authorization-degraded-mode-design/當 RBAC（Role-Based Access Control）的 Link Table 資料不正確時，系統該全站拒絕、繼續相信 cache、還是進入 degraded mode？這篇文章分享我的設計決策與實作方式https://peter-notes.com/posts/flutter-vs-vue-debugging-complexity/Sun, 04 Jan 2026 00:00:00 +0000https://peter-notes.com/posts/flutter-vs-vue-debugging-complexity/同樣是「關於我們」頁面的顯示邏輯，Vue 改了十幾個 commit 都很順利，Flutter 卻卡了很久。本文從 Debug 實戰出發，延伸到 Domain Model 的防禦能力、Clean Architecture 的責任邊界、扁平架構的取捨、BFF 的可靠性價值，最後探討交接代碼的信任陷阱。https://peter-notes.com/posts/why-choose-strapi-cms-2024/Tue, 23 Dec 2025 00:00:00 +0000https://peter-notes.com/posts/why-choose-strapi-cms-2024/深入分析 2024 年 6 月為公司進行 CMS 技術選型的決策過程，從 Headless CMS 架構、自動化 API 生成、到實際人力成本節省的完整考量https://peter-notes.com/posts/swift-redux-architecture/Thu, 21 Aug 2025 00:00:00 +0000https://peter-notes.com/posts/swift-redux-architecture/深入解析 Swift Redux 架構設計，包含 Reducer、Store、Middleware 的完整實作，搭配清晰的架構圖與資料流程圖，掌握可預測的狀態管理模式https://peter-notes.com/posts/rxswift-bind-viewmodel/Fri, 21 Jul 2023 00:00:00 +0000https://peter-notes.com/posts/rxswift-bind-viewmodel/學習如何使用 RxSwift 的 bind(to:) 方法將 ViewModel 的資料綁定到 View，實現響應式 UI 更新，並探討常見的記憶體管理陷阱。https://peter-notes.com/posts/flutter-state-listening-complete-guide/Thu, 13 Jul 2023 00:00:00 +0000https://peter-notes.com/posts/flutter-state-listening-complete-guide/深入探討 Flutter 四大狀態管理方案的監聽機制：Provider、Bloc、Riverpod、GetX 的核心原理、實戰應用與最佳實踐，幫助你選擇最適合的狀態管理方案。