Skip to main content

API Route Cycle

Trigger a cycle via a named form action, demonstrating the fetch-based API pattern.

Pipeline

order & status
CLIENTSERVERBrowser — client-side form submission or fetch callBrowserNetwork — HTTP round-trip between browser and serverNetworkServer — SvelteKit hooks, validation, authServerDomain — pure business logic, no framework depsDomainDatabase — Drizzle insert into showcase.cycle_runDatabaseResponse — serialization back to the clientResponse

Waterfall

relative timing
Browser
Network
Server
Domain
Database
Response