distributed-systems skillA
distributed-systems is agent-read markdown (skill) from yuecao365/offercome: 分布式系统深挖：一致性与共识、分布式事务、幂等与恰好一次、锁与时钟、微服务治理、热点写入、多活。.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
## 面试官在意什么 这本把后端包里"分布式"三个字下面的东西挖开：数据在多台机器上怎么保持一致、跨服务的操作失败一半怎么办、同一条消息来两次怎么只做一次、机房挂了怎么活。面试官不考 CAP 的背诵，考的是候选人在自己系统里选了哪种一致性、代价是什么、出过什么一致性事故。二面与架构面重点。 ## 项目 / 实习怎么深挖 简历上出现下面这类经历时从哪里切、追什么。追到候选人能说出机制、数字的来源与一次真实的故障或取舍才算实；只有框架名与结论、说不出自己那一段的，记为危险信号。通用的追问方法见 project-deep-dive。 - 简历出现分布式事务 / Seata / Saga → 追为什么需要、补偿失败怎么办、有没有出过不一致、对账怎么做 - 简历出现微服务拆分 → 追按什么拆、拆完最痛的问题、有没有合并过、数据归属怎么定 - 简历出现秒杀 / 库存 / 热点 → 追怎么扛并发写、热点行锁怎么处理、异步落库与对账 - 简历出现分布式锁 → 追用什么实现、过期与续期、脑裂时会怎样、为什么不用数据库唯一键 - 简历出现多活 / 容灾 → 追数据怎么同步、冲突怎么解、切换演练过没有 - 简历出现"恰好一次" → 追靠什么保证（幂等键、事务消费、去重表）、重复消费出过没有 ## 常见失守与危险信号 - 一致性与共识：只会背 CAP；说不出 Raft 选主与日志复制的流程；不知道自己系统是哪种一致性 - 分布式事务与一致性：只会说"用 Seata"；把最终一致当成不一致；不知道补偿也会失败 - 幂等与恰好一次：认为 MQ 能保证恰好一次；幂等靠数据库唯一索引报错却没考虑并发与体验 - 分布式锁与时钟：Redis 锁没考虑过期与续期；不知道依赖系统时钟的风险 - 服务拆分与微服务治理：认为微服务天然更好；拆分依据是技术层而不是业务边界；没考虑数据归属 - 高并发写入与热点处理：直接 update 库存表扛并发；不知道热点行锁；没有异步落库与对账 - 多活与容灾：只说"两地三中心"；不知道数据同步延迟与冲突；从没演练过切换 - 故障演练与混沌：没做过故障注入；不知道自己系统挂哪个依赖会整体不可用 ## 常考主题清单 只列名字、阶梯与答实的标志，作"问到哪一层算实"的参考；问哪些、问几道由这份 JD 与这份简历定，不是配额。 ### 分布式事务与一致性 - 阶梯：为什么跨服务不能用数据库事务 → 2PC、TCC、Saga、本地消息表各自的模型与代价 → 补偿失败、悬挂、空回滚这些边界情况怎么处理 → 业务上能不能通过重新定义流程避开分布式事务 - 答实的标志：优先考虑通过预占、状态机、异步核对避开强一致；TCC 有 try 阶段资源预留的具体设计；有对账与人工兜底；能量化一致性窗口 ### 服务拆分与微服务治理 …
Read the whole file at its exact version.
How to install
mdr add yuecao365/offercome/distributed-systems@git:20260920.a4843f5mdr add yuecao365/offercome/distributed-systems@sha256:4fbcacd8d64509dfPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_b7hkiqfvqb5a7yq5)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6744 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yuecao365/offercome · 23 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_b7hkiqfvqb5a7yq5 GET https://markdownregistry.com/api/v1/resolve?ref=yuecao365/offercome/distributed-systems GET https://markdownregistry.com/api/v1/blob/4fbcacd8d64509df9515eecdb31eced09a863557b344126669c8e6e92a95a3be
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from yuecao365/offercome
Every file in yuecao365/offercome