Show HN: Pacto – OCI-distributed contracts for cloud-native services

**Show HN: Pacto – OCI-distributed contracts for cloud-native services**

Author here.I work as a platform engineer and kept running into the same problem: services are described in fragments across different tools.APIs live in OpenAPI specs. Deployment assumptions end up in Helm values. Runtime details are hidden in Kubernetes manifests. Configuration lives in environment variables. Dependencies are often documented in READMEs or tribal knowledge.There is no single machine-readable contract that describes how a service actually behaves operationally.So I started building Pacto.Pacto defines a contract for cloud-native services that captures things like:• interfaces (HTTP, gRPC, events) • runtime semantics (stateless, stateful, hybrid) • dependencies between services • configuration schema • scaling expectationsAll of this lives in a single pacto.yaml file and can be packaged and distributed as an OCI artifact.The idea is that platforms, CI systems, and tooling can reason about services without guessing or reverse-engineering deployments.For example the CLI can already:• validate service contracts • detect breaking operational changes (pacto diff) • resolve dependency graphs • package contracts as OCI artifactsOne part I found particularly useful is making state semantics explicit, for example:runtime.state.type: stateless | stateful | hybridThat allows platforms to reason about storage, lifecycle and scaling without relying on implicit assumptions.The project is still early but already usable...

---

**[devsupporter 해설]**

이 기사는 Show HN에서 제공하는 최신 개발 동향입니다. 관련 도구나 기술에 대해 더 알아보시려면 원본 링크를 참고하세요.