A production-ready framework is not only a set of runtime features. It also needs signals that tell a team whether those features still behave correctly after an adapter, provider, or deployment change. Jeston treats contract tests and operational signals as part of the architecture.
Provider-neutral interfaces for databases, cache, queues, storage, metrics, and deployment create natural contract-test boundaries. An adapter should prove the behavior the application relies on, including failure semantics and supported optional methods.
Applications can provide a health registry that exposes /health and /ready. Reports include status, latency, optional tags, and an ISO timestamp. A non-ok report returns 503. These endpoints answer operational questions that unit tests cannot: can the process respond, and are dependencies ready to serve traffic?
Jeston also emphasizes deterministic route discovery, isolated build output directories, structured logs, request IDs, metrics hooks, and CI release gates. Together, these reduce the gap between “the code compiled” and “the deployment is observable and safe to operate.”
Start with one route contract test, add adapter contract tests as infrastructure changes, add health checks for dependencies that affect readiness, and use release gates to verify the artifact and operational signals in CI. Explore the repository at github.com/kvantjs/jeston.
Top comments (0)