effect-http-routing

HTTP routing creates endpoints that handle requests and return JSON responses. Use thin handler functions that decode inputs, validate them against schemas, call services, and encode responses back to clients. Wire these handlers to routes through a composed App layer that provisions dependencies.

Structure handlers as thin functions that perform three steps: decode and validate incoming request data using schema-based validation, call the appropriate service with validated inputs, and encode the service result into a JSON response with proper headers. This separation keeps routing logic clean.

Layers provide a composed App that holds dependencies and injects them into handlers. Define your routes with handlers that receive these dependencies, then pass the App to your HTTP server on startup. This decouples endpoints from service implementations and makes testing easier.

Yes. Proxy endpoints follow the same handler pattern: decode the incoming request, forward it to an upstream service, and encode the response back as JSON. The layer-based dependency system lets you inject the upstream service client and manage its lifecycle.

Schema-based validation checks that incoming request data matches expected structure and types before processing. Handlers use schemas to validate inputs early, returning structured errors to clients if validation fails. This prevents invalid data from reaching service logic.

Structured errors provide consistent, machine-readable error information to clients instead of raw stack traces. They let handlers return appropriate HTTP status codes and error details in JSON format, making client error handling predictable and enabling better debugging.