Domain Cloud Native

作者 actionbook5c40d3ad7851無授權條款1.5K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫6 週前更新

Use when building cloud-native apps. Keywords: kubernetes, k8s, docker, container, grpc, tonic, microservice, service mesh, observability, tracing, metrics, health check, cloud, deployment, 云原生, 微服务, 容器

僅含說明DevOps & Cloud Software Development

AI 產生的概覽

為 Rust 雲原生服務設計提供 12 要素、無狀態、可觀測性與優雅關閉等約束指引。

功能: 此技能為建構雲原生應用程式（主要是 Rust）提供領域約束。它將 12 要素設定、無狀態設計、健康檢查、優雅關閉與可觀測性等規則對應到設計影響與 crate 選擇。文件包含優雅關閉與健康/就緒端點的程式碼模式，以及常見錯誤與相關技能對照表。
適用情境: 適用於設計或審查執行於容器或 Kubernetes 中的雲原生服務。適合需要無狀態設計、分散式追蹤、指標、健康檢查或優雅關閉的工作。它僅提供指引，不產出檔案或指令碼。
執行需求: 無需指令碼或特殊工具，僅為純說明文件。程式碼模式涉及 tonic、kube、tracing、opentelemetry、prometheus、config、axum 等 Rust crate，但閱讀這些指引無需安裝任何項目。

Cloud-Native Domain

Layer 3: Domain Constraints

Domain Constraints → Design Implications

Domain Rule	Design Constraint	Rust Implication
12-Factor	Config from env	Environment-based config
Observability	Metrics + traces	tracing + opentelemetry
Health checks	Liveness/readiness	Dedicated endpoints
Graceful shutdown	Clean termination	Signal handling
Horizontal scale	Stateless design	No local state
Container-friendly	Small binaries	Release optimization

Critical Constraints

Stateless Design

RULE: No local persistent stateWHY: Pods can be killed/rescheduled anytimeRUST: External state (Redis, DB), no static mut

RULE: No local persistent stateWHY: Pods can be killed/rescheduled anytimeRUST: External state (Redis, DB), no static mut

Graceful Shutdown

RULE: Handle SIGTERM, drain connectionsWHY: Zero-downtime deploymentsRUST: tokio::signal + graceful shutdown

RULE: Handle SIGTERM, drain connectionsWHY: Zero-downtime deploymentsRUST: tokio::signal + graceful shutdown

Observability

RULE: Every request must be traceableWHY: Debugging distributed systemsRUST: tracing spans, opentelemetry export

RULE: Every request must be traceableWHY: Debugging distributed systemsRUST: tracing spans, opentelemetry export

Trace Down ↓

From constraints to design (Layer 2):

"Need distributed tracing"    ↓ m12-lifecycle: Span lifecycle    ↓ tracing + opentelemetry
"Need graceful shutdown"    ↓ m07-concurrency: Signal handling    ↓ m12-lifecycle: Connection draining
"Need health checks"    ↓ domain-web: HTTP endpoints    ↓ m06-error-handling: Health status

"Need distributed tracing"    ↓ m12-lifecycle: Span lifecycle    ↓ tracing + opentelemetry
"Need graceful shutdown"    ↓ m07-concurrency: Signal handling    ↓ m12-lifecycle: Connection draining
"Need health checks"    ↓ domain-web: HTTP endpoints    ↓ m06-error-handling: Health status

Key Crates

Design Patterns

Pattern	Purpose	Implementation
gRPC services	Service mesh	tonic + tower
K8s operators	Custom resources	kube-runtime Controller
Observability	Debugging	tracing + OTEL
Health checks	Orchestration	`/health`, `/ready`
Config	12-factor	Env vars + secrets

Code Pattern: Graceful Shutdown

rust

use tokio::signal;
async fn run_server() -> anyhow::Result<()> {    let app = Router::new()        .route("/health", get(health))        .route("/ready", get(ready));
    let addr = SocketAddr::from(([0, 0, 0, 0], 8080));
    axum::Server::bind(&addr)        .serve(app.into_make_service())        .with_graceful_shutdown(shutdown_signal())        .await?;
    Ok(())}
async fn shutdown_signal() {    signal::ctrl_c().await.expect("failed to listen for ctrl+c");    tracing::info!("shutdown signal received");}

use tokio::signal;
async fn run_server() -> anyhow::Result<()> {    let app = Router::new()        .route("/health", get(health))        .route("/ready", get(ready));
    let addr = SocketAddr::from(([0, 0, 0, 0], 8080));
    axum::Server::bind(&addr)        .serve(app.into_make_service())        .with_graceful_shutdown(shutdown_signal())        .await?;
    Ok(())}
async fn shutdown_signal() {    signal::ctrl_c().await.expect("failed to listen for ctrl+c");    tracing::info!("shutdown signal received");}

Health Check Pattern

rust

async fn health() -> StatusCode {    StatusCode::OK}
async fn ready(State(db): State<Arc<DbPool>>) -> StatusCode {    match db.ping().await {        Ok(_) => StatusCode::OK,        Err(_) => StatusCode::SERVICE_UNAVAILABLE,    }}

async fn health() -> StatusCode {    StatusCode::OK}
async fn ready(State(db): State<Arc<DbPool>>) -> StatusCode {    match db.ping().await {        Ok(_) => StatusCode::OK,        Err(_) => StatusCode::SERVICE_UNAVAILABLE,    }}

Common Mistakes

Trace to Layer 1

Constraint	Layer 2 Pattern	Layer 1 Implementation
Stateless	External state	Arc<Client> for external
Graceful shutdown	Signal handling	tokio::signal
Tracing	Span lifecycle	tracing + OTEL
Health checks	HTTP endpoints	Dedicated routes

Related Skills

來源與署名

來源：actionbook/rust-skills位於skills/domain-cloud-native提交5c40d3a

授權條款：無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

Mistake	Domain Violation	Fix
Local file state	Not stateless	External storage
No SIGTERM handling	Hard kills	Graceful shutdown
No tracing	Can't debug	tracing spans
Static config	Not 12-factor	Env vars

When	See
Async patterns	m07-concurrency
HTTP endpoints	domain-web
Error handling	m13-domain-error
Resource lifecycle	m12-lifecycle

Domain Cloud Native

Cloud-Native Domain

Domain Constraints → Design Implications

Critical Constraints

Stateless Design

Graceful Shutdown

Observability

Trace Down ↓

Key Crates

Design Patterns

Code Pattern: Graceful Shutdown

Health Check Pattern

Common Mistakes

Trace to Layer 1

Related Skills

來源與署名

更多來自 actionbook/rust-skills 的技能

Rust Trait Explorer

Rust Symbol Analyzer

Rust Skill Creator

Rust Router

Rust Refactor Helper

Rust Daily

更多DevOps & Cloud技能

Playwright Devops

M5 Onboard

Yeet

Runbook

Incident Response

Deploy Checklist