Documentation
Time is a dependency.
Modern systems depend on latency, retries, timeouts, and user perception — yet time is often mocked, skipped, or approximated during development.
Delay as a Service exists to make time explicit.
It does not simulate networks.
It does not emulate failures.
It simply waits.
By treating time as a first-class input, developers can test loading states, retry logic, and user experience under real waiting conditions — without adding complexity or infrastructure.
This service is intentionally minimal.
The constraint is the product.
https://daas.awestar.solutions
Returns a response after a short, random delay.
GET /delay
Requests a specific delay duration.
GET /delay?ms=1000
HTTP/1.1 200 OK
Content-Type: application/json
{
"status": "ok",
"delay_ms": 1000
}
Invalid request:
HTTP/1.1 400 Bad Request
{
"status": "invalid_request",
"message": "Delay must be between 100 and 5000 milliseconds."
}
Rate limited or too many concurrent requests:
HTTP/1.1 429 Too Many Requests
{
"status": "rate_limited"
}