https://shio-chan-dev.github.io/jeanblog/zh/tags/%E6%9E%B6%E6%9E%84/Recent content in 架构 on Jeanphilo BlogHugo -- 0.159.2zh-cnSat, 24 Jan 2026 15:35:03 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/general/refactor-vs-rewrite-debate/Sat, 24 Jan 2026 15:35:03 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/general/refactor-vs-rewrite-debate/给出重构 vs 重写的决策框架，避免拍脑袋。https://shio-chan-dev.github.io/jeanblog/zh/dev/design-patterns/active-record-limitations/Sat, 24 Jan 2026 15:29:20 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/design-patterns/active-record-limitations/分析 Active Record 模式的局限性，并给出适用边界与替代方案。https://shio-chan-dev.github.io/jeanblog/zh/dev/design/design-vs-architecture/Sat, 24 Jan 2026 15:29:20 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/design/design-vs-architecture/从范围与抽象层级解释设计与架构的区别。https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/event-driven-scalability/Sat, 24 Jan 2026 15:29:20 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/event-driven-scalability/解释事件驱动架构的扩展优势、适用场景与工程取舍。https://shio-chan-dev.github.io/jeanblog/zh/dev/management/cto-decision-framework/Sat, 24 Jan 2026 13:35:15 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/management/cto-decision-framework/提供 CTO 视角下的决策框架：业务、架构、组织与风险。https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/recommendation-people-also-like/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/recommendation-people-also-like/用协同过滤的简化模型实现“相似商品推荐”。https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cpu-changes-after-80s/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cpu-changes-after-80s/概述 CPU 从频率提升到多核与缓存层级的演进，并解释对编程的影响。https://shio-chan-dev.github.io/jeanblog/zh/dev/soa/soa-vs-microservices/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/soa/soa-vs-microservices/对比 SOA 与微服务在服务粒度、治理方式与演进路径上的差异。https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/design-issues-causing-dos/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/design-issues-causing-dos/讨论架构设计缺陷如何引发类似 DoS 的系统故障。https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/failover-and-user-session/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/failover-and-user-session/解释故障切换与用户会话管理的核心策略与工程取舍。https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/design-decentralized-p2p-system/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/design-decentralized-p2p-system/从节点发现、路由与一致性角度介绍 P2P 系统设计。https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/unity-of-design-aristocracy/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/unity-of-design-aristocracy/讨论“统一设计”与团队自治之间的张力与平衡。https://shio-chan-dev.github.io/jeanblog/zh/dev/soa/microservices-pros-cons/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/soa/microservices-pros-cons/总结微服务的优势与代价，并给出选型建议。https://shio-chan-dev.github.io/jeanblog/zh/dev/soa/when-microservices-too-micro/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/soa/when-microservices-too-micro/讨论微服务拆分过细的代价与判断标准。https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cgi-scalability-issues/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cgi-scalability-issues/解释 CGI 进程模型的性能瓶颈与扩展性问题。https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/performance-lifecycle-management/Sat, 24 Jan 2026 13:27:25 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/performance-lifecycle-management/说明性能从需求、设计、开发到上线的生命周期管理要点。https://shio-chan-dev.github.io/jeanblog/zh/dev/design-patterns/anti-corruption-layer/Sat, 24 Jan 2026 13:08:42 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/design-patterns/anti-corruption-layer/解释反腐败层的作用、使用场景与实现方式。https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/fallacies-of-distributed-computing/Sat, 24 Jan 2026 13:08:42 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/fallacies-of-distributed-computing/用工程视角解释分布式计算的常见谬论与风险。https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/failure-handling/Sat, 24 Jan 2026 13:08:42 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/failure-handling/总结分布式系统常见故障处理策略，并给出工程落地建议。https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/secure-vs-open-network-architecture/Sat, 24 Jan 2026 13:08:42 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/secure-vs-open-network-architecture/对比封闭安全网络与开放网络下的架构重点与安全策略。https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/emergent-vs-evolutionary-architecture/Sat, 24 Jan 2026 13:08:42 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/emergent-vs-evolutionary-architecture/对比紧急设计与演化架构的理念与工程实践。https://shio-chan-dev.github.io/jeanblog/zh/dev/database/implement-transactions-without-db/Sat, 24 Jan 2026 13:08:42 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/database/implement-transactions-without-db/讨论无事务系统的补救思路：日志、锁与补偿。https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/when-tight-coupling-ok/Sat, 24 Jan 2026 13:08:42 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/when-tight-coupling-ok/讨论紧耦合的合理场景与风险控制方法。https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cloud-ready-system/Sat, 24 Jan 2026 13:08:42 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/cloud-ready-system/总结云就绪系统的关键特征与工程实践清单。https://shio-chan-dev.github.io/jeanblog/zh/dev/database/business-logic-in-stored-procedures/Sat, 24 Jan 2026 13:08:42 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/database/business-logic-in-stored-procedures/讨论把业务逻辑放进存储过程的收益、风险与适用场景。https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/request-response-vs-pubsub/Sat, 24 Jan 2026 13:04:00 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/request-response-vs-pubsub/对比请求/响应与发布/订阅的适用场景、优缺点与选型建议。https://shio-chan-dev.github.io/jeanblog/zh/dev/engineering/greenfield-vs-brownfield/Sat, 24 Jan 2026 12:47:45 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/engineering/greenfield-vs-brownfield/对比新建项目与遗留系统的利弊，并给出选择与落地策略。https://shio-chan-dev.github.io/jeanblog/zh/dev/design-patterns/hollywood-principle/Sat, 24 Jan 2026 12:45:38 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/design-patterns/hollywood-principle/解释好莱坞原则的含义、与 IoC 的关系，以及在框架设计中的落地方式。https://shio-chan-dev.github.io/jeanblog/zh/dev/design-patterns/active-record-vs-data-mapper/Sat, 24 Jan 2026 12:40:32 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/design-patterns/active-record-vs-data-mapper/对比 Active Record 与 Data Mapper 两种持久化模式的适用场景与代价。https://shio-chan-dev.github.io/jeanblog/zh/dev/design/design-architecture-functionality-aesthetic/Sat, 24 Jan 2026 12:33:47 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/design/design-architecture-functionality-aesthetic/用工程视角区分设计、架构、功能与美学，并给出落地实践与协作方式。https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/rpc-common-drawbacks/Sat, 24 Jan 2026 12:23:30 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/rpc-common-drawbacks/总结 RPC 的通用缺点，包括耦合、可观测性与错误处理复杂度。https://shio-chan-dev.github.io/jeanblog/zh/dev/database/object-relational-impedance-mismatch/Sat, 24 Jan 2026 11:06:00 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/database/object-relational-impedance-mismatch/解释对象模型与关系模型的不匹配来源，并给出实际工程中的缓解策略。https://shio-chan-dev.github.io/jeanblog/zh/dev/frontend/csr-vs-ssr-tradeoffs/Sat, 24 Jan 2026 11:03:05 +0800https://shio-chan-dev.github.io/jeanblog/zh/dev/frontend/csr-vs-ssr-tradeoffs/从 TTFB/TTI/SEO 等指标出发，对比 CSR 与 SSR 的优缺点，并给出决策指南与可运行示例。https://shio-chan-dev.github.io/jeanblog/zh/dev/python/pipeline-orchestration/Tue, 13 Jan 2026 00:00:00 +0000https://shio-chan-dev.github.io/jeanblog/zh/dev/python/pipeline-orchestration/用通俗语言解释“后端任务编排”的必要性：把流程顺序从前端移到后端，用配置驱动步骤与等待点。给出最小可运行示例、落地步骤与常见坑。https://shio-chan-dev.github.io/jeanblog/zh/thoughts/thoughts/algorithm-vs-business/Wed, 07 Jan 2026 00:00:00 +0000https://shio-chan-dev.github.io/jeanblog/zh/thoughts/thoughts/algorithm-vs-business/用投标写作系统为例，解释算法与业务的边界：算法负责把模糊世界压缩成结构化中间态，业务负责在中间态稳定后编排流程。附：JupyterLab 验证清单、最小可运行示例与常见坑。