microservices-developer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Microservices Developer

微服务开发者（Microservices Developer）

When to Use

适用场景

Decompose a monolith or greenfield system into bounded contexts and service boundaries
Design REST, gRPC, or event contracts between services with clear ownership
Choose sync vs async communication and document failure semantics
Implement resilience—timeouts, retries with jitter, circuit breakers, bulkheads, load shedding
Enforce database-per-service (or schema-per-service) and avoid shared mutable stores
Apply saga, outbox, or idempotent consumers for cross-service consistency
Containerize services with twelve-factor config, health checks, and graceful shutdown
Add observability—correlation/trace IDs, RED metrics, structured logs, trace propagation
Plan API versioning, deprecation, and backward compatibility at gateway or mesh edge
Introduce contract tests or consumer-driven contract checks between teams

将单体系统或全新系统拆分为**bounded contexts（有界上下文）**和服务边界
设计服务间的REST、gRPC或事件契约，明确所有权
选择同步vs异步通信方式，并记录故障语义
实现弹性机制——超时、带抖动的重试、断路器、舱壁、流量削峰
强制实施单服务对应单数据库（或单服务对应单Schema），避免共享可变存储
采用saga、outbox或幂等消费者模式保障跨服务一致性
按照**twelve-factor（十二要素）**配置对服务进行容器化，包含健康检查与优雅停机机制
添加可观测性能力——关联ID/链路ID、RED指标、结构化日志、链路追踪传播
在网关或网格层面规划API版本控制、废弃策略与向后兼容性
在团队间引入契约测试或消费者驱动的契约检查

When NOT to Use

不适用场景

Operate Kubernetes clusters, Helm platform add-ons, or cluster SRE only →
```
platform-engineer
```
,
```
cluster-deployment-engineer
```
Define org-wide SLO programs, error budgets, and PRR gates →
```
site-reliability-engineer
```
Design enterprise iPaaS, canonical enterprise models, or B2B integration hubs →
```
enterprise-integration-api-developer
```
Build monolith features, general RFCs, or stack-agnostic code review without service split →
```
senior-software-engineer
```
Implement CI/CD pipelines, GitOps, or release automation only →
```
devops
```
Provision VPC, managed cloud services, or landing zones →
```
cloud-engineer
```
,
```
infrastructure-engineer
```
Gate production builds and artifact promotion policy →
```
build-validator
```
Profile p99 latency and run load/soak tests as the main task →
```
performance-engineer
```
Classified air-gapped pipelines, ATO evidence, cleared promotion →
```
classified-software-devsecops-engineer
```

仅负责Kubernetes集群运维、Helm平台插件或集群SRE工作 →
```
platform-engineer
```
、
```
cluster-deployment-engineer
```
定义全组织范围的SLO方案、错误预算与PRR准入规则 →
```
site-reliability-engineer
```
设计企业iPaaS、标准企业模型或B2B集成枢纽 →
```
enterprise-integration-api-developer
```
开发单体功能、通用RFC或不涉及服务拆分的跨栈代码评审 →
```
senior-software-engineer
```
仅负责CI/CD流水线、GitOps或发布自动化工作 →
```
devops
```
配置VPC、托管云服务或着陆区 →
```
cloud-engineer
```
、
```
infrastructure-engineer
```
管控生产构建与制品晋升策略 →
```
build-validator
```
将分析p99延迟、运行负载/压力测试作为主要任务 →
```
performance-engineer
```
涉密隔离流水线、ATO证据收集、涉密制品晋升 →
```
classified-software-devsecops-engineer
```

Related skills

Need	Skill
General service design, RFCs, refactoring	`senior-software-engineer`
Internal developer platform, golden paths	`platform-engineer`
SLOs, error budgets, reliability program	`site-reliability-engineer`
Enterprise integration, OpenAPI hub, iPaaS	`enterprise-integration-api-developer`
CI/CD, GitOps, deploy pipelines	`devops`
Cloud networking, IAM, managed services	`cloud-engineer`
Terraform modules and core IaC	`infrastructure-engineer`
Build gates and promotion validation	`build-validator`
Profiling, load tests, latency budgets	`performance-engineer`
Cross-system ADRs and NFR sign-off	`senior-system-architecture`
Rollout cutover and change tiers	`deployment-strategist`
Pipeline SAST, SBOM, supply chain	`devsecops`

需求	技能
通用服务设计、RFC、重构	`senior-software-engineer`
内部开发者平台、标准化路径	`platform-engineer`
SLO、错误预算、可靠性方案	`site-reliability-engineer`
企业集成、OpenAPI枢纽、iPaaS	`enterprise-integration-api-developer`
CI/CD、GitOps、部署流水线	`devops`
云网络、IAM、托管服务	`cloud-engineer`
Terraform模块与核心IaC	`infrastructure-engineer`
构建准入与晋升验证	`build-validator`
性能分析、负载测试、延迟预算	`performance-engineer`
跨系统ADR与NFR签署	`senior-system-architecture`
发布切换与变更分级	`deployment-strategist`
流水线SAST、SBOM、供应链安全	`devsecops`

Core Workflows

核心工作流

1. Scope and boundaries

1. 范围与边界

Map domains, define service APIs, and document non-goals.

See
references/microservices_developer_scope.md
and
references/service_boundaries_and_design.md
.

映射领域、定义服务API并记录非目标内容。

参考文档：
references/microservices_developer_scope.md
和
references/service_boundaries_and_design.md
。

2. Communication and contracts

2. 通信与契约

Pick sync/async patterns; define schemas, errors, and versioning.

See
references/communication_sync_async.md
.

选择同步/异步模式；定义 schema、错误处理与版本规则。

参考文档：
references/communication_sync_async.md
。

3. Resilience and reliability

3. 弹性与可靠性

Apply timeouts, retries, breakers, and failure isolation per dependency.

See
references/resilience_and_reliability.md
.

为每个依赖项配置超时、重试、断路器与故障隔离机制。

参考文档：
references/resilience_and_reliability.md
。

4. Data, events, and consistency

4. 数据、事件与一致性

Own data per service; use outbox/saga where cross-service invariants matter.

See
references/data_consistency_and_events.md
.

每个服务独立管理数据；在跨服务不变性场景下使用outbox/saga模式。

参考文档：
references/data_consistency_and_events.md
。

5. Operate, test, and ship

5. 运维、测试与交付

Observability, contract tests, twelve-factor deploy, gateway compatibility.

See
references/observability_testing_deployment.md
.

可观测性、契约测试、十二要素部署、网关兼容性。

参考文档：
references/observability_testing_deployment.md
。

Outputs

交付产物

Service map — contexts, APIs, data ownership, sync/async edges
Contract draft — OpenAPI/proto/event schema with error model and versioning note
Resilience table — per-dependency timeout, retry, breaker, fallback
Consistency note — saga/outbox/idempotency choice with failure compensation
Runbook snippet — health checks, dashboards, rollback triggers

服务映射图 — 上下文、API、数据所有权、同步/异步连接关系
契约草案 — 包含错误模型与版本说明的OpenAPI/proto/事件schema
弹性配置表 — 每个依赖项的超时、重试、断路器、降级方案
一致性说明 — saga/outbox/幂等性方案选择及故障补偿机制
运行手册片段 — 健康检查、仪表盘、回滚触发条件

Principles

原则

Prefer fewer, cohesive services over fine-grained chatter; split on change cadence and team boundaries
Fail fast with explicit timeouts; never unbounded blocking across the network
Design for partial failure—degrade features, do not cascade outages
Make contracts testable before production coupling multiplies

优先选择数量更少、内聚性更强的服务，而非细粒度的频繁交互；根据变更频率与团队边界进行拆分
通过明确的超时机制快速失败；绝不在网络间进行无限制阻塞
针对部分故障设计——降级功能，避免故障级联扩散
在生产环境耦合度增加前，确保契约可测试