技能详情（站内镜像，无评论）
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v1.0.0
统计：⭐ 0 · 4 · 0当前安装次数· 0历史安装次数
⭐ 0
安装量（当前） 0
🛡 VirusTotal ：良性 · OpenClaw ：良性
Package：clawkk/microservices
安全扫描（ClawHub）
- VirusTotal ：良性
- OpenClaw ：良性
OpenClaw 评估
这是一份仅供参考的微服务工作流程指南，不需要凭据、安装或系统访问权限，并且在内部与其既定目的一致。
目的
名称和描述与SKILL.md内容相匹配：六阶段微服务工作流程。元数据或说明中没有任何内容要求提供不相关的资源或功能。
说明范围
SKILL.md是纯散文指南（架构/流程清单）。它不包含shell命令、文件读取、网络端点或对环境变量或机密的请求。
安装机制
没有安装规范和代码文件。在安装过程中，不会将任何制品写入磁盘或执行；这是低风险的。
证书
技能没有声明所需的环境变量、凭据或配置路径；指导文本也没有引用任何机密或外部令牌。
持久
始终为false ，并且该技能是用户可调用的。它不会请求持续存在或修改其他技能或系统设置。
综合结论
此技能是纯文本微服务工作流程，不请求凭据或安装软件，因此启用此技能的风险较低。在依赖其建议之前，如果需要出处，请验证作者/来源，将指南视为高级（有见地的）建议，而不是明确的实施计划，并让工程师/安全审查员验证任何拟议的架构更改。这项技能是用户可调用的，并不总是如此……
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「微服务」。简介：深度微服务工作流程-服务边界、数据所有权、同步与异步集成、合约、部署独立性和运营复杂性...。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/clawkk/microservices/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
---
name: microservices
description: Deep microservices workflow—service boundaries, data ownership, synchronous vs async integration, contracts, deployment independence, and operational complexity. Use when splitting a monolith, reviewing service boundaries, or debugging distributed failures.
---
# Microservices (Deep Workflow)
Microservices trade **code simplicity** for **operational and contract complexity**. Justify each boundary with **ownership** and **data isolation**—not fashion.
## When to Offer This Workflow
**Trigger conditions:**
- Splitting the monolith; coupling blocks independent deploys
- Latency cascades, partial failures, contract breaks
- Conway’s law alignment between teams and services
**Initial offer:**
Use **six stages**: (1) goals & constraints, (2) boundaries & data ownership, (3) integration patterns, (4) contracts & versioning, (5) reliability patterns, (6) ops & governance). Confirm org maturity and platform capabilities.
---
## Stage 1: Goals & Constraints
**Goal:** Why not a modular monolith first?
### Valid drivers
- Independent deploy cadence per team
- Different scaling profiles or stacks
- Clear domain ownership and blast-radius isolation
### Costs
- Distributed transactions, harder debugging, broader test matrix
**Exit condition:** Explicit assumption that modular monolith was considered.
---
## Stage 2: Boundaries & Data Ownership
**Goal:** One service owns each aggregate’s write path; no shared writable tables across services.
### Practices
- Bounded contexts from DDD when helpful
**Exit condition:** Entity → owning service map.
---
## Stage 3: Integration Patterns
**Goal:** Sync HTTP/gRPC vs async events—match consistency needs.
### Patterns
- Sagas or outbox for multi-step business processes
**Exit condition:** Sequence diagrams for top three flows.
---
## Stage 4: Contracts & Versioning
**Goal:** Backward-compatible evolution; consumer-driven contracts optional.
### Practices
- Deprecation policy published
---
## Stage 5: Reliability Patterns
**Goal:** Timeouts, retries with backoff, circuit breakers, bulkheads; idempotent handlers for retries.
---
## Stage 6: Ops & Governance
**Goal:** Service catalog, SLIs on dependency edges, golden paths for new services.
---
## Final Review Checklist
- [ ] Boundary and data ownership clear
- [ ] Integration style matches consistency needs
- [ ] Contract versioning policy exists
- [ ] Reliability patterns applied at boundaries
- [ ] Ops ownership and catalog in place
## Tips for Effective Guidance
- Microservices without delivery maturity often fail—say so explicitly.
- Shared databases are hidden coupling—flag them.
- The network is not reliable—design for partial failure.
## Handling Deviations
- Small teams: strong bias toward modular monolith or few services.