Rust HTTP Service Delivery

Deliver server-side HTTP APIs based on HTTP contracts and runtime lifecycles. The framework handles transport adaptation; domain logic and data access remain independently testable without embedding all backend issues into handlers.

Confirming the Service Contract

Before modification, verify from OpenAPI specs, existing routes, clients, tests, configuration, and run environments:

• Methods, paths, status codes, request/response schemas, and compatibility strategies;
• Authentication context origin (authentication system design is outside this skill scope);
• Request bodies, concurrency limits, timeouts, upload sizes, and response size constraints;
• Dependencies on external HTTP services, databases, caches, or queues, including failure semantics;
• Listening addresses, proxies, TLS termination, health checks, graceful shutdown budgets;
• Rust/MSRV versions of axum, Tokio, Tower, and related crates with locked dependencies;
• Logging levels, tracing configuration, metrics exposure, sensitive field handling, data retention policies.

Response fields from existing client libraries constitute compatibility constraints. When contracts are missing, declare minimal assumptions first.

Workflow